1

Last night I upgraded to the latest kernel of openvz. I rebooted the host node. It came up with the latest kernel. However, the containers are still running the old kernel.

What I did on the host node was reboot in CLI to cycle the machine. How do I get all the containers to cycle as well on a reboot?

Also, is the host node and other containers at a security risk if containers are running the old kernel still?

2
  • Ummm, with OpenVZ, the containers don't run their own kernels. There's only one kernel, and that's the one that the host runs. This is one of the primary detractors about OpenVZ versus other proper virtualization options, and is why I try and steer people away from it whenever possible.
    – EEAA
    Jul 23, 2014 at 15:03
  • Well when the system came back online, the containers it looks like were "put to sleep". they came back up with the older kernel till they were rebooted or maybe it was just a cache when I did uname -a.
    – Jason
    Jul 23, 2014 at 15:06

0

You must log in to answer this question.

Browse other questions tagged .