What it can be? # uname -a Linux server.vs 2.6.8-022stab070-up #4 Thu Feb 23 20:39:22 MSK 2006 i686 i686 i386 GNU/Linux # rpm -qa | grep vzctl vzctl-lib-3.0.0-2 vzctl-3.0.0-2 # date Fri Feb 24 01:46:25 MSK 2006 # vzctl --verbose start 105 Unable to open /usr/lib/vzctl/modules/: No such file or directory Warning: configuration file for distribution trustix.3 not found default used Starting VPS ... Running: /usr/sbin/vzquota show 105 Running: /usr/sbin/vzquota on 105 -r 0 -b 1048676 -B 1153534 -i 200100 -I 220100 -e 0 -n 0 -s 0 Mounting root: /run/vz/root/105 /run/vz/private/105 VPS is mounted Running: /usr/sbin/vzquota stat 105 -f Running: vzquota setlimit 105 -b 1048576 -B 1153434 -i 200000 -I 220000 -e 0 -n 0 Adding IP address(es): 10.0.5.10 Running: /usr/lib/vzctl/scripts/vps-net_add Running VPS script: /etc/sysconfig/vz-scripts/dists/scripts/redhat-add_ip.sh FATAL: kernel too old Setting CPU units: 1000 Set hostname: shell.vs Running VPS script: /etc/sysconfig/vz-scripts/dists/scripts/redhat-set_hostname.sh FATAL: kernel too old VPS start in progress... root@server /run/vz/private/111/etc# FATAL: kernel too old root@server ~# vzctl enter 105 entered into VPS 105 FATAL: kernel too old exited from VPS 105 # vzctl stop 105 Stopping VPS ... Unable to stop VPS, operation timed out
Can you please try older vzctl version? Say, latest 2.7.0-x, and please report if it works or not. This is probably a bug in vzctl due to latest changes, we will try to find it out as soon as next Monday.
I reboot (reset ) in older kernel and make downgrade of vzctl. Start and stop all vpses. After what I rebootin new kernel, upgrade vzctl till newest version, and now it works.
I apologize. I have found a source of a problem. It has begun, when I have made the following: #echo 'FreeBSD 4.10-RELEASE-p2' > /proc/sys/kernel/virt_osrelease In this connection a question. Whether it is possible to use it, and if yes, how? From changelog of 2.6.8-022stab070.1: diff-ve-virt-osrelease-20060220 Patch from Alexander, modified by Denis: This patch virtualizes kernel version in `uname -a` and VPS /proc/version. it is inherited on VPS start from /proc/sys/kernel/virt_osrelease
It is possible to use this, but ELF loader checks kernel version to make sure that executables are compatible with kernel ABI. So you cannot write _any_ arbitrary text to this variable It should be something like "2.x...". For example, it should work fine with "2.6.8", "2.6.x-any-text", "2.4.X-..." and so on. You can write "2.6.x FreeBSD 4.10-RELEASE-p"
Just another question. Is it ok, what in vps'es we have both, and virt_osrelease and osrelease sysctl variables? # sysctl -a | grep osrelease error: "Invalid argument" reading key "net.ipv4.route.flush" error: "Operation not permitted" reading key "kernel.cap-bound" kernel.virt_osrelease = 2.6.18 kernel.osrelease = 2.6.8-022stab078-up `uname -r` get his value from kernel.virt_osrelease, but I can just look right version of kernel from sysctl...
I realy thought what 've0 kernel.virt_osrelease' = 'vps* kernel.osrelease.'
this feature was added not to fake people and make them believe they have different kernel, but rather some applications/glibc.