From 07450cd42951d5007ab28d8e522f65d948181674 Mon Sep 17 00:00:00 2001
From: Laine Stump
There are several possibilities for specifying a network
interface visible to the guest. Each subsection below provides
- more details about common setup options. Additionally,
- each
+ Since 1.2.10),
+ the
+ Each
+ If the model type is set to
...
<devices>
- <interface type='bridge'>
- <source bridge='xenbr0'/>
- <mac address='00:16:3e:5d:c7:9e'/>
- <script path='vif-bridge'/>
+ <interface type='direct' trustGuestRxFilters='yes'>
+ <source dev='eth0'/>
+ <mac address='52:54:00:5d:c7:9e'/>
<boot order='1'/>
<rom bar='off'/>
</interface>
@@ -3356,8 +3355,23 @@
<interface>
element has an
+ more details about common setup options.
+ interface
element
+ property trustGuestRxFilters
provides the
+ capability for the host to detect and trust reports from the
+ guest regarding changes to the interface mac address and receive
+ filters by setting the attribute to yes
. The default
+ setting for the attribute is no
for security
+ reasons and support depends on the guest network device model as
+ well as the type of connection on the host - currently it is
+ only supported for the virtio ddevice model and for macvtap
+ connections on the host.
+ <interface>
element has an
optional <address>
sub-element that can tie
the interface to a particular pci slot, with
attribute type='pci'
@@ -3589,6 +3603,18 @@
being the default mode. The individual modes cause the delivery of
packets to behave as follows:
virtio
and
+ interface's trustGuestRxFilters
attribute is set
+ to yes
, changes made to the interface mac address,
+ unicast/multicast receive filters, and vlan settings in the
+ guest will be monitored and propagated to the associated macvtap
+ device on the host (Since
+ 1.2.10). If trustGuestRxFilters
is not set,
+ or is not supported for the device model in use, an attempted
+ change to the mac address originating from the guest side will
+ result in a non-working network connection.
+
vepa
- <network ipv6='yes'> + <network ipv6='yes' trustGuestRxFilters='no'> <name>default</name> <uuid>3e3fce45-4f53-4fa7-bb32-11f34168b82b</uuid> ...@@ -60,6 +60,16 @@ to have guest-to-guest communications. For further information, see the example below for the example with no gateway addresses. Since 1.0.1 +
trustGuestRxFilters='yes'
trustGuestRxFilters
can
+ be used to set that attribute of the same name for each domain
+ interface connected to this network (since
+ 1.2.10). See
+ the 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.<bandwidth>
(described here)
and <virtualport>
@@ -650,6 +660,19 @@
considered an error, and will prevent the interface from
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
+ 1.2.10). See
+ the 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.
+
diff --git a/docs/schemas/domaincommon.rng b/docs/schemas/domaincommon.rng
index 6b69fd1bac..20d81ae2d6 100644
--- a/docs/schemas/domaincommon.rng
+++ b/docs/schemas/domaincommon.rng
@@ -2240,6 +2240,11 @@
+