Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Kernel Panic vmware 2 sockets 1 core #1695
Things successfully boot if you go to 1 core, 1 socket, or up to 4 socket, 4 cores. Also if you do 1 socket, 2 cores.
This can be reproduced by:
Release 1192.2.0 was the last update our hosts received before the kernel panic'ing started, which was also the last 4.7.x kernel before 4.8.x kernel. Seems like maybe there was something introduced in that kernel? Have also narrowed this down to be only when the VM has 2 vCPUs and 4GB of RAM. If I move the VM to 2GB or 6GB of RAM it will boot normally.
The configuration of vCPUs to RAM and what causes the issue appears to be more random than at first thought. Sometimes it boots, sometimes it doesn't. Sometimes changing the configuration works, sometimes not. Every time a new OS releases we get hit by this because the OS won't update due to the panic and we get into reboot, update, panic, reboot, update, panic loops. Just curious if others are having this issue or if it is potentially unique to our environment.
Experiencing the same issue (beta channel, 1235.1.0). pressing "Restart guest" button seems to "fix" it most of the time.
I have disabled the updating mechanism so it doesn't reboot :P
My vm config is 8gb mem with 2 virtual sockets and 1 core per socket.
Changed the VM to 1 virtual socket and 1 core per socket, power cycled the system a lot of times resuling in 0 kernel panics.
Changed the virtual sockets back to 2 and got a kernel panic right away.
I was able to upgrade to the latest beta version (1298.3.0) by changing to 1 cpu/1 core as @Sebas- suggested. But switching back to the original CoreOS OVA settings—2 cpu/1 core—causes it to kernel panic again.
I was able to stop the kernel panic in both cases (1248.4.0 and 1298.3.0) by upgrading the VM compatibility to hardware version 9 or higher. The CoreOS OVA is set to hardware version 7 by default.