libvirt/tests/networkxml2xmlin
Laine Stump 3f9274a524 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.)
2012-08-15 13:10:57 -04:00
..
8021Qbh-net.xml conf: add <vlan> element to network and domain interface elements 2012-08-15 13:10:57 -04:00
bandwidth-network.xml bandwidth: Add test cases for network 2011-07-25 13:50:06 +08:00
direct-net.xml conf: support abstracted interface info in network XML 2011-07-21 14:46:53 -04:00
host-bridge-net.xml conf: support abstracted interface info in network XML 2011-07-21 14:46:53 -04:00
isolated-network.xml Give each virtual network bridge its own fixed MAC address 2011-02-17 13:36:32 -05:00
nat-network-dns-hosts.xml Network: Add support for DNS hosts definition to the network XML 2011-06-24 16:15:36 -04:00
nat-network-dns-srv-record-minimal.xml Implement DNS SRV record into the bridge driver 2012-01-02 23:05:55 +08:00
nat-network-dns-srv-record.xml Implement DNS SRV record into the bridge driver 2012-01-02 23:05:55 +08:00
nat-network-dns-txt-record.xml Add TXT record support for virtual DNS service 2011-06-24 16:15:12 -04:00
nat-network.xml Change virtual network XML parsing/formatting to support IPv6 2010-12-23 15:53:55 -05:00
netboot-network.xml tests: Add network XML to XML tests. 2009-10-16 10:52:26 -04:00
netboot-proxy-network.xml Add support for an external TFTP boot server 2009-10-28 15:57:49 +01:00
openvswitch-net.xml conf: add <vlan> element to network and domain interface elements 2012-08-15 13:10:57 -04:00
passthrough-pf.xml Adding the element pf to network xml. 2012-01-11 13:10:21 -07:00
routed-network.xml Give each virtual network bridge its own fixed MAC address 2011-02-17 13:36:32 -05:00
vepa-net.xml conf: support partially-specified <virtualport> in parser and formatter 2012-08-14 15:47:50 -04:00