| OpenVZ 7 node and container different kernel versions? [message #53509] |
Sat, 04 May 2019 12:48  |
HHawk
Messages: 29
Registered: September 2017
Location: Europe
|
Junior Member |
|
|
Hi all,
We have been testing OpenVZ 7 as OpenVZ 6 (legacy) will be EOL later this year.
So I have been testing it quite a bit. And I noticed something very strange.
The node which has OpenVZ 7 installed is running the following kernel:
Quote:Linux server5000.node.com 3.10.0-957.10.1.vz7.85.17 #1 SMP Thu Apr 11 18:11:44 MSK 2019 x86_64 x86_64 x86_64 GNU/Linux
And I created an Ubuntu 18.04 container by using: vzctl create 10003 --ostemplate ubuntu-18.04-x86_64
After that I copied several things over from the /etc/vz/conf/10002.conf from a working server (made minor changes for obvious part).
When I did that I tried installing Plesk in the Ubuntu container and it worked without any issues. Cannot see errors or issues.
However when I run uname inside the container I was surprised to see higher kernel version:
Quote:Linux ns1.ubuntu1804.nl 4.15.0 #1 SMP Thu Apr 11 18:11:44 MSK 2019 x86_64 x86_64 x86_64 GNU/Linux
Remember that I come from OpenVZ 6 (legacy). Here the container had always the same kernel version as the hardware node.
Maybe something changed and the above is normal?
Can someone confirm and/or explain this please?
Thanks in advance.
Regards
|
|
|
|
| Re: OpenVZ 7 node and container different kernel versions? [message #53511 is a reply to message #53509] |
Mon, 06 May 2019 07:51  |
HHawk
Messages: 29
Registered: September 2017
Location: Europe
|
Junior Member |
|
|
A small follow-up with extra information.
I also migrated a container a CentOS 7 with ovztransfer.sh.
This container is running the same kernel as the hardware node:
Linux nodename.server.com 3.10.0-957.10.1.vz7.85.17 #1 SMP Thu Apr 11 18:11:44 MSK 2019 x86_64 x86_64 x86_64 GNU
A container I created manually, also with CentOS 7, has a similar kernel version as the hardware node:
Node: Linux nodename.server.com 3.10.0-957.10.1.vz7.85.17 #1 SMP Thu Apr 11 18:11:44 MSK 2019 x86_64 x86_64 x86_64 GNU
Container: ns1.container.com 3.10.0 #1 SMP Thu Apr 11 18:11:44 MSK 2019 x86_64 x86_64 x86_64 GNU/Linux
So the only weird one is the Ubtuntu created container? Which has kernel version: Linux ns1.ubuntu1804.nl 4.15.0 #1 SMP Thu Apr 11 18:11:44 MSK 2019 x86_64 x86_64 x86_64 GNU/Linux
Can please someone inform me if this is bad or am I worrying to much? I hope someone can give me a clear answer on this and explain some stuff.
Thanks in advance!
//edit
By the way; I created the Ubuntu container by using the EZ templates with the following command: vzctl create 10003 --ostemplate ubuntu-18.04-x86_64
[Updated on: Mon, 06 May 2019 07:56] Report message to a moderator |
|
|
|
| Re: OpenVZ 7 node and container different kernel versions? [message #53513 is a reply to message #53511] |
Mon, 06 May 2019 15:34 |
khorenko
Messages: 533
Registered: January 2006
Location: Moscow, Russia
|
Senior Member |
|
|
Hi!
You have nothing to worry about, it works as designed.
Some modern distros require new kernel version and do check the version during their work,
so we backport kernel features which those distros require from newer kernels
(so appropriate apps can use those features)
and fake "uname" output for those containers.
Actual kernel version reported is configured in templates config, for example:
# cat /vz/template/ubuntu/16.04/x86_64/config/os/default/osrelease
4.4.0
BTW, it was the same for OpenVZ 6.
Hope that helps.
If your problem is solved - please, report it!
It's even more important than reporting the problem itself...
|
|
|
|
| Re: OpenVZ 7 node and container different kernel versions? [message #53515 is a reply to message #53513] |
Tue, 07 May 2019 17:32 |
HHawk
Messages: 29
Registered: September 2017
Location: Europe
|
Junior Member |
|
|
khorenko wrote on Mon, 06 May 2019 15:34Hi!
You have nothing to worry about, it works as designed.
Some modern distros require new kernel version and do check the version during their work,
so we backport kernel features which those distros require from newer kernels
(so appropriate apps can use those features)
and fake "uname" output for those containers.
Actual kernel version reported is configured in templates config, for example:
# cat /vz/template/ubuntu/16.04/x86_64/config/os/default/osrelease
4.4.0
BTW, it was the same for OpenVZ 6.
Hope that helps.
Thank you khorenko!
Highly appreciated.
|
|
|
|
OpenVZ Forum
Members
Search
Help
Register
Login
Home
