From nobody Tue Jan 21 07:32:31 2025 Delivered-To: importer@patchew.org Received-SPF: pass (zohomail.com: domain of lists.libvirt.org designates 8.43.85.245 as permitted sender) client-ip=8.43.85.245; envelope-from=devel-bounces@lists.libvirt.org; helo=lists.libvirt.org; Authentication-Results: mx.zohomail.com; dkim=fail; spf=pass (zohomail.com: domain of lists.libvirt.org designates 8.43.85.245 as permitted sender) smtp.mailfrom=devel-bounces@lists.libvirt.org; dmarc=fail(p=none dis=none) header.from=solinno.co.uk Return-Path: Received: from lists.libvirt.org (lists.libvirt.org [8.43.85.245]) by mx.zohomail.com with SMTPS id 1736343224462834.8924027704726; Wed, 8 Jan 2025 05:33:44 -0800 (PST) Received: by lists.libvirt.org (Postfix, from userid 996) id 803D212B1; Wed, 8 Jan 2025 08:33:43 -0500 (EST) Received: from lists.libvirt.org (localhost [IPv6:::1]) by lists.libvirt.org (Postfix) with ESMTP id 74572135F; Wed, 8 Jan 2025 08:31:39 -0500 (EST) Received: by lists.libvirt.org (Postfix, from userid 996) id A0A791272; Wed, 8 Jan 2025 08:31:27 -0500 (EST) Received: from doppler.solinno.uk (doppler.solinno.uk [81.2.106.178]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by lists.libvirt.org (Postfix) with ESMTPS id 7DBDA1270 for ; Wed, 8 Jan 2025 08:31:26 -0500 (EST) Received: from plato.solinno.co.uk (e.d.1.4.d.2.c.e.4.d.9.9.7.9.7.e.a.c.f.8.6.f.d.1.0.b.8.0.1.0.0.2.ip6.arpa [IPv6:2001:8b0:1df6:8fca:e797:99d4:ec2d:41de]) by doppler.solinno.uk (Postfix) with ESMTPSA id A9E9F62048; Wed, 8 Jan 2025 13:31:25 +0000 (GMT) Received: by plato.solinno.co.uk (Postfix, from userid 1000) id 68ED847; Wed, 08 Jan 2025 13:31:41 +0000 (GMT) X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on lists.libvirt.org X-Spam-Level: X-Spam-Status: No, score=-0.6 required=5.0 tests=DKIM_INVALID,DKIM_SIGNED, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, RCVD_IN_VALIDITY_RPBL_BLOCKED,RCVD_IN_VALIDITY_SAFE_BLOCKED, SPF_HELO_PASS autolearn=unavailable autolearn_force=no version=3.4.4 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=solinno.co.uk; s=mail; t=1736343085; bh=GCXoTqRG+x2rPfYx1My1RJnpxw5Y1QKaRqL49T/MLDk=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=hrR99xpcImXX6yk+yCLi/JttfH6qCNClu63PL1CA9zOZiV4G601F9ZRT1RZCMb645 rnx4RPRCvzaiqwV0PT6nE9aETfWM0VWRgt4XsL4awcERQe2jJ2ODE0fkntfrEIGzYy GQFS/dOVpTTp8B60eKkFib+w8jPLaAx5NodHcQhE= From: Leigh Brown To: devel@lists.libvirt.org, Laine Stump Subject: [PATCH v4 4/4] docs: standard linux bridges now support vlans Date: Wed, 8 Jan 2025 13:31:30 +0000 Message-ID: <20250108133130.182335-5-leigh@solinno.co.uk> X-Mailer: git-send-email 2.47.1 In-Reply-To: <20250108133130.182335-1-leigh@solinno.co.uk> References: <20250108133130.182335-1-leigh@solinno.co.uk> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Message-ID-Hash: WWU6S2KQKHE7TJ4ICYRSZM35F6HNKD3P X-Message-ID-Hash: WWU6S2KQKHE7TJ4ICYRSZM35F6HNKD3P X-MailFrom: leigh@solinno.co.uk X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-config-1; header-match-config-2; header-match-config-3; header-match-devel.lists.libvirt.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; suspicious-header CC: Leigh Brown X-Mailman-Version: 3.2.2 Precedence: list List-Id: Development discussions about the libvirt library & tools Archived-At: List-Archive: List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-ZohoMail-DKIM: fail (Computed bodyhash is different from the expected one) X-ZM-MESSAGEID: 1736343225604116600 Content-Type: text/plain; charset="utf-8" Update domain XML and network XML documentation to describe how standard linux bridges support the VLAN configuration. Signed-off-by: Leigh Brown Reviewed-by: Laine Stump --- docs/formatdomain.rst | 37 +++++++++++++++++----------------- docs/formatnetwork.rst | 45 +++++++++++++++++++++--------------------- 2 files changed, 42 insertions(+), 40 deletions(-) diff --git a/docs/formatdomain.rst b/docs/formatdomain.rst index 02c5361905..89073feb48 100644 --- a/docs/formatdomain.rst +++ b/docs/formatdomain.rst @@ -6039,28 +6039,29 @@ VLAN tags to apply to the guest's network traffic := since:`Since 0.10.0`. =20 Network connections that support guest-transparent VLAN tagging include ``type=3D'bridge'`` interfaces connected to an Open vSwitch bridge, SRIOV -Virtual Functions (VF) used via ``type=3D'hostdev'`` (direct device assign= ment) -and, :since:`since 1.3.5`, SRIOV VFs used via ``type=3D'direct'`` with -``mode=3D'passthrough'`` (macvtap "passthru" mode). All other -connection types, including standard linux bridges and libvirt's own virtu= al +Virtual Functions (VF) used via ``type=3D'hostdev'`` (direct device assign= ment), +:since:`since 1.3.5`, SRIOV VFs used via ``type=3D'direct'`` with +``mode=3D'passthrough'`` (macvtap "passthru" mode) and, :since:`since 11.0= .0` +standard linux bridges. Other connection types, including libvirt's own vi= rtual networks, **do not** support it. 802.1Qbh (vn-link) and 802.1Qbg (VEPA) sw= itches provide their own way (outside of libvirt) to tag guest traffic onto a spe= cific VLAN. Each tag is given in a separate ```` subelement of ```` (= for example: ````). For VLAN trunking of multiple tags (which = is -supported only on Open vSwitch connections), multiple ```` subelement= s can -be specified, which implies that the user wants to do VLAN trunking on the -interface for all the specified tags. In the case that VLAN trunking of a = single -tag is desired, the optional attribute ``trunk=3D'yes'`` can be added to t= he -toplevel ```` element to differentiate trunking of a single tag from -normal tagging. - -For network connections using Open vSwitch it is also possible to configure -'native-tagged' and 'native-untagged' VLAN modes :since:`Since 1.1.0`. Thi= s is -done with the optional ``nativeMode`` attribute on the ```` subelemen= t: -``nativeMode`` may be set to 'tagged' or 'untagged'. The ``id`` attribute = of the -```` subelement containing ``nativeMode`` sets which VLAN is consider= ed to -be the "native" VLAN for this interface, and the ``nativeMode`` attribute -determines whether or not traffic for that VLAN will be tagged. +supported on Open vSwitch connections and standard linux bridges), multiple +```` subelements can be specified, which implies that the user wants = to do +VLAN trunking on the interface for all the specified tags. In the case tha= t VLAN +trunking of a single tag is desired, the optional attribute ``trunk=3D'yes= '`` can +be added to the toplevel ```` element to differentiate trunking of a +single tag from normal tagging. + +For network connections using Open vSwitch and standard linux bridges it i= s also +possible to configure 'native-tagged' and 'native-untagged' VLAN modes +:since:`Since 1.1.0`. This is done with the optional ``nativeMode`` attrib= ute on +the ```` subelement: ``nativeMode`` may be set to 'tagged' or 'untagg= ed'. +The ``id`` attribute of the ```` subelement containing ``nativeMode``= sets +which VLAN is considered to be the "native" VLAN for this interface, and t= he +``nativeMode`` attribute determines whether or not traffic for that VLAN w= ill be +tagged. =20 =20 Isolating guests' network traffic from each other diff --git a/docs/formatnetwork.rst b/docs/formatnetwork.rst index 9b4ecbf31d..053fe6ad56 100644 --- a/docs/formatnetwork.rst +++ b/docs/formatnetwork.rst @@ -520,28 +520,29 @@ VLAN tags to apply to the guest's network traffic :si= nce:`Since 0.10.0`. =20 Network connections that support guest-transparent VLAN tagging include ``type=3D'bridge'`` interfaces connected to an Open vSwitch bridge, SRIOV -Virtual Functions (VF) used via ``type=3D'hostdev'`` (direct device assign= ment) -and, :since:`since 1.3.5`, SRIOV VFs used via ``type=3D'direct'`` with -``mode=3D'passthrough'`` (macvtap "passthru" mode). All other -connection types, including standard linux bridges and libvirt's own virtu= al -networks, **do not** support it. 802.1Qbh (vn-link) and 802.1Qbg (VEPA) sw= itches -provide their own way (outside of libvirt) to tag guest traffic onto a spe= cific -VLAN. Each tag is given in a separate ```` subelement of ```` (= for -example: ````). For VLAN trunking of multiple tags (which = is -supported only on Open vSwitch connections), multiple ```` subelement= s can -be specified, which implies that the user wants to do VLAN trunking on the -interface for all the specified tags. In the case that VLAN trunking of a = single -tag is desired, the optional attribute ``trunk=3D'yes'`` can be added to t= he -toplevel ```` element to differentiate trunking of a single tag from -normal tagging. - -For network connections using Open vSwitch it is also possible to configure -'native-tagged' and 'native-untagged' VLAN modes :since:`Since 1.1.0`. Thi= s is -done with the optional ``nativeMode`` attribute on the ```` subelemen= t: -``nativeMode`` may be set to 'tagged' or 'untagged'. The ``id`` attribute = of the -```` subelement containing ``nativeMode`` sets which VLAN is consider= ed to -be the "native" VLAN for this interface, and the ``nativeMode`` attribute -determines whether or not traffic for that VLAN will be tagged. +Virtual Functions (VF) used via ``type=3D'hostdev'`` (direct device assign= ment), +:since:`since 1.3.5`, SRIOV VFs used via ``type=3D'direct'`` with +``mode=3D'passthrough'`` (macvtap "passthru" mode) and, :since:`since 11.0= .0`, +standard linux bridges. All other connection types, including libvirt's own +virtual networks, **do not** support it. 802.1Qbh (vn-link) and 802.1Qbg (= VEPA) +switches provide their own way (outside of libvirt) to tag guest traffic o= nto a +specific VLAN. Each tag is given in a separate ```` subelement of +```` (for example: ````). For VLAN trunking of multi= ple +tags (which is supported on Open vSwitch connections and standard linux +bridges), multiple ```` subelements can be specified, which implies t= hat +the user wants to do VLAN trunking on the interface for all the specified = tags. +In the case that VLAN trunking of a single tag is desired, the optional +attribute ``trunk=3D'yes'`` can be added to the toplevel ```` elemen= t to +differentiate trunking of a single tag from normal tagging. + +For network connections using Open vSwitch :since:`since 1.1.10` and stand= ard +linux bridges :since:`since 11.0.0` it is also possible to configure +'native-tagged' and 'native-untagged' VLAN modes. This is done with the op= tional +``nativeMode`` attribute on the ```` subelement: ``nativeMode`` may b= e set +to 'tagged' or 'untagged'. The ``id`` attribute of the ```` subelement +containing ``nativeMode`` sets which VLAN is considered to be the "native"= VLAN +for this interface, and the ``nativeMode`` attribute determines whether or= not +traffic for that VLAN will be tagged. =20 ```` elements can also be specified in a ```` element, as= well as directly in a domain's ```` element. In the case that a vlan= tag --=20 2.39.5