Re: [Lxc-users] lxc_namespace - failed to clone(0x6c020000): Invalid argument
On 06/01/2011 10:25 AM, Ulli Horlacher wrote: On Wed 2011-06-01 (10:18), Daniel Lezcano wrote: root@vms2:/lxc# lxc-start -f bunny.cfg -n bunny -d -o /dev/tty lxc-start 1306913218.901 ERRORlxc_namespace - failed to clone(0x6c02): Invalid argument Can you show the content of the /cgroup root directory please ? Any message in /var/log/messages ? -- Simplify data backup and recovery for your virtual environment with vRanger. Installation's a snap, and flexible recovery options mean your data is safe, secure and there when you need it. Data protection magic? Nope - It's vRanger. Get your free trial download today. http://p.sf.net/sfu/quest-sfdev2dev ___ Lxc-users mailing list Lxc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-users
Re: [Lxc-users] lxc_namespace - failed to clone(0x6c020000): Invalid argument
On Wed 2011-06-01 (10:30), Daniel Lezcano wrote: On 06/01/2011 10:25 AM, Ulli Horlacher wrote: On Wed 2011-06-01 (10:18), Daniel Lezcano wrote: root@vms2:/lxc# lxc-start -f bunny.cfg -n bunny -d -o /dev/tty lxc-start 1306913218.901 ERRORlxc_namespace - failed to clone(0x6c02): Invalid argument Can you show the content of the /cgroup root directory please ? Any message in /var/log/messages ? 2011-06-01 10:34:53 [ 5228.816214] device vetheBqcj5 entered promiscuous mode 2011-06-01 10:34:53 [ 5228.817240] ADDRCONF(NETDEV_UP): vetheBqcj5: link is not ready This is strange, because I have not configured vetheBqcj5. I use: root@vms2:/var/log# grep network /lxc/bunny.cfg lxc.network.type = veth lxc.network.link = br8 lxc.network.name = eth0 With: root@vms2:/var/log# cat /etc/network/interfaces auto lo iface lo inet loopback auto eth0 iface eth0 inet manual up ifconfig eth0 up auto br0 iface br0 inet static address 129.69.1.68 netmask 255.255.255.0 gateway 129.69.1.254 bridge_ports eth0 bridge_stp off bridge_maxwait 5 post-up /usr/sbin/brctl setfd br0 0 # VLAN8 auto eth2 iface eth2 inet manual up ifconfig eth2 up auto vlan8 iface vlan8 inet manual vlan_raw_device eth2 up ifconfig vlan8 up auto br8 iface br8 inet manual bridge_ports vlan8 bridge_maxwait 5 bridge_stp off post-up /usr/sbin/brctl setfd br8 0 root@vms2:/var/log# ifconfig br0 Link encap:Ethernet HWaddr 00:23:ae:6c:4f:cd inet addr:129.69.1.68 Bcast:129.69.1.255 Mask:255.255.255.0 inet6 addr: fe80::223:aeff:fe6c:4fcd/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:140360 errors:0 dropped:0 overruns:0 frame:0 TX packets:4288 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:10991449 (10.9 MB) TX bytes:631122 (631.1 KB) br8 Link encap:Ethernet HWaddr 00:e0:52:b7:37:fe inet6 addr: fe80::2e0:52ff:feb7:37fe/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:54832 errors:0 dropped:0 overruns:0 frame:0 TX packets:6 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:2654293 (2.6 MB) TX bytes:468 (468.0 B) eth0 Link encap:Ethernet HWaddr 00:23:ae:6c:4f:cd inet6 addr: fe80::223:aeff:fe6c:4fcd/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:154863 errors:0 dropped:0 overruns:0 frame:0 TX packets:4300 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:30994037 (30.9 MB) TX bytes:632223 (632.2 KB) Memory:fe9e-fea0 eth2 Link encap:Ethernet HWaddr 00:e0:52:b7:37:fe inet6 addr: fe80::2e0:52ff:feb7:37fe/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:55625 errors:0 dropped:0 overruns:0 frame:0 TX packets:12 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:3513414 (3.5 MB) TX bytes:936 (936.0 B) Interrupt:18 Base address:0x8f00 loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:152 errors:0 dropped:0 overruns:0 frame:0 TX packets:152 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:12394 (12.3 KB) TX bytes:12394 (12.3 KB) veth80Eh90 Link encap:Ethernet HWaddr 3a:ce:cf:67:68:55 UP BROADCAST PROMISC MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) veth9NBAU3 Link encap:Ethernet HWaddr 2a:00:8d:c1:1f:98 UP BROADCAST PROMISC MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) vethO3dr66 Link encap:Ethernet HWaddr 62:05:7b:53:4d:07 UP BROADCAST PROMISC MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) vethORKGHz Link encap:Ethernet HWaddr 0e:b6:91:af:d2:9d UP BROADCAST PROMISC MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0
Re: [Lxc-users] lxc_namespace - failed to clone(0x6c020000): Invalid argument
On 06/01/2011 10:45 AM, Ulli Horlacher wrote: [ ... ] 2011-06-01 10:34:53 [ 5228.816214] device vetheBqcj5 entered promiscuous mode 2011-06-01 10:34:53 [ 5228.817240] ADDRCONF(NETDEV_UP): vetheBqcj5: link is not ready This is strange, because I have not configured vetheBqcj5. It is configured by lxc automatically. No worries. Oh ! As far as I remember the ubuntu kernel team disabled the network namespace in the kernel. Can you check that with lxc-checkconfig ? Thanks -- Daniel -- Simplify data backup and recovery for your virtual environment with vRanger. Installation's a snap, and flexible recovery options mean your data is safe, secure and there when you need it. Data protection magic? Nope - It's vRanger. Get your free trial download today. http://p.sf.net/sfu/quest-sfdev2dev ___ Lxc-users mailing list Lxc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-users
Re: [Lxc-users] lxc_namespace - failed to clone(0x6c020000): Invalid argument
On 06/01/2011 11:17 AM, Daniel Lezcano wrote: On 06/01/2011 10:45 AM, Ulli Horlacher wrote: [ ... ] 2011-06-01 10:34:53 [ 5228.816214] device vetheBqcj5 entered promiscuous mode 2011-06-01 10:34:53 [ 5228.817240] ADDRCONF(NETDEV_UP): vetheBqcj5: link is not ready This is strange, because I have not configured vetheBqcj5. It is configured by lxc automatically. No worries. Oh ! As far as I remember the ubuntu kernel team disabled the network namespace in the kernel. Can you check that with lxc-checkconfig ? Daniel, I use Natty (11.04) and in it's enabled: $ lxc-checkconfig Kernel config /proc/config.gz not found, looking in other places... Found kernel config file /boot/config-2.6.38-8-server --- Namespaces --- Namespaces: enabled Utsname namespace: enabled Ipc namespace: enabled Pid namespace: enabled User namespace: enabled Network namespace: enabled Multiple /dev/pts instances: enabled --- Control groups --- Cgroup: enabled Cgroup namespace: enabled Cgroup device: enabled Cgroup sched: enabled Cgroup cpu account: enabled Cgroup memory controller: enabled Cgroup cpuset: enabled --- Misc --- Veth pair device: enabled Macvlan: enabled Vlan: enabled File capabilities: enabled Note : Before booting a new kernel, you can check its configuration usage : CONFIG=/path/to/config /usr/bin/lxc-checkconfig Just FYI. tamas -- Simplify data backup and recovery for your virtual environment with vRanger. Installation's a snap, and flexible recovery options mean your data is safe, secure and there when you need it. Data protection magic? Nope - It's vRanger. Get your free trial download today. http://p.sf.net/sfu/quest-sfdev2dev ___ Lxc-users mailing list Lxc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-users
Re: [Lxc-users] lxc_namespace - failed to clone(0x6c020000): Invalid argument
On Wed 2011-06-01 (11:17), Daniel Lezcano wrote: On 06/01/2011 10:45 AM, Ulli Horlacher wrote: [ ... ] 2011-06-01 10:34:53 [ 5228.816214] device vetheBqcj5 entered promiscuous mode 2011-06-01 10:34:53 [ 5228.817240] ADDRCONF(NETDEV_UP): vetheBqcj5: link is not ready This is strange, because I have not configured vetheBqcj5. It is configured by lxc automatically. No worries. Ahh.. ok :-) Oh ! As far as I remember the ubuntu kernel team disabled the network namespace in the kernel. Can you check that with lxc-checkconfig ? root@vms2:~# lxc-checkconfig Kernel config /proc/config.gz not found, looking in other places... Found kernel config file /boot/config-2.6.32-32-server --- Namespaces --- Namespaces: enabled Utsname namespace: enabled Ipc namespace: enabled Pid namespace: enabled User namespace: enabled Network namespace: missing ^^ A! Can I enable it at runtime or is it a compile time feature? -- Ullrich Horlacher Server- und Arbeitsplatzsysteme Rechenzentrum E-Mail: horlac...@rus.uni-stuttgart.de Universitaet Stuttgart Tel:++49-711-685-65868 Allmandring 30 Fax:++49-711-682357 70550 Stuttgart (Germany) WWW:http://www.rus.uni-stuttgart.de/ -- Simplify data backup and recovery for your virtual environment with vRanger. Installation's a snap, and flexible recovery options mean your data is safe, secure and there when you need it. Data protection magic? Nope - It's vRanger. Get your free trial download today. http://p.sf.net/sfu/quest-sfdev2dev ___ Lxc-users mailing list Lxc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-users
Re: [Lxc-users] lxc_namespace - failed to clone(0x6c020000): Invalid argument
On 06/01/2011 11:55 AM, Papp Tamas wrote: On 06/01/2011 11:17 AM, Daniel Lezcano wrote: On 06/01/2011 10:45 AM, Ulli Horlacher wrote: [ ... ] 2011-06-01 10:34:53 [ 5228.816214] device vetheBqcj5 entered promiscuous mode 2011-06-01 10:34:53 [ 5228.817240] ADDRCONF(NETDEV_UP): vetheBqcj5: link is not ready This is strange, because I have not configured vetheBqcj5. It is configured by lxc automatically. No worries. Oh ! As far as I remember the ubuntu kernel team disabled the network namespace in the kernel. Can you check that with lxc-checkconfig ? Daniel, I use Natty (11.04) and in it's enabled: Yep, it is only a 2.6.32 kernel which is concerned by this modification. What I meant is the kernel team just disabled the netns with an update in 2.6.32 https://lists.ubuntu.com/archives/kernel-team/2011-March/015173.html That looked very weird for me. I tried to convince them the netns was needed but they decided to remove a kernel feature in a kernel update. :s -- Simplify data backup and recovery for your virtual environment with vRanger. Installation's a snap, and flexible recovery options mean your data is safe, secure and there when you need it. Data protection magic? Nope - It's vRanger. Get your free trial download today. http://p.sf.net/sfu/quest-sfdev2dev ___ Lxc-users mailing list Lxc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-users
Re: [Lxc-users] lxc_namespace - failed to clone(0x6c020000): Invalid argument
On 06/01/2011 12:25 PM, Ulli Horlacher wrote: On Wed 2011-06-01 (11:17), Daniel Lezcano wrote: On 06/01/2011 10:45 AM, Ulli Horlacher wrote: [ ... ] 2011-06-01 10:34:53 [ 5228.816214] device vetheBqcj5 entered promiscuous mode 2011-06-01 10:34:53 [ 5228.817240] ADDRCONF(NETDEV_UP): vetheBqcj5: link is not ready This is strange, because I have not configured vetheBqcj5. It is configured by lxc automatically. No worries. Ahh.. ok :-) Oh ! As far as I remember the ubuntu kernel team disabled the network namespace in the kernel. Can you check that with lxc-checkconfig ? root@vms2:~# lxc-checkconfig Kernel config /proc/config.gz not found, looking in other places... Found kernel config file /boot/config-2.6.32-32-server --- Namespaces --- Namespaces: enabled Utsname namespace: enabled Ipc namespace: enabled Pid namespace: enabled User namespace: enabled Network namespace: missing ^^ A! Can I enable it at runtime or is it a compile time feature? It is a compile feature :( But you can install a more recent kernel as suggested in the kernel team email thread. https://lists.ubuntu.com/archives/kernel-team/2011-March/015173.html Well, there is an alternative for those folks that _are_ dependent on NET_NS: sudo apt-get install linux-image-server-lts-backport-maverick -- Simplify data backup and recovery for your virtual environment with vRanger. Installation's a snap, and flexible recovery options mean your data is safe, secure and there when you need it. Data protection magic? Nope - It's vRanger. Get your free trial download today. http://p.sf.net/sfu/quest-sfdev2dev ___ Lxc-users mailing list Lxc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-users
Re: [Lxc-users] lxc_namespace - failed to clone(0x6c020000): Invalid argument
On 06/01/2011 03:06 PM, Ulli Horlacher wrote: On Wed 2011-06-01 (14:40), Daniel Lezcano wrote: root@vms2:~# lxc-checkconfig Kernel config /proc/config.gz not found, looking in other places... Found kernel config file /boot/config-2.6.32-32-server --- Namespaces --- Namespaces: enabled Utsname namespace: enabled Ipc namespace: enabled Pid namespace: enabled User namespace: enabled Network namespace: missing ^^ A! Can I enable it at runtime or is it a compile time feature? It is a compile feature :( Bad... https://lists.ubuntu.com/archives/kernel-team/2011-March/015173.html Well, there is an alternative for those folks that _are_ dependent on NET_NS: sudo apt-get install linux-image-server-lts-backport-maverick With this workaround my LXC containers are working again! Thanks! Nevertheless this IS an (Ubuntu) bug! Both packages, lxc and linux-image belong to the same Ubuntu (LTS!) version and should work together! I will file a bug-report at launchpad.net I fully agree with you. Disabling a feature in the kernel for an update to fix a bug is not a solution. -- Simplify data backup and recovery for your virtual environment with vRanger. Installation's a snap, and flexible recovery options mean your data is safe, secure and there when you need it. Data protection magic? Nope - It's vRanger. Get your free trial download today. http://p.sf.net/sfu/quest-sfdev2dev ___ Lxc-users mailing list Lxc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-users
