Proxmox 8.2.4 hangs server with kernel panic

[eltincho]

Hello,

I’ve a problem with a Proxmox installed manually on Debian 12 in a VPS AMD Epyc based, who was updated to 8.2.4 version.



After a random time the server hangs, I loose connection, and the virtual console did not response, the only option is reboot from web panel console because server had a Kernel Panic.



I try with different kernel versions 6.8.12, 6.8.8, 6.5 and 6.2 with the same problem. I added to the grub amd_iommu=off and the problem persists.



Any idea or fix to try?



journal -f:



Sep 04 08:18:54 proxmoxsrv pvestatd[1161]: VM 300104 qmp command failed - VM 300104 qmp command 'query-proxmox-support' failed - unable to connect to VM 300104 qmp socket - timeout after 51 retries

Sep 04 08:18:54 proxmoxsrv pvestatd[1161]: status update time (8.571 seconds)

Sep 04 08:19:04 proxmoxsrv pvestatd[1161]: VM 300104 qmp command failed - VM 300104 qmp command 'query-proxmox-support' failed - unable to connect to VM 300104 qmp socket - timeout after 51 retries

Sep 04 08:19:05 proxmoxsrv pvestatd[1161]: status update time (8.605 seconds)

Sep 04 08:19:14 proxmoxsrv pvestatd[1161]: VM 300104 qmp command failed - VM 300104 qmp command 'query-proxmox-support' failed - unable to connect to VM 300104 qmp socket - timeout after 51 retries

Sep 04 08:19:14 proxmoxsrv pvestatd[1161]: status update time (8.572 seconds)

Sep 04 08:19:25 proxmoxsrv pvestatd[1161]: VM 300104 qmp command failed - VM 300104 qmp command 'query-proxmox-support' failed - unable to connect to VM 300104 qmp socket - timeout after 51 retries

Sep 04 08:19:25 proxmoxsrv pvestatd[1161]: status update time (8.595 seconds)

Sep 04 08:19:26 proxmoxsrv pvedaemon[19041]: worker exit

Sep 04 08:19:26 proxmoxsrv pvedaemon[1178]: worker 19041 finished

Sep 04 08:19:26 proxmoxsrv pvedaemon[1178]: starting 1 worker(s)

Sep 04 08:19:26 proxmoxsrv pvedaemon[1178]: worker 23965 started

Sep 04 08:19:34 proxmoxsrv pvestatd[1161]: VM 300104 qmp command failed - VM 300104 qmp command 'query-proxmox-support' failed - unable to connect to VM 300104 qmp socket - timeout after 51 retries

Sep 04 08:19:35 proxmoxsrv pvestatd[1161]: status update time (8.598 seconds)

Sep 04 08:19:44 proxmoxsrv pvestatd[1161]: VM 300104 qmp command failed - VM 300104 qmp command 'query-proxmox-support' failed - unable to connect to VM 300104 qmp socket - timeout after 51 retries

Sep 04 08:19:44 proxmoxsrv pvestatd[1161]: status update time (8.600 seconds)

Sep 04 08:19:54 proxmoxsrv pvestatd[1161]: VM 300104 qmp command failed - VM 300104 qmp command 'query-proxmox-support' failed - unable to connect to VM 300104 qmp socket - timeout after 51 retries

Sep 04 08:19:55 proxmoxsrv pvestatd[1161]: status update time (8.568 seconds)

Sep 04 08:20:04 proxmoxsrv pvestatd[1161]: VM 300104 qmp command failed - VM 300104 qmp command 'query-proxmox-support' failed - unable to connect to VM 300104 qmp socket - timeout after 51 retries

Sep 04 08:20:04 proxmoxsrv pvestatd[1161]: status update time (8.622 seconds)

Sep 04 08:20:15 proxmoxsrv pvestatd[1161]: VM 300104 qmp command failed - VM 300104 qmp command 'query-proxmox-support' failed - unable to connect to VM 300104 qmp socket - timeout after 51 retries

Sep 04 08:20:15 proxmoxsrv pvestatd[1161]: status update time (8.663 seconds)

Sep 04 08:20:24 proxmoxsrv pvestatd[1161]: VM 300104 qmp command failed - VM 300104 qmp command 'query-proxmox-support' failed - unable to connect to VM 300104 qmp socket - timeout after 51 retries

Sep 04 08:20:25 proxmoxsrv pvestatd[1161]: status update time (8.614 seconds)

Sep 04 08:20:33 proxmoxsrv dhcpd[818]: DHCPREQUEST for 192.168.30.2 from bc:24:11:b7:f3:60 via vmbr1

Sep 04 08:20:33 proxmoxsrv dhcpd[818]: DHCPACK on 192.168.30.2 to bc:24:11:b7:f3:60 via vmbr1

Sep 04 08:20:34 proxmoxsrv pvestatd[1161]: VM 300104 qmp command failed - VM 300104 qmp command 'query-proxmox-support' failed - unable to connect to VM 300104 qmp socket - timeout after 51 retries

Sep 04 08:20:34 proxmoxsrv pvestatd[1161]: status update time (8.611 seconds)

Sep 04 08:20:44 proxmoxsrv pvestatd[1161]: VM 300104 qmp command failed - VM 300104 qmp command 'query-proxmox-support' failed - unable to connect to VM 300104 qmp socket - timeout after 51 retries

Sep 04 08:20:45 proxmoxsrv pvestatd[1161]: status update time (8.636 seconds)

Sep 04 08:20:54 proxmoxsrv pvestatd[1161]: VM 300104 qmp command failed - VM 300104 qmp command 'query-proxmox-support' failed - unable to connect to VM 300104 qmp socket - timeout after 51 retries

Sep 04 08:20:55 proxmoxsrv pvestatd[1161]: status update time (8.598 seconds)

Sep 04 08:21:03 proxmoxsrv kernel: INFO: task kvm:1986 blocked for more than 122 seconds.

Sep 04 08:21:03 proxmoxsrv kernel: Tainted: P O 6.8.12-1-pve #1

Sep 04 08:21:03 proxmoxsrv kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.

Sep 04 08:21:03 proxmoxsrv kernel: task:kvm state stack:0 pid:1986 tgid:1986 ppid:1 flags:0x00000002

Sep 04 08:21:03 proxmoxsrv kernel: Call Trace:

Sep 04 08:21:03 proxmoxsrv kernel: <TASK>

Sep 04 08:21:03 proxmoxsrv kernel: __schedule+0x3ec/0x1520

Sep 04 08:21:03 proxmoxsrv kernel: ? srso_alias_return_thunk+0x5/0xfbef5

Sep 04 08:21:03 proxmoxsrv kernel: ? scheduler_tick+0x11b/0x2f0

Sep 04 08:21:03 proxmoxsrv kernel: ? srso_alias_return_thunk+0x5/0xfbef5

Sep 04 08:21:03 proxmoxsrv kernel: schedule+0x33/0xf0

Sep 04 08:21:03 proxmoxsrv kernel: kvm_async_pf_task_wait_schedule+0x171/0x1b0

Sep 04 08:21:03 proxmoxsrv kernel: ? clockevents_program_event+0x9e/0x110

Sep 04 08:21:03 proxmoxsrv kernel: __kvm_handle_async_pf+0x5c/0xc0

Sep 04 08:21:03 proxmoxsrv kernel: exc_page_fault+0xb6/0x1b0

Sep 04 08:21:03 proxmoxsrv kernel: asm_exc_page_fault+0x27/0x30

Sep 04 08:21:03 proxmoxsrv kernel: RIP: 0033:0x736871126f8d

Sep 04 08:21:03 proxmoxsrv kernel: RSP: 002b:000073654eaeada0 EFLAGS: 00010246

Sep 04 08:21:03 proxmoxsrv kernel: RAX: 0000736871261cc0 RBX: 0000000000401040 RCX: 00000000003fffd0

Sep 04 08:21:03 proxmoxsrv kernel: RDX: 0000599bbce9e030 RSI: 0000599bbf2a6000 RDI: 0000599bbca9cff0

Sep 04 08:21:03 proxmoxsrv kernel: RBP: 0000736871261c60 R08: 0000599bc2eb5ca0 R09: 0000736871261d70

Sep 04 08:21:03 proxmoxsrv kernel: R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000401030

Sep 04 08:21:03 proxmoxsrv kernel: R13: 0000599bbca9cff0 R14: 0000000000801010 R15: 0000736871261cc0

Sep 04 08:21:03 proxmoxsrv kernel: </TASK>

Sep 04 08:21:04 proxmoxsrv pvestatd[1161]: VM 300104 qmp command failed - VM 300104 qmp command 'query-proxmox-support' failed - unable to connect to VM 300104 qmp socket - timeout after 51 retries

Sep 04 08:21:04 proxmoxsrv pvestatd[1161]: status update time (8.655 seconds)

Sep 04 08:21:14 proxmoxsrv pvestatd[1161]: VM 300104 qmp command failed - VM 300104 qmp command 'query-proxmox-support' failed - unable to connect to VM 300104 qmp socket - timeout after 51 retries

Sep 04 08:21:15 proxmoxsrv pvestatd[1161]: status update time (8.619 seconds)

Sep 04 08:21:24 proxmoxsrv pvestatd[1161]: VM 300104 qmp command failed - VM 300104 qmp command 'query-proxmox-support' failed - unable to connect to VM 300104 qmp socket - timeout after 51 retries

Sep 04 08:21:24 proxmoxsrv pvestatd[1161]: status update time (8.594 seconds)

Sep 04 08:21:35 proxmoxsrv pvestatd[1161]: VM 300104 qmp command failed - VM 300104 qmp command 'query-proxmox-support' failed - unable to connect to VM 300104 qmp socket - timeout after 51 retries

Sep 04 08:21:35 proxmoxsrv pvestatd[1161]: status update time (8.598 seconds)

Sep 04 08:21:44 proxmoxsrv pvestatd[1161]: VM 300104 qmp command failed - VM 300104 qmp command 'query-proxmox-support' failed - unable to connect to VM 300104 qmp socket - timeout after 51 retries

Sep 04 08:21:45 proxmoxsrv pvestatd[1161]: status update time (8.594 seconds)

Sep 04 08:21:54 proxmoxsrv pvestatd[1161]: VM 300104 qmp command failed - VM 300104 qmp command 'query-proxmox-support' failed - unable to connect to VM 300104 qmp socket - timeout after 51 retries

Sep 04 08:21:54 proxmoxsrv pvestatd[1161]: status update time (8.595 seconds)

 

[andaga]

You have installed ProxMox into a VM? So an hypervisor into an hypervisor? Maybe because virtualization into virtulization is absolutly not recommended.