Re: [libvirt] [PATCH v3 17/21] LXC from native: map vlan network type

2014-02-12 Thread Daniel P. Berrange
On Wed, Feb 05, 2014 at 03:10:15PM +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

Re: [libvirt] [PATCH v3 17/21] LXC from native: map vlan network type

2014-02-12 Thread Daniel P. Berrange
On Wed, Feb 05, 2014 at 03:10:15PM +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

[libvirt] [PATCH v3 17/21] LXC from native: map vlan network type

2014-02-05 Thread Cédric Bosdonnat
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