I know of no one who has done an inplace upgrade. You are better off setting up a new server and copying the containers from the old system to the new system.
Since there are changes in ploop you can do vzmigrate, or something like manually create the ploop systems on the new server and manually migrate them. I have done in place upgrades from centos3->4, 4->5 and 5->6. Never tried 6->7 with changes like systemctl and extensive kernel changes (v2->3 all the others were in in 2.x) you are looking at a difficult change when a copy is so much easier. Even with that, there were occassional issues with in place upgrades that would come up from time to time, and need good knowledge of the systems to fix them. ________________________________ From: users-boun...@openvz.org <users-boun...@openvz.org> on behalf of Conseev Hosting <host...@conseev.com> Sent: Sunday, June 30, 2019 9:44:29 AM To: users@openvz.org Subject: [Users] Switching to vzkernel-3.10.0-957.10.1.vz7.85.17.x86_64.rpm Hello, We currently have OpenVZ nodes running 2.6.32-042stab124.2 and would like to be able to have the newer OpenVZ kernel. On these existing nodes is there no issue with installing this RPM from https://download.openvz.org/virtuozzo/releases/openvz-7.0.10-252/x86_64/os/Packages/v/ and rebooting into it or are there other steps that have to be taken to prepare for the change?
_______________________________________________ Users mailing list Users@openvz.org https://lists.openvz.org/mailman/listinfo/users
