On Thu, Jan 30, 2014 at 10:56:05AM +0100, Cédric Bosdonnat wrote: > The problem with VLAN is that the user still has to manually create the > vlan interface on the host. Then the generated configuration will use > it as a nerwork hostdev device. So the generated configurations of the > following two fragments are equivalent (see rhbz#1059637). > > lxc.network.type = phys > lxc.network.link = eth0.5 > > lxc.network.type = vlan > lxc.network.link = eth0 > lxc.network.vlan.id = 5 > --- > src/lxc/lxc_native.c | 28 ++++++++++++++++++---- > .../lxcconf2xmldata/lxcconf2xml-vlannetwork.config | 12 ++++++++++ > tests/lxcconf2xmldata/lxcconf2xml-vlannetwork.xml | 26 ++++++++++++++++++++ > tests/lxcconf2xmltest.c | 1 + > 4 files changed, 62 insertions(+), 5 deletions(-) > create mode 100644 tests/lxcconf2xmldata/lxcconf2xml-vlannetwork.config > create mode 100644 tests/lxcconf2xmldata/lxcconf2xml-vlannetwork.xml ACK Daniel -- |: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :| |: http://libvirt.org -o- http://virt-manager.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :| -- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list