| Re: Duplicate kernel error / error checking dependencies [message #53616 is a reply to message #53615] |
Wed, 08 January 2020 20:39   |
dmc_dtc
Messages: 15
Registered: May 2014
Location: Serbia
|
Junior Member |
|
|
Hi,
yes, initially i didnt get answer here so i posted it as bug in openvz forums here
https://bugs.openvz.org/browse/OVZ-7157
There is a workaround i will post in the end but the main thing is we are doing it wrong. OpenVZ7 is only officially supported on Virtuozzo Liux 7. So up until to now it was possible to somewhat interchangeably use CentOS 7 with OpenVZ and you could install OpenVZ7 on CentOS7, but since latest release (7.0.12) there are changes in json-c and jansson libs which differ from vanilla CentOS versions of those libs. Solution is to install json-c and jansonn from Virtuozzo linux release repos... So before doing install of OpenVZ7 just install this two rpms first:
yum install http://repo.virtuozzo.com/vzlinux/7.7/x86_64/os/Packages/j/j ansson-2.10-1.vl7.1.x86_64.rpm
yum install http://repo.virtuozzo.com/vzlinux/7.7/x86_64/os/Packages/j/j son-c-0.11-13.vl7.1.x86_64.rpm
it can be done on a newly installed CentOS BEFORE openvz packages or apply it to existing CentOS7 with Openvz7 ones up until 7.0.12 release.
So after this i am not sure we wont run into similar issues again in the future if we continue to use CentOS 7 since obviosly virtuozzo linux and CentOS7 are now two separated branches, so i think definitely where you can, better use full virtuozzo linux 7 iso instalation to install it.. but as i mentioned in bug report some hosters make it hard for you to install custom iso so it is better to use centos7 and then convert CentOS7 to virtuozzo ... but the sciprt vzdeploy (which used to do exactly that) is broken with latest CentOS 7.7... so you have two options, either leave it on CentOS7 with this custom "hack" or use Virtuozzo Linux 7. I dont really see this hack as a problem, since i dont use dom0 (host OS) for anything, and i only need it to provide kernel updates to paravirtualaized containers, so even if in the future something similar happens and i cannot update OpenVZ i could still update just vzkernel which is fine.
Hope this solves your problem and give you a bit of background of the problem, again better to read bug report thread for more details.
Cheers
>> dmc / dtc <<
[Updated on: Wed, 08 January 2020 20:40] Report message to a moderator |
|
|
|
OpenVZ Forum
Members
Search
Help
Register
Login
Home
