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

docs: formatdomain: Remove 'elementsNICS' anchor

Browse Source 
The one local link addition prompted rewrapping of the whole paragraph.

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 abc1b8ab60
commit dadd384907
3 changed files with 8 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
docs/formatdomain.rst
View File

@ -239,11 +239,11 @@ harddisk, cdrom, network) determining where to obtain/find the boot image.
(the sorted list is vda, vdb, hda, hdc). Similar domain with hdc, vda, vdb,
and hda disks will boot from hda (sorted disks are: hda, hdc, vda, vdb). It
can be tricky to configure in the desired way, which is why per-device boot
elements (see `Hard drives, floppy disks, CDROMs`_, `network
interfaces <#elementsNICS>`__, and `Host device assignment`_
sections below) were introduced and they are the preferred way providing full
control over booting order. The ``boot`` element and per-device boot elements
are mutually exclusive. :since:`Since 0.1.3, per-device boot since 0.8.8`
elements (see `Hard drives, floppy disks, CDROMs`_, `Network interfaces`_,
and `Host device assignment`_ sections below) were introduced and they are
the preferred way providing full control over booting order.
The ``boot`` element and per-device boot elements are mutually exclusive.
:since:`Since 0.1.3, per-device boot since 0.8.8`
``smbios``
How to populate SMBIOS information visible in the guest. The ``mode``
attribute must be specified, and is either "emulate" (let the hypervisor
@ -4441,7 +4441,6 @@ Each mode supports an optional sub-element ``<address>`` (See `Device Addresses`
which fine-tunes the correlation between the smartcard and a ccid bus controller.
For now, qemu only supports at most one smartcard, with an address of bus=0 slot=0.
:anchor:`<a id="elementsNICS"/>`
Network interfaces
~~~~~~~~~~~~~~~~~~

4
docs/formatnetwork.rst
View File

@ -61,7 +61,7 @@ The first elements provide basic metadata about the virtual network.
The optional parameter ``trustGuestRxFilters`` can be used to set that
attribute of the same name for each domain interface connected to this
network ( :since:`since 1.2.10` ). See the `Network
interfaces <formatdomain.html#elementsNICS>`__ section of the domain XML
interfaces <formatdomain.html#network-interfaces>`__ section of the domain XML
documentation for more details. Note that an explicit setting of this
attribute in a portgroup or the individual domain interface will override the
setting in the network.
@ -616,7 +616,7 @@ starting.
portgroups also support the optional parameter ``trustGuestRxFilters`` which can
be used to set that attribute of the same name for each domain interface using
this portgroup ( :since:`since 1.2.10` ). See the `Network
interfaces <formatdomain.html#elementsNICS>`__ section of the domain XML
interfaces <formatdomain.html#network-interfaces>`__ section of the domain XML
documentation for more details. Note that an explicit setting of this attribute
in the portgroup overrides the network-wide setting, and an explicit setting in
the individual domain interface will override the setting in the portgroup.

2
docs/formatnetworkport.rst
View File

@ -98,7 +98,7 @@ The following elements are common to one or more of the plug types listed later
``virtualport``
The ``virtualport`` element describes metadata that needs to be provided to
the underlying network subsystem. It is described in the domain XML
`interface documentation <formatdomain.html#elementsNICS>`__.
`interface documentation <formatdomain.html#network-interfaces>`__.
Plugs
~~~~~