You don't mention what kernel you are using, but this is probably due to the maturity of your kernel; for example, the RHEL6 2.6.32 kernel does not allow movement of physical devices into a network namespace. As a test, try creating a VLAN device on your eth3, and configure your container to use that device.
As a workaround, you could leave eth3 in the default namespace, attach it to a bridge in the default namespace, create a veth pair, attach one of the veths to your bridge, and push the other into your container. A bit of work and overhead, but otherwise you may be looking at a kernel upgrade. E On Sat, Feb 5, 2011 at 6:32 AM, pmenier <patr...@pmenier.dynalias.net> wrote: > Hello all > > Using lxc since many months, i decided to add a network card on my host. I > thought it could be assigned to the lxc-guests i will create later. > > But ... it doesn't work. > > when i try to start the container i get this error: > > root@p733:/opt/lxc/vm1733# lxc-start -n vm1733 -d -o /tmp/outvm1733 > > root@p733:/opt/lxc/vm1733# cat /tmp/outvm1733 > lxc-start 1296908902.660 ERROR lxc_conf - failed to move 'eth3' to > the > container : Invalid argument > lxc-start 1296908902.660 ERROR lxc_start - failed to create the > configured network > lxc-start 1296908902.660 ERROR lxc_start - failed to spawn 'vm1733' > > eth3 exists on the hosts (3 because i tried with another card before) > > Here the guest config: > > root@p733:/opt/lxc/vm1733# cat config > # Container with network virtualized using a physical network device with name > lxc.utsname = vm1733 > lxc.network.type = phys > lxc.network.flags = up > lxc.network.link = eth3 > lxc.network.name = eth0 > #lxc.network.hwaddr = 01:50:fc:45:6e:35 > lxc.network.ipv4 = 192.168.0.69/24 > > This guest works fine with config veth (lxc.network.link= br0) but i should > like to understand... > > Thanks > Patrick > > > ------------------------------------------------------------------------------ > The modern datacenter depends on network connectivity to access resources > and provide services. The best practices for maximizing a physical server's > connectivity to a physical network are well understood - see how these > rules translate into the virtual world? > http://p.sf.net/sfu/oracle-sfdevnlfb > _______________________________________________ > Lxc-users mailing list > Lxc-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/lxc-users > -- E ------------------------------------------------------------------------------ The modern datacenter depends on network connectivity to access resources and provide services. The best practices for maximizing a physical server's connectivity to a physical network are well understood - see how these rules translate into the virtual world? http://p.sf.net/sfu/oracle-sfdevnlfb _______________________________________________ Lxc-users mailing list Lxc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-users