Container start failure when ipv6 is disabled [message #38584] |
Tue, 05 January 2010 16:16 ![Go to next message Go to next message](/theme/ovz3/images/down.png) |
tdaniel
Messages: 2 Registered: January 2010 Location: Romania
|
Junior Member |
|
|
Hello,
I am a long time user of OpenVZ. I've setup a new machine for which I disabled ipv6 support in order to troubleshoot some OpenVZ unrelated networking issues and I stumbled on a problem.
If ipv6 support is completely disabled using the modprobe.d approach, containers fail to start.
If the following option is entered in a file under /etc/modprobe.d
Containers fail to start with the following dmesg output:
CT: 170: failed to start with err=-12
CT: 110: stopped
kmem_cache_create: duplicate cache ndisc_cache
Call Trace:
[<ffffffff8003aa8d>] kmem_cache_create+0x5e8/0x624
[<ffffffff80229ce9>] neigh_table_init_no_netlink+0x8d/0x37a
[<ffffffff80226a89>] neigh_sysctl_register+0x241/0x275
[<ffffffff80229fe4>] neigh_table_init+0xe/0x90
[<ffffffff8836689f>] :ipv6:ve_ndisc_init+0x6f/0xeb
[<ffffffff883c4446>] :vzmon:do_env_create+0x951/0xded
[<ffffffff883c4e74>] :vzmon:vzcalls_ioctl+0x2b8/0x5ee
[<ffffffff8828516f>] :vzdev:vzctl_ioctl+0x34/0x50
[<ffffffff800437fa>] do_ioctl+0x21/0x6b
[<ffffffff80031181>] vfs_ioctl+0x457/0x4b9
[<ffffffff800c00a0>] audit_syscall_entry+0x180/0x1b3
[<ffffffff8004eaee>] sys_ioctl+0x3c/0x5c
[<ffffffff800602dd>] tracesys+0xd5/0xe0
My setup is as follows:
OS:
Kernel:
2.6.18-164.2.1.el5.028stab066.10 #1 SMP Sat Dec 12 18:52:53 MSK 2009 x86_64 x86_64 x86_64 GNU/Linux
Tools:
vzquota-3.0.12-1
vzctl-lib-3.0.23-1
vzctl-3.0.23-1
There is no problem if NETWORKING_IPV6=no is set in /etc/sysconfig/network so i think this is a bug or something.
If i remove the /etc/modprobe.d file containing the ipv6 disable=1 option and reboot the system containers start to function as usual.
|
|
|
|
|
|
|