Is possible that OS kernel upgrade ( minor or major) to induce instability in LXC guests?
The initial idea came from the book "Proxmox high availability" http://droppdf.com/v/FpQNV. Quote : " However, since all containers share the system kernel of the host OS, a system-related problem might appear during the host OS kernel upgrade". The author was talking about OpenVZ containers, but the same question applies also to LXC containers.
This potential issue is the only thing that is holding me for going for a high density LXC cluster, instead of KVM.
I was planing to test this, by installing an old version of Proxmox ( 4.0 beta1 with kernel 3.19.8) and to migrate the lxc container to the newest kernel 4.4.19. But I can't find the old isos http://download.proxmox.com/
Maybe an early adopter of LXC from 4.0 beginnings could share experience.
On the other hand, it makes no sense to open a separate post. Are the initial LXC issues from https://forum.proxmox.com/threads/moving-to-lxc-is-a-mistake.25603/ solved now ? At first glance, the answer is yes.
Thanks!
Disclaimer: This is a theoretical question, I didn't experienced such issues.
The initial idea came from the book "Proxmox high availability" http://droppdf.com/v/FpQNV. Quote : " However, since all containers share the system kernel of the host OS, a system-related problem might appear during the host OS kernel upgrade". The author was talking about OpenVZ containers, but the same question applies also to LXC containers.
This potential issue is the only thing that is holding me for going for a high density LXC cluster, instead of KVM.
I was planing to test this, by installing an old version of Proxmox ( 4.0 beta1 with kernel 3.19.8) and to migrate the lxc container to the newest kernel 4.4.19. But I can't find the old isos http://download.proxmox.com/
Maybe an early adopter of LXC from 4.0 beginnings could share experience.
On the other hand, it makes no sense to open a separate post. Are the initial LXC issues from https://forum.proxmox.com/threads/moving-to-lxc-is-a-mistake.25603/ solved now ? At first glance, the answer is yes.
Thanks!
Disclaimer: This is a theoretical question, I didn't experienced such issues.
Last edited: