diff --git a/docs/formatdomain.html.in b/docs/formatdomain.html.in index 14d237198ab518da3c97ae38464d20878437bd43..9041cc6a507873dc6c15abde801f61ac9930d379 100644 --- a/docs/formatdomain.html.in +++ b/docs/formatdomain.html.in @@ -742,11 +742,34 @@

Provides direct attachment of the virtual machine's NIC to the given physial interface of the host. This setup requires the Linux macvtap - driver to be available. One of the modes 'vepa', 'bridge' or 'private' + driver to be available. One of the modes 'vepa' + ( + 'Virtual Ethernet Port Aggregator'), 'bridge' or 'private' can be chosen for the operation mode of the macvtap device, 'vepa' - being the default mode. + being the default mode. The individual modes cause the delivery of + packets to behave as follows:

+
+
vepa
+
All VMs' packets are sent to the external bridge. Packets + whose destination is a VM on the same host as where the + packet originates from are sent back to the host by the VEPA + capable bridge (today's bridges are typically not VEPA capable).
+
bridge
+
Packets whose destination is on the same host as where they + originate from are directly delivered to the target macvtap device. + Both origin and destination devices need to be in bridge mode + for direct delivery. If either one of them is in vepa mode, + a VEPA capable bridge is required. +
private
+
All packets are sent to the external bridge and will only be + delivered to a target VM on the same host if they are sent through an + external router or gateway and that device sends them back to the + host. This procedure is followed if either the source or destination + device is in private mode.
+
+
   ...
   <devices>