Article ID: 113446, created on Mar 12, 2012, last review on Aug 12, 2014

  • Applies to:
  • Virtuozzo containers for Linux 4.7
  • Virtuozzo containers for Linux 4.6
  • Virtuozzo containers for Linux 4.0


If you try to start containers based on an old Linux distribution like Fedora Core 1, Debian 3.0, etc., on a recent PVC kernel, behavior similar to that displayed below could be observed:
[root@hwnode ~]# vzctl start 103
Starting the Container ...
Container is mounted
Setting permissions 20002 dev 0x7d00
Set up ioprio: 7
Set up iolimit: 0
Adding IP addresses:
Received signal 11
Hostname of the Container set: mycontainer.tld
Received signal 11
Received signal 11
File resolv.conf was modified
Container is unmounted
Failed to start the Container
[root@hwnode ~]#


Older versions of glibc used by those distributions do not work correctly if Virtual Dynamically-linked Shared Objects support is enabled in the kernel.


The resolution is to use supported and up-to-date distributions for containers on a newer version of the kernel.

The workaround is to disable vdso for the PVC kernel:
1. Add vm.vdso_enabled=0 to sysctl.conf to preserve changes after the reboot:
~# sysctl vm.vdso_enabled=0 >> /etc/sysctl.conf

2. Add abi.vsyscall32=0 to sysctl.conf to preserve changes after the reboot:
~# sysctl abi.vsyscall32=0 >> /etc/sysctl.conf

3. Apply these settings on the current kernel:
~# echo 0 > /proc/sys/vm/vdso_enabled
~# echo 0 > /proc/sys/abi/vsyscall32

36627b12981f68a16405a79233409a5e d02f9caf3e11b191a38179103495106f e8e50b42231236b82df27684e7ec0beb 35c16f1fded8e42577cb3df16429c57a 0c05f0c76fec3dd785e9feafce1099a9 2897d76d56d2010f4e3a28f864d69223

Email subscription for changes to this article
Save as PDF