diff options
author | Laine Stump <laine@laine.org> | 2012-08-12 03:51:30 -0400 |
---|---|---|
committer | Laine Stump <laine@laine.org> | 2012-08-15 13:10:57 -0400 |
commit | 3f9274a524804f8aa59c811932dba56550c120a1 (patch) | |
tree | 348bf52bf88261864e7a4bcb1450d62f50d7b5c7 /tests/networkxml2xmlin/openvswitch-net.xml | |
parent | util: add virNetDevVlanType (diff) | |
download | libvirt-3f9274a524804f8aa59c811932dba56550c120a1.tar.gz libvirt-3f9274a524804f8aa59c811932dba56550c120a1.tar.bz2 libvirt-3f9274a524804f8aa59c811932dba56550c120a1.zip |
conf: add <vlan> element to network and domain interface elements
The following config elements now support a <vlan> subelements:
within a domain: <interface>, and the <actual> subelement of <interface>
within a network: the toplevel, as well as any <portgroup>
Each vlan element must have one or more <tag id='n'/> subelements. If
there is more than one tag, it is assumed that vlan trunking is being
requested. If trunking is required with only a single tag, the
attribute "trunk='yes'" should be added to the toplevel <vlan>
element.
Some examples:
<interface type='hostdev'/>
<vlan>
<tag id='42'/>
</vlan>
<mac address='52:54:00:12:34:56'/>
...
</interface>
<network>
<name>vlan-net</name>
<vlan trunk='yes'>
<tag id='30'/>
</vlan>
<virtualport type='openvswitch'/>
</network>
<interface type='network'/>
<source network='vlan-net'/>
...
</interface>
<network>
<name>trunk-vlan</name>
<vlan>
<tag id='42'/>
<tag id='43'/>
</vlan>
...
</network>
<network>
<name>multi</name>
...
<portgroup name='production'/>
<vlan>
<tag id='42'/>
</vlan>
</portgroup>
<portgroup name='test'/>
<vlan>
<tag id='666'/>
</vlan>
</portgroup>
</network>
<interface type='network'/>
<source network='multi' portgroup='test'/>
...
</interface>
IMPORTANT NOTE: As of this patch there is no backend support for the
vlan element for *any* network device type. When support is added in
later patches, it will only be for those select network types that
support setting up a vlan on the host side, without the guest's
involvement. (For example, it will be possible to configure a vlan for
a guest connected to an openvswitch bridge, but it won't be possible
to do that for one that is connected to a standard Linux host bridge.)
Diffstat (limited to 'tests/networkxml2xmlin/openvswitch-net.xml')
-rw-r--r-- | tests/networkxml2xmlin/openvswitch-net.xml | 8 |
1 files changed, 8 insertions, 0 deletions
diff --git a/tests/networkxml2xmlin/openvswitch-net.xml b/tests/networkxml2xmlin/openvswitch-net.xml index 8aa1897ab..a3d82b165 100644 --- a/tests/networkxml2xmlin/openvswitch-net.xml +++ b/tests/networkxml2xmlin/openvswitch-net.xml @@ -4,11 +4,19 @@ <forward mode='bridge'/> <virtualport type='openvswitch'/> <portgroup name='bob' default='yes'> + <vlan trunk='yes'> + <tag id='666'/> + </vlan> <virtualport> <parameters profileid='bob-profile'/> </virtualport> </portgroup> <portgroup name='alice'> + <vlan trunk='yes'> + <tag id='777'/> + <tag id='888'/> + <tag id='999'/> + </vlan> <virtualport> <parameters profileid='alice-profile'/> </virtualport> |