Kernel 3.2 / Debian 7 hypervisor [message #45409] |
Sat, 03 March 2012 20:33 |
NIXin
Messages: 3 Registered: March 2012 Location: UK
|
Junior Member |
|
|
Hi guys,
There's a lot of reasons for people to upgrade the kernel to 3.2, even if just for testing for now.
Are there no planned patches for kernel 3.2?
What is the future of the OpenVZ technology in this context?
Thank you
|
|
|
|
|
|
|
|
|
|
|
Re: Kernel 3.2 / Debian 7 hypervisor [message #52568 is a reply to message #50037] |
Fri, 16 September 2016 10:40 |
|
Well newer libc simply will reject old kernels (as well as udev and some other stuff). Since upgrades are blocked I have to get rid of openvz. That's sad because lxc is still an unstable pile of glorified chroot, but I won't go into "compile everything again for myself" game. And it's well integrated into the kernel and it doesn't relate to redhat.
|
|
|
Re: Kernel 3.2 / Debian 7 hypervisor [message #52571 is a reply to message #52568] |
Mon, 19 September 2016 18:45 |
|
dowdle
Messages: 261 Registered: December 2005 Location: Bozeman, Montana
|
Senior Member |
|
|
With regards to OpenVZ Legacy (the version of OpenVZ based on the RHEL6-2.6.32x kernel, you should be able to run Debian 7 and 8 containers on it just fine as they offer supported OS Templates for them.
OpenVZ 7 was released near the end of July 2016 and it is RHEL7-based with their 3.10.x kernel.
--
TYL, Scott Dowdle
Belgrade, Montana, USA
|
|
|