External/libvirt
1
0
Fork 0
mirror of https://gitlab.com/libvirt/libvirt.git synced 2024-12-22 21:55:25 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs: formatdomain: Remove 'elementsNICSTargetOverride' 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 4506e4057d
commit 99e01a44e4
1 changed files with 3 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
docs/formatdomain.rst
View File

@ -4513,8 +4513,7 @@ can be determined by examining the virtual network config with
'default' setup out of the box which does NAT'ing to the default route and has 'default' setup out of the box which does NAT'ing to the default route and has
an IP range of ``192.168.122.0/255.255.255.0``. Each guest will have an an IP range of ``192.168.122.0/255.255.255.0``. Each guest will have an
associated tun device created with a name of vnetN, which can also be overridden associated tun device created with a name of vnetN, which can also be overridden
with the <target> element (see `overriding the target with the <target> element (see `Overriding the target element`_).
element <#elementsNICSTargetOverride>`__).
When the source of an interface is a network, a ``portgroup`` can be specified When the source of an interface is a network, a ``portgroup`` can be specified
along with the name of the network; one network may have multiple portgroups along with the name of the network; one network may have multiple portgroups
@ -4580,8 +4579,8 @@ static wired networking configs.**
Provides a bridge from the VM directly to the LAN. This assumes there is a Provides a bridge from the VM directly to the LAN. This assumes there is a
bridge device on the host which has one or more of the hosts physical NICs bridge device on the host which has one or more of the hosts physical NICs
attached. The guest VM will have an associated tun device created with a name of attached. The guest VM will have an associated tun device created with a name of
vnetN, which can also be overridden with the <target> element (see `overriding vnetN, which can also be overridden with the <target> element (see
the target element <#elementsNICSTargetOverride>`__). The tun device will be `Overriding the target element`_). The tun device will be
attached to the bridge. The IP range / network configuration is whatever is used attached to the bridge. The IP range / network configuration is whatever is used
on the LAN. This provides the guest VM full incoming & outgoing net access just on the LAN. This provides the guest VM full incoming & outgoing net access just
like a physical machine. like a physical machine.
@ -5331,7 +5330,6 @@ bridge interfaces. This does not work in session mode. :since:`Since 1.2.9`
For tap devices there is also ``sndbuf`` element which can adjust the size of For tap devices there is also ``sndbuf`` element which can adjust the size of
send buffer in the host. :since:`Since 0.8.8` send buffer in the host. :since:`Since 0.8.8`
:anchor:`<a id="elementsNICSTargetOverride"/>`
Overriding the target element Overriding the target element
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^