Kernel panic on VM's since Kernel pve-kernel-5.0.21-4-pve: 5.0.21-8

mensinck

Renowned Member
Oct 19, 2015
24
1
68
Kiel, germany
Since we updated to Kernel pve-kernel-5.0.21-4-pve: 5.0.21-8 we can not start any VM's on this host.
Migrated VM's do have kernel panic as like this:

1573057811077.png

This are the package versions we are running on the host:

proxmox-ve: 6.0-2 (running kernel: 5.0.21-3-pve)
pve-manager: 6.0-11 (running version: 6.0-11/2140ef37)
pve-kernel-helper: 6.0-11 pve-kernel-5.0: 6.0-10
pve-kernel-5.0.21-4-pve: 5.0.21-8
pve-kernel-5.0.21-3-pve: 5.0.21-7
pve-kernel-5.0.15-1-pve: 5.0.15-1
ceph: 14.2.4-pve1
ceph-fuse: 14.2.4-pve1
corosync: 3.0.2-pve4
criu: 3.11-3
glusterfs-client: 5.5-3
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.13-pve1
libpve-access-control: 6.0-3
libpve-apiclient-perl: 3.0-2
libpve-common-perl: 6.0-6
libpve-guest-common-perl: 3.0-2
libpve-http-server-perl: 3.0-3
libpve-storage-perl: 6.0-9
libqb0: 1.0.5-1
lvm2: 2.03.02-pve3
lxc-pve: 3.2.1-1
lxcfs: 3.0.3-pve60
novnc-pve: 1.1.0-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.0-8
pve-cluster: 6.0-7
pve-container: 3.0-10
pve-docs: 6.0-8
pve-edk2-firmware: 2.20190614-1
pve-firewall: 4.0-7
pve-firmware: 3.0-4
pve-ha-manager: 3.0-2
pve-i18n: 2.0-3
pve-qemu-kvm: 4.0.1-4
pve-xtermjs: 3.13.2-1
qemu-server: 6.0-13
smartmontools: 7.0-pve2
spiceterm: 3.1-1
vncterm: 1.6-1
zfsutils-linux: 0.8.2-pve2


OK, WE ARE RUNNING ON A VERY OLD MAINBOARD of HP G5 , Processor is Intel Xeon E5320, but we do have install intel-microcode on the host.

When booting kernel 5.0.21-3-pve

We can move VM's and also boot VM's on that host.

Any hints to resolve since I'm not a kernel hacker ;-)
 
We are already looking into those issues, with these dinosaurs. I'm curious, what's running on those machines? I mean the e5320 was dropped 2009 from Intel and is probably not one of the most efficient models compared to modern cpu's.
 
We are already looking into those issues, with these dinosaurs. I'm curious, what's running on those machines? I mean the e5320 was dropped 2009 from Intel and is probably not one of the most efficient models compared to modern cpu's.

I think this pve-kernel-5.0.21-4-pve cause Debian guests to reboot loop on older intel CPUs is what you are talking about. The same good old dinosaurs. We use this old hosts for testing and DMZ hosts. Having a lot of HDD's for ceph, a tape drive.....

So I will follow the other discussion.
 
I confirm the problem. Moreover, the new virtual machine can not boot from ISO with the latest update.
Fixed after apt install pve-kernel-5.3
 
I can confirm Version pve-kernel-5.0.21-4-pve: 5.0.21-9

is working correct on 8 x Intel(R) Xeon(R) CPU E5320

So this is fixed now.

Thanks so much for great work
 

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!