| Re: Openvz7 and CVE-2026-31431 (Copy Fail) vulnerability [message #53890 is a reply to message #53889] |
Sat, 02 May 2026 03:16  |
dmc_dtc
Messages: 16
Registered: May 2014
Location: Serbia
|
Junior Member |
|
|
OpenVZ User here, did same analysis today as you, came to the same conclusion, i am sure that we are home free on this one.
Unfortunate problem is that, if some day in the future there is some RCE or serious kernel bug, we are stuck with this kernel from 2024 ... I am actively migrating from OpenVZ since it seems dead anyways. Though my guest systems are alma 8 9 and 10 and up 2 date, we are stuck with this old kernel, If they would only support kernel i could go along for few more years, at last if they would fix these kinds of serious bugs.
I was tempted to try to patch some newer kernels myself or use ones from never OpenVZ just why waste time.
That being said, thanks to the OpenVZ community and devels while it lasted, it was the easist and best solution for containers, Now i use KVM for new systems, and for older VZ containers i've ported (easily) to systemd-nspawnd (i used simfs so migration was easy - just copying the files).. i managed to successfully migrate few of openVZ containers just for fun and it works great, but we dont have all capabilities maybe as OpenVZ had, but for now KVM is best solution for me going forward, so i dont worry about host kernel vulnerabilities.
If OpenVZ ever continues i will be happy to reconsider.
Sorry for off topic
>> dmc / dtc <<
[Updated on: Sat, 02 May 2026 03:21] Report message to a moderator |
|
|
|
OpenVZ Forum
Members
Search
Help
Register
Login
Home
