shaba/libvirt
1
0
Fork 0
mirror of https://gitlab.com/libvirt/libvirt.git synced 2025-01-05 13:17:51 +03:00
Code Releases Activity

docs: formatdomain: Remove 'elementsNICSDirect' anchor

Browse Source 
Signed-off-by: Peter Krempa <pkrempa@redhat.com>
Reviewed-by: Ján Tomko <jtomko@redhat.com>
This commit is contained in:
Peter Krempa 2022-05-13 10:31:34 +02:00
parent dadd384907
commit 4506e4057d
3 changed files with 3 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
docs/formatdomain.rst
View File

@ -4725,7 +4725,6 @@ integration is required.
</devices> </devices>
... ...
:anchor:`<a id="elementsNICSDirect"/>`
Direct attachment to physical interface Direct attachment to physical interface
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

4
docs/formatnetwork.rst
View File

@ -253,7 +253,7 @@ to the physical LAN (if at all).
interfaces to be used for a "direct" connection via macvtap using interfaces to be used for a "direct" connection via macvtap using
macvtap's "bridge" mode (if the forward element has one or more macvtap's "bridge" mode (if the forward element has one or more
``<interface>`` subelements, :since:`Since 0.9.4` ) (see `Direct ``<interface>`` subelements, :since:`Since 0.9.4` ) (see `Direct
attachment to physical interface <formatdomain.html#elementsNICSDirect>`__ attachment to physical interface <formatdomain.html#direct-attachment-to-physical-interface>`__
for descriptions of the various macvtap modes). libvirt doesn't attempt to for descriptions of the various macvtap modes). libvirt doesn't attempt to
manage the bridge interface at all, thus the ``<bridge>`` element's manage the bridge interface at all, thus the ``<bridge>`` element's
``stp`` and ``delay`` attributes are not allowed; no iptables rules, IP ``stp`` and ``delay`` attributes are not allowed; no iptables rules, IP
@ -599,7 +599,7 @@ as the 'default' portgroup for the network), and each portgroup has a name, as
well as various attributes and subelements associated with it. The currently well as various attributes and subelements associated with it. The currently
supported subelements are ``<bandwidth>`` (described in `Quality of service`_) supported subelements are ``<bandwidth>`` (described in `Quality of service`_)
and ``<virtualport>`` (documented and ``<virtualport>`` (documented
`here <formatdomain.html#elementsNICSDirect>`__). If a domain interface `here <formatdomain.html#direct-attachment-to-physical-interface>`__). If a domain interface
definition specifies a portgroup (by adding a ``portgroup`` attribute to the definition specifies a portgroup (by adding a ``portgroup`` attribute to the
``<source>`` subelement), that portgroup's info will be merged into the ``<source>`` subelement), that portgroup's info will be merged into the
interface's configuration. If no portgroup is given in the interface definition, interface's configuration. If no portgroup is given in the interface definition,

2
docs/formatnetworkport.rst
View File

@ -151,7 +151,7 @@ interface.
The ``dev`` attribute provides the name of the physical network interface to The ``dev`` attribute provides the name of the physical network interface to
which the port will be connected. The ``mode`` attribute describes how the which the port will be connected. The ``mode`` attribute describes how the
connection will be setup and takes the same values described in the `domain connection will be setup and takes the same values described in the `domain
XML <formatdomain.html#elementsNICSDirect>`__. XML <formatdomain.html#direct-attachment-to-physical-interface>`__.
Host PCI Host PCI
^^^^^^^^ ^^^^^^^^