OpenVZ Forum: Support » virt

Home » General » Support » virt_osrelease

Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend

virt_osrelease [message #1783]

Thu, 23 February 2006 22:49

Valmont
Messages: 225
Registered: September 2005

Senior Member

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

[Updated on: Wed, 30 August 2006 14:05]

Report message to a moderator

Re: FATAL: kernel too old [message #1788 is a reply to message #1783]

Fri, 24 February 2006 03:33

kir
Messages: 1645
Registered: August 2005
Location: Moscow, Russia

Senior Member

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.

Kir Kolyshkin

http://static.openvz.org/userbars/openvz-developer.png

Report message to a moderator

Re: FATAL: kernel too old [message #1792 is a reply to message #1783]

Fri, 24 February 2006 10:25

Valmont
Messages: 225
Registered: September 2005

Senior Member

I reboot (reset Smile

) 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.

Report message to a moderator

Re: FATAL: kernel too old [message #1803 is a reply to message #1783]

Sat, 25 February 2006 00:30

Valmont
Messages: 225
Registered: September 2005

Senior Member

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

[Updated on: Sat, 25 February 2006 00:31]

Report message to a moderator

Re: FATAL: kernel too old [message #1809 is a reply to message #1803]

Sun, 26 February 2006 08:47

dev
Messages: 1693
Registered: September 2005
Location: Moscow

Senior Member

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 Sad

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" Very Happy

Report message to a moderator

Re: FATAL: kernel too old [message #5777 is a reply to message #1783]

Wed, 30 August 2006 14:01

Valmont
Messages: 225
Registered: September 2005

Senior Member

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...

Report message to a moderator