This morning I upgraded to Proxmox 8. All works well as long as I boot with kernel 5.15.30-2-pve. If I try booting with 5.15.108-1-pve or 6.2.16-4-pve I get an immediate kernel panic, which ends with "---[ end Kernel panic - not syncing: Attempted to kill init! exit code ..."
My Proxmox 7 setup has been stable on kernel 5.15.30-2-pve.
/root/kernel/cmdline
(I had some random instability every few weeks before adding split_lock_detect=off)
I'm not entirely sure what to provide but I'm happing to add whatever is needed to help diagnose of course. Here are a few things I think may be helpful:
uname -a
pveceph status
zfs list -r -o name,mountpoint,mounted
proxmox-boot-tool status
efibootmgr -v
pveversion -v
I have also tried booting the 6.x kernel without the following additions: "intel_iommu=on iommu=pt split_lock_detect=off", same result.
Any suggestions? Many thanks in advance.
My Proxmox 7 setup has been stable on kernel 5.15.30-2-pve.
/root/kernel/cmdline
Code:
root=ZFS=rpool/ROOT/pve-1 boot=zfs intel_iommu=on iommu=pt split_lock_detect=off(I had some random instability every few weeks before adding split_lock_detect=off)
I'm not entirely sure what to provide but I'm happing to add whatever is needed to help diagnose of course. Here are a few things I think may be helpful:
uname -a
Code:
Linux proxmox 5.15.30-2-pve #1 SMP PVE 5.15.30-3 (Fri, 22 Apr 2022 18:08:27 +0200) x86_64 GNU/Linuxpveceph status
Code:
binary not installed: /usr/bin/ceph-monzfs list -r -o name,mountpoint,mounted
Code:
NAME MOUNTPOINT MOUNTED
rpool /rpool yes
rpool/ROOT /rpool/ROOT yes
rpool/ROOT/pve-1 / yes
rpool/data /rpool/data yes
rpool/data/subvol-100-disk-0 /rpool/data/subvol-100-disk-0 yes
rpool/data/subvol-104-disk-0 /rpool/data/subvol-104-disk-0 yes
rpool/data/subvol-108-disk-0 /rpool/data/subvol-108-disk-0 yes
rpool/data/subvol-109-disk-0 /rpool/data/subvol-109-disk-0 yes
rpool/data/subvol-110-disk-0 /rpool/data/subvol-110-disk-0 yes
rpool/data/subvol-113-disk-0 /rpool/data/subvol-113-disk-0 yes
rpool/data/subvol-114-disk-0 /rpool/data/subvol-114-disk-0 yes
rpool/data/subvol-120-disk-0 /rpool/data/subvol-120-disk-0 yes
rpool/data/vm-101-disk-0 - -
rpool/data/vm-102-disk-0 - -
rpool/data/vm-102-disk-1 - -
rpool/data/vm-103-disk-0 - -
rpool/data/vm-103-disk-1 - -
rpool/data/vm-105-disk-0 - -
rpool/data/vm-105-disk-1 - -
rpool/data/vm-105-disk-2 - -
rpool/data/vm-106-disk-0 - -
rpool/data/vm-107-disk-0 - -
rpool/data/vm-107-disk-1 - -
rpool/data/vm-111-disk-0 - -
rpool/data/vm-111-disk-1 - -
rpool/data/vm-112-disk-0 - -
rpool/data/vm-112-disk-1 - -
rpool/data/vm-116-disk-0 - -
rpool/data/vm-117-disk-0 - -
rpool/data/vm-118-disk-0 - -
rpool/data/vm-118-disk-1 - -
rpool/data/vm-118-disk-2 - -
rpool/data/vm-119-disk-0 - -proxmox-boot-tool status
Code:
System currently booted with uefi
C7EC-0E57 is configured with: uefi (versions: 5.15.108-1-pve, 5.15.30-2-pve, 6.2.16-4-pve)efibootmgr -v
Code:
BootCurrent: 0003
Timeout: 1 seconds
BootOrder: 0003,0004,0001,0000
Boot0000 Windows Boot Manager VenHw(99e275e7-75a0-4b37-a2e6-c5385e6c00cb)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}...a...............
Boot0001 UEFI: Built-in EFI Shell VenMedia(5023b95c-db26-429b-a648-bd47664c8012)..BO
Boot0003* Linux Boot Manager HD(2,GPT,e941d35f-6245-4e48-9280-a7484e350158,0x800,0x100000)/File(\EFI\SYSTEMD\SYSTEMD-BOOTX64.EFI)
Boot0004* UEFI OS HD(2,GPT,e941d35f-6245-4e48-9280-a7484e350158,0x800,0x100000)/File(\EFI\BOOT\BOOTX64.EFI)..BOpveversion -v
Code:
proxmox-ve: 8.0.1 (running kernel: 5.15.30-2-pve)
pve-manager: 8.0.3 (running version: 8.0.3/bbf3993334bfa916)
pve-kernel-6.2: 8.0.3
pve-kernel-5.15: 7.4-4
pve-kernel-6.2.16-4-pve: 6.2.16-5
pve-kernel-5.15.108-1-pve: 5.15.108-1
pve-kernel-5.15.107-2-pve: 5.15.107-2
pve-kernel-5.15.107-1-pve: 5.15.107-1
pve-kernel-5.15.85-1-pve: 5.15.85-1
pve-kernel-5.15.83-1-pve: 5.15.83-1
pve-kernel-5.15.30-2-pve: 5.15.30-3
ceph-fuse: 17.2.6-pve1+3
corosync: 3.1.7-pve3
criu: 3.17.1-2
glusterfs-client: 10.3-5
ifupdown2: 3.2.0-1+pmx3
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-3
libknet1: 1.25-pve1
libproxmox-acme-perl: 1.4.6
libproxmox-backup-qemu0: 1.4.0
libproxmox-rs-perl: 0.3.0
libpve-access-control: 8.0.3
libpve-apiclient-perl: 3.3.1
libpve-common-perl: 8.0.6
libpve-guest-common-perl: 5.0.3
libpve-http-server-perl: 5.0.4
libpve-rs-perl: 0.8.4
libpve-storage-perl: 8.0.2
libspice-server1: 0.15.1-1
lvm2: 2.03.16-2
lxc-pve: 5.0.2-4
lxcfs: 5.0.3-pve3
novnc-pve: 1.4.0-2
openvswitch-switch: 3.1.0-2
proxmox-backup-client: 3.0.1-1
proxmox-backup-file-restore: 3.0.1-1
proxmox-kernel-helper: 8.0.2
proxmox-mail-forward: 0.2.0
proxmox-mini-journalreader: 1.4.0
proxmox-offline-mirror-helper: 0.6.2
proxmox-widget-toolkit: 4.0.6
pve-cluster: 8.0.2
pve-container: 5.0.4
pve-docs: 8.0.4
pve-edk2-firmware: 3.20230228-4
pve-firewall: 5.0.2
pve-firmware: 3.7-1
pve-ha-manager: 4.0.2
pve-i18n: 3.0.5
pve-qemu-kvm: 8.0.2-3
pve-xtermjs: 4.16.0-3
qemu-server: 8.0.6
smartmontools: 7.3-pve1
spiceterm: 3.3.0
swtpm: 0.8.0+pve1
vncterm: 1.8.0
zfsutils-linux: 2.1.12-pve1I have also tried booting the 6.x kernel without the following additions: "intel_iommu=on iommu=pt split_lock_detect=off", same result.
Any suggestions? Many thanks in advance.
Last edited:
