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)`
-This setup requires the Linux macvtap driver to be available. :since:`(Since
-Linux 2.6.34.)` One of the modes 'vepa' ( `'Virtual Ethernet Port
+This setup requires the Linux macvtap driver (introduced in 2.6.34)
+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>`__),
'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
bridge (in particular, the port attaching the bridge to the physical
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
- not supported by older kernels. :since:`Since 1.2.11, requires kernel 3.17 or
- newer`
+ not supported by kernels older than 3.17. :since:`Since 1.2.11`
The optional ``zone`` attribute of the ``bridge`` element is used to specify
the `firewalld <https://firewalld.org>`__ zone for the bridge of a network
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
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