Kernel panic after first upgrade

G

gmtech

New Member
Proxmox Subscriber
Jan 8, 2026
3
0
1
I installed a new virtual machine proxmox mail gateway on Esxi. Added the license and then ran the updates that were available. The proxmox kernel upgraded from 6.14 to 6.17 and on a reboot there is a kernel panic not syncing attempting to kill the idle task. I can boot into the previous kernel but have been unable to find an answer as the why the new kernel panics on boot. Any help would be greatly appreciated. If I can provide any more information that would help please let me know. Thank you

Phil
 
Could you provide a kernel dump or atleast logs? Hard to debug with zero information.
 
I have attached the journalctl log for today. There was a reboot with a kernel panic at 6:15am. I do not know how to get a kernel dump. I attempted to follow the directions to enable this but there is no linux-image-<current-kernel>-dbg package and nothing is in /var/crash after rebooting into the working kernel. The current kernel it is trying to boot it 6.17.2-2-pve. That is the one that panics. Sorry I have never had the reason to get a kernel dump from a Proxmox project.
 

Attachments

gmtech said:
There was a reboot with a kernel panic at 6:15am
Click to expand...
Not to be found in the journal, but that is due to it not even making it to the init system i guess. Boots seen in the journal are 6.14.11-4-pve.
gmtech said:
virtual machine proxmox mail gateway on Esxi
Click to expand...
What version of Esxi are you running? Your systemd journal contains some XSAVE consistency problem: size 2440 != kernel_size 2696 warnings, which might lead to AVX support being disabled. Please see [0] and make sure you run an up to date version of your hypervisor.

gmtech said:
there is no linux-image-<current-kernel>-dbg package
Click to expand...
Since PMG and all other products do not use the default Debian kernel, but rather a custom kernel build and packaged by Proxmox. Rather than trying to generate the kdump, can you show the kernel panic message you get when the boot fails? E.g. a screenshot?

Further, you can check if the latest kernel 6.17.4-2-pve as available in the pmg-test repo also shows the same issue. To do so, temporarily enable the pbs-test repo and install the kernel via apt update && apt install proxmox-kernel-6.17.4-2-pve

[0] https://knowledge.broadcom.com/external/article/324780/xsave-consistency-problem-for-rhel-8x-vm.html
 
  • Like
Reactions: fstrankowski
You must log in or register to reply here.
Top Bottom