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

docs: Leave kernel version out of :since:

Browse Source 
Tweak things so that the required kernel version is still
listed, just not as part of the :since: tag.

Signed-off-by: Andrea Bolognani <abologna@redhat.com>
Reviewed-by: Michal Privoznik <mprivozn@redhat.com>
This commit is contained in:
Andrea Bolognani 2024-02-19 18:26:08 +01:00
parent f80dc130ed
commit e833c3d122
2 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/formatdomain.rst
View File

@ -5119,8 +5119,8 @@ Direct attachment to physical interface
Provides direct attachment of the virtual machine's NIC to the given physical Provides direct attachment of the virtual machine's NIC to the given physical
interface of the host. :since:`Since 0.7.7 (QEMU and KVM only)` interface of the host. :since:`Since 0.7.7 (QEMU and KVM only)`
This setup requires the Linux macvtap driver to be available. :since:`(Since This setup requires the Linux macvtap driver (introduced in 2.6.34)
Linux 2.6.34.)` One of the modes 'vepa' ( `'Virtual Ethernet Port to be available. One of the modes 'vepa' ( `'Virtual Ethernet Port
Aggregator' <https://www.ieee802.org/1/files/public/docs2009/new-evb-congdon-vepa-modular-0709-v01.pdf>`__), Aggregator' <https://www.ieee802.org/1/files/public/docs2009/new-evb-congdon-vepa-modular-0709-v01.pdf>`__),
'bridge' or 'private' can be chosen for the operation mode of the macvtap 'bridge' or 'private' can be chosen for the operation mode of the macvtap
device, 'vepa' being the default mode. The individual modes cause the delivery device, 'vepa' being the default mode. The individual modes cause the delivery

6
docs/formatnetwork.rst
View File

@ -127,8 +127,7 @@ to the physical LAN (if at all).
bridge (in particular, the port attaching the bridge to the physical bridge (in particular, the port attaching the bridge to the physical
network). However, it can also cause some networking setups to stop working network). However, it can also cause some networking setups to stop working
(e.g. vlan tagging, multicast, guest-initiated changes to MAC address) and is (e.g. vlan tagging, multicast, guest-initiated changes to MAC address) and is
not supported by older kernels. :since:`Since 1.2.11, requires kernel 3.17 or not supported by kernels older than 3.17. :since:`Since 1.2.11`
newer`
The optional ``zone`` attribute of the ``bridge`` element is used to specify The optional ``zone`` attribute of the ``bridge`` element is used to specify
the `firewalld <https://firewalld.org>`__ zone for the bridge of a network the `firewalld <https://firewalld.org>`__ zone for the bridge of a network
@ -1110,7 +1109,8 @@ will be no restrictions on inbound or outbound connections).
Using a macvtap "direct" connection Using a macvtap "direct" connection
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:since:`Since 0.9.4, QEMU and KVM only, requires Linux kernel 2.6.34 or newer` :since:`Since 0.9.4, QEMU and KVM only`. Requires Linux kernel 2.6.34 or newer.
This shows how to use macvtap to connect to the physical network directly This shows how to use macvtap to connect to the physical network directly
through one of a group of physical devices (without using a host bridge device). through one of a group of physical devices (without using a host bridge device).
As with the host bridge network, the guests will effectively be directly As with the host bridge network, the guests will effectively be directly