On Fri, Jan 24, 2014 at 03:24:19PM +0100, Cedric Bosdonnat wrote:
On Fri, 2014-01-24 at 13:58 +0000, Daniel P. Berrange wrote:
> On Tue, Jan 14, 2014 at 02:50:05PM +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.
> >
> > lxc.network.type = phys
> > lxc.network.link = eth0.5
> >
> > lxc.network.type = vlan
> > lxc.network.link = eth0
> > lxc.network.vlan.id = 5
>
> How does LXC deal with VLAN devices listed like this ? Would it
> automatically create the eth0.5 device in the second example ?
Yes, LXC automatically creates the eth0.5 in such a case. May be another
RFE to file or patch?
Yeah, probably worth an RFE
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 :|