kernel panic caused by using kernel.pid_ns_hide_child=1

zerkms

New Member
Jan 23, 2013
16
0
1
When `kernel.pid_ns_hide_child=1` sysctl flag is used it causes the proxmox v3.2-5a885216-5 (2.6.32-29-pve #1 SMP Thu Apr 24 10:03:02 CEST 2014 x86_64 GNU/Linux) to crash into kernel panic when one starts an openvz container.

It's presumably caused somehow by openvz and they have fixed it recently: https://bugzilla.openvz.org/show_bug.cgi?id=2983 (+ see 2 duplicates)

So is there any known workaround to hide children from containers from being visible on a host machine, and if not - any schedule to reintegrate the fix into pve kernel?
 
Last edited:
So is there any known workaround to hide children from containers from being visible on a host machine, and if not - any schedule to reintegrate the fix into pve kernel?

There is already a new kernel in the pve-no-subscription repository including that fix.
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!