VM Unresponsive after update

meichthys

Well-Known Member
Sep 25, 2019
43
7
48
36
After updating my proxmox host node (and ProxmoxBackupServer) on 5/29/2026 (included 7.xx kernel), the PBS server (running as a VM - I know it's not best practice) randomly (but only about once a day) becomes unresponsive. It doesn't seem to happen on any kind of predictable schedule or on the start of a job. When it happens, I cannot ping the machine despite the proxmox interface showing the VM as running (but can't access console via the proxmox web UI or interact with VM). When the crash happens i don't see anything on the VM logs or in dmesg -the logs just cut off with no errors or warnings.

Environment:
3 node proxmox cluster updated to current (no-subscription repo).
1 PBS VM on the cluster with USB pass-through disks (We rotate external backup drives weekly and keep them offsite)

Host node config:

`pveversion -v`
Code:
proxmox-ve: 9.2.0 (running kernel: 7.0.6-2-pve)
pve-manager: 9.2.3 (running version: 9.2.3/d0fde103346cf89a)
proxmox-kernel-helper: 9.2.0
proxmox-kernel-7.0: 7.0.6-2
proxmox-kernel-7.0.6-2-pve-signed: 7.0.6-2
proxmox-kernel-6.17: 6.17.13-13
proxmox-kernel-6.17.13-13-pve-signed: 6.17.13-13
proxmox-kernel-6.17.13-2-pve-signed: 6.17.13-2
proxmox-kernel-6.17.13-1-pve-signed: 6.17.13-1
proxmox-kernel-6.17.9-1-pve-signed: 6.17.9-1
proxmox-kernel-6.17.4-1-pve-signed: 6.17.4-1
proxmox-kernel-6.8: 6.8.12-17
proxmox-kernel-6.8.12-17-pve-signed: 6.8.12-17
proxmox-kernel-6.8.12-9-pve-signed: 6.8.12-9
ceph-fuse: 19.2.3-pve4
corosync: 3.1.10-pve2
criu: 4.1.1-1
frr-pythontools: 10.6.1-1+pve2
ifupdown2: 3.3.0-1+pmx12
ksm-control-daemon: 1.5-1
libjs-extjs: 7.0.0-5
libproxmox-acme-perl: 1.7.1
libproxmox-backup-qemu0: 2.0.2
libproxmox-rs-perl: 0.4.1
libpve-access-control: 9.1.1
libpve-apiclient-perl: 3.4.2
libpve-cluster-api-perl: 9.1.6
libpve-cluster-perl: 9.1.6
libpve-common-perl: 9.1.13
libpve-guest-common-perl: 6.0.3
libpve-http-server-perl: 6.0.5
libpve-network-perl: 1.6.6
libpve-notify-perl: 9.1.6
libpve-rs-perl: 0.15.3
libpve-storage-perl: 9.1.5
libspice-server1: 0.15.2-1+b1
lvm2: 2.03.31-2+pmx1
lxc-pve: 7.0.0-2
lxcfs: 7.0.0-pve1
novnc-pve: 1.7.0-1
proxmox-backup-client: 4.2.1-1
proxmox-backup-file-restore: 4.2.1-1
proxmox-backup-restore-image: 1.0.0
proxmox-firewall: 1.2.3
proxmox-kernel-helper: 9.2.0
proxmox-mail-forward: 1.0.3
proxmox-mini-journalreader: 1.6
proxmox-offline-mirror-helper: 0.7.4
proxmox-widget-toolkit: 5.2.3
pve-cluster: 9.1.6
pve-container: 6.1.10
pve-docs: 9.2.2
pve-edk2-firmware: 4.2025.05-2
pve-esxi-import-tools: 1.0.1
pve-firewall: 6.0.4
pve-firmware: 3.18-4
pve-ha-manager: 5.2.4
pve-i18n: 3.7.5
pve-qemu-kvm: 11.0.0-4
pve-xtermjs: 6.0.0-1
qemu-server: 9.1.16
smartmontools: 7.5-pve2
spiceterm: 3.4.2
swtpm: 0.8.0+pve3
vncterm: 1.9.2
zfsutils-linux: 2.4.2-pve1


`uname -r`
Code:
Linux proxity 7.0.6-2-pve #1 SMP PREEMPT_DYNAMIC PMX 7.0.6-2 (2026-05-29T11:08Z) x86_64 GNU/Linux


PBS VM config:
Code:
agent: 1,fstrim_cloned_disks=1
boot: order=scsi0
cores: 4
memory: 6000
meta: creation-qemu=6.2.0,ctime=1659379246
name: backup
net0: virtio=52:60:55:68:48:E5,bridge=vmbr0,firewall=1
numa: 0
onboot: 1
ostype: l26
parent: pre_kernel_revert
scsi0: local-zfs:vm-105-disk-0,discard=on,size=20G,ssd=1
scsi1: local-zfs:vm-105-disk-1,backup=0,discard=on,replicate=0,size=3584G,ssd=1
scsihw: virtio-scsi-pci
smbios1: uuid=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
sockets: 1
startup: up=120
tablet: 0
usb0: host=2-3
vga: qxl
vmgenid: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
 
same like me, did not know how to fix yet.
 
  • Like
Reactions: meichthys