From aab0470f0d7ce1ef8a183e6f3c32f70f0eac6a30 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Daniel=20P=2E=20Berrang=C3=A9?=
This provides an isolated bridge device (ie no physical NICs
- enslaved). Guest TAP devices are attached to this bridge.
+ attached). Guest TAP devices are attached to this bridge.
Guests can talk to each other and the host, and optionally the
wider world.
@@ -46,7 +46,7 @@
Thus the virtual network driver in libvirt was invented. This takes the form of an isolated bridge device (ie one with no physical NICs - enslaved). The TAP devices associated with the guest NICs are attached + attached). The TAP devices associated with the guest NICs are attached to the bridge device. This immediately allows guests on a single host to talk to each other and to the host OS (modulo host IPtables rules).
diff --git a/docs/formatdomain.html.in b/docs/formatdomain.html.in index bd662727d3..562bd3e538 100644 --- a/docs/formatdomain.html.in +++ b/docs/formatdomain.html.in @@ -5785,11 +5785,11 @@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 enslaved. The guest VM will have an associated tun device + physical NICs 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 the target element). - The tun device will be enslaved to the bridge. The IP range / network + The tun device will be 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 like a physical machine.