HA & TASK ERROR: VM is locked (backup)

YAGA

Well-Known Member
Feb 15, 2016
97
21
73
Hello,

I use the no-subscription repos of PVE and PBS, with daily updates. Since the beginning of the week, many VM backups (about 80%) to an external PBS server have been failing:

task started by HA resource agent
TASK ERROR: VM is locked (backup)

Log :
INFO: Starting Backup of VM 154 (qemu)
INFO: Backup started at 2026-11-18 21:30:40
INFO: status = stopped
INFO: backup mode: stop
INFO: ionice priority: 7
INFO: VM Name: VM154
INFO: include disk 'scsi0' 'Ext-Ceph:vm-154-disk-0' 30G
INFO: creating Proxmox Backup Server archive 'vm/154/2026-11-18T20:30:40Z'
INFO: enabling encryption
INFO: starting kvm to execute backup task
generating cloud-init ISO
INFO: starting backup via QMP command
INFO: started backup task '1b86fe03-2998-4f19-83ab-217497ff4592'
ERROR: VM 154 qmp command 'query-pbs-bitmap-info' failed - got timeout
INFO: aborting backup job
INFO: stopping kvm after backup task
trying to acquire lock...
OK
ERROR: Backup of VM 154 failed - VM 154 qmp command 'query-pbs-bitmap-info' failed - got timeout
INFO: Failed at 2026-11-18 21:30:58

However, checking the configuration files, none of the VMs appear to be locked.

Have you encountered this issue before?

Could it be related to recent kernel 7.0, PVE, or PBS updates?

Thanks a lot
 
Last edited:
I recently had the same issue with backups failing, but only for 1 VM and it was frustrating as heck to debug. I still don't know the root cause and Claude seems to think it's got something to do with rbd_diff_iterate2() getting stuck somewhere, it was way over my head and I didn't understand it. This VM was my homeassistant VM and I think it had something to do with it being write heavy with me using timescaledb as it's recorder.

This was the log for the failing backups from PVE side:
Code:
INFO: Starting Backup of VM 100 (qemu)
INFO: Backup started at 2026-11-17 11:00:01
INFO: status = running
INFO: VM Name: avocado
INFO: include disk 'scsi0' 'ceph-workloads:vm-100-disk-1' 64G
INFO: include disk 'efidisk0' 'ceph-workloads:vm-100-disk-0' 128K
INFO: backup mode: snapshot
INFO: ionice priority: 7
INFO: creating Proxmox Backup Server archive 'vm/100/2026-11-17T01:00:01Z'
INFO: issuing guest-agent 'fs-freeze' command
INFO: starting backup via QMP command
INFO: issuing guest-agent 'fs-thaw' command
INFO: started backup task '1555a3c6-165f-47f8-8e3e-be881684274d'
INFO: resuming VM again
ERROR: VM 100 qmp command 'query-pbs-bitmap-info' failed - got timeout
INFO: aborting backup job
INFO: resuming VM again
ERROR: Backup of VM 100 failed - VM 100 qmp command 'query-pbs-bitmap-info' failed - got timeout
INFO: Failed at 2026-11-17 11:00:41

And these were from PBS side:
Code:
2026-11-17T11:00:18+10:00: starting new backup on datastore 'eden' from ::ffff:127.0.0.1: "vm/100/2026-11-17T01:00:01Z"
2026-11-17T11:00:18+10:00: download 'index.json.blob' from previous backup 'vm/100/2026-11-17T00:00:01Z'.
2026-11-17T11:00:18+10:00: register chunks in 'drive-efidisk0.img.fidx' from previous backup 'vm/100/2026-11-17T00:00:01Z'.
2026-11-17T11:00:18+10:00: download 'drive-efidisk0.img.fidx' from previous backup 'vm/100/2026-11-17T00:00:01Z'.
2026-11-17T11:00:18+10:00: created new fixed index 1 ("vm/100/2026-11-17T01:00:01Z/drive-efidisk0.img.fidx")
2026-11-17T11:00:19+10:00: register chunks in 'drive-scsi0.img.fidx' from previous backup 'vm/100/2026-11-17T00:00:01Z'.
2026-11-17T11:00:19+10:00: download 'drive-scsi0.img.fidx' from previous backup 'vm/100/2026-11-17T00:00:01Z'.
2026-11-17T11:00:19+10:00: created new fixed index 2 ("vm/100/2026-11-17T01:00:01Z/drive-scsi0.img.fidx")
2026-11-17T11:00:19+10:00: add blob "/mnt/pbs/vm/100/2026-11-17T01:00:01Z/qemu-server.conf.blob" (626 bytes, comp: 626)
2026-11-17T11:00:41+10:00: backup failed: connection error
2026-11-17T11:00:41+10:00: removing failed backup
2026-11-17T11:00:41+10:00: removing backup snapshot "/mnt/pbs/vm/100/2026-11-17T01:00:01Z"
2026-11-17T11:00:41+10:00: TASK ERROR: connection error: not connected

However, the first workaround that worked on kernel 7.0.14-29 was to enable fleecing in the backup job.
Logs:
Code:
INFO: Starting Backup of VM 100 (qemu)
INFO: Backup started at 2026-11-17 23:00:04
INFO: status = running
INFO: VM Name: avocado
INFO: include disk 'scsi0' 'ceph-workloads:vm-100-disk-1' 64G
INFO: include disk 'efidisk0' 'ceph-workloads:vm-100-disk-0' 128K
INFO: backup mode: snapshot
INFO: ionice priority: 7
INFO: creating Proxmox Backup Server archive 'vm/100/2026-11-17T13:00:04Z'
  Logical volume "vm-100-fleece-0" created.
  Logical volume pve/vm-100-fleece-0 changed.
INFO: drive-scsi0: attaching fleecing image local-lvm:vm-100-fleece-0 to QEMU
INFO: issuing guest-agent 'fs-freeze' command
INFO: starting backup via QMP command
INFO: issuing guest-agent 'fs-thaw' command
INFO: started backup task 'e9ef3f11-01a6-46cf-8cba-fcf8337d0f28'
INFO: resuming VM again
INFO: efidisk0: dirty-bitmap status: OK (drive clean)
INFO: scsi0: dirty-bitmap status: OK (1.8 GiB of 64.0 GiB dirty)
INFO: using fast incremental mode (dirty-bitmap), 1.8 GiB dirty of 64.0 GiB total
INFO: 100% (1.8 GiB of 1.8 GiB) in 2s, read: 918.0 MiB/s, write: 896.0 MiB/s
INFO: backup was done incrementally, reused 62.25 GiB (97%)
INFO: transferred 1.79 GiB in 2 seconds (918.0 MiB/s)
INFO: adding notes to backup
INFO: removing (old) fleecing image 'local-lvm:vm-100-fleece-0'
  Logical volume "vm-100-fleece-0" successfully removed.
INFO: Finished Backup of VM 100 (00:00:27)
INFO: Backup finished at 2026-11-17 23:00:31

That worked for a few rounds until I upgraded my kernel to 7.3.5-1-pve and then backups started failing in the same way again.
Code:
INFO: starting new backup job: vzdump --mailto admin@pve.invalid --storage backup-tnassy --mode snapshot --notes-template '{{guestname}}' --mailnotification failure --exclude 347,340,448,140 --all 1 --quiet 1 --fleecing '1,storage=local-lvm' --notification-mode notification-system
INFO: skip external VMs: 132, 331, 333, 334, 337, 343, 350, 351, 352, 353, 354, 355, 356, 357, 443, 444, 446, 447
INFO: Starting Backup of VM 100 (qemu)
INFO: Backup started at 2026-11-18 21:00:00
INFO: status = running
INFO: VM Name: avocado
INFO: include disk 'scsi0' 'ceph-workloads:vm-100-disk-1' 64G
INFO: include disk 'efidisk0' 'ceph-workloads:vm-100-disk-0' 128K
INFO: backup mode: snapshot
INFO: ionice priority: 7
INFO: creating Proxmox Backup Server archive 'vm/100/2026-11-18T11:00:00Z'
  Logical volume "vm-100-fleece-0" created.
  Logical volume pve/vm-100-fleece-0 changed.
INFO: drive-scsi0: attaching fleecing image local-lvm:vm-100-fleece-0 to QEMU
INFO: issuing guest-agent 'fs-freeze' command
INFO: starting backup via QMP command
INFO: issuing guest-agent 'fs-thaw' command
INFO: started backup task 'fc2bd955-0237-46a0-a08d-51b13f1544a3'
INFO: resuming VM again
ERROR: VM 100 qmp command 'query-pbs-bitmap-info' failed - got timeout
INFO: aborting backup job
INFO: resuming VM again
INFO: removing (old) fleecing image 'local-lvm:vm-100-fleece-0'
  Logical volume "vm-100-fleece-0" successfully removed.
ERROR: Backup of VM 100 failed - VM 100 qmp command 'query-pbs-bitmap-info' failed - got timeout
INFO: Failed at 2026-11-18 21:00:39

However this time, it was determined that maybe because this was an older VM it was created with not optimal values, e.g. I had cache=writethrough, scsihw: virtio-scsi-pci and didn't have iothread turned on. Fixing that enabled backups for that specific VM to start working again even without fleecing e.g.
Manual run without fleecing:
Code:
INFO: starting new backup job: vzdump 100 --mode snapshot --node eden --compress zstd --storage backup-tnassy --notes-template '{{guestname}}' --remove 0
INFO: Starting Backup of VM 100 (qemu)
INFO: Backup started at 2026-11-18 21:49:54
INFO: status = running
INFO: VM Name: avocado
INFO: include disk 'scsi0' 'ceph-workloads:vm-100-disk-1' 64G
INFO: include disk 'efidisk0' 'ceph-workloads:vm-100-disk-0' 128K
INFO: backup mode: snapshot
INFO: ionice priority: 7
INFO: creating Proxmox Backup Server archive 'vm/100/2026-11-18T11:49:54Z'
INFO: issuing guest-agent 'fs-freeze' command
ERROR: unable to freeze guest fs - child process has failed to execute fsfreeze hook: File system freeze requested, freezing Home Assistant
ERROR: Error: 'BackupManager.freeze_all' blocked from execution, system is not running - startup
INFO: starting backup via QMP command
INFO: issuing guest-agent 'fs-thaw' command
ERROR: Agent error: child process has failed to execute fsfreeze hook: File system thaw requested, thawing Home Assistant
ERROR: Error: 'BackupManager.thaw_all' blocked from execution, system is not frozen - startup
INFO: started backup task '23d49e49-23c4-4c02-93a8-995c75cb9dec'
INFO: resuming VM again
INFO: efidisk0: dirty-bitmap status: created new
INFO: scsi0: dirty-bitmap status: created new
INFO:   1% (992.0 MiB of 64.0 GiB) in 3s, read: 330.7 MiB/s, write: 32.0 MiB/s
INFO:   3% (2.1 GiB of 64.0 GiB) in 6s, read: 377.3 MiB/s, write: 53.3 MiB/s
INFO:   4% (3.0 GiB of 64.0 GiB) in 9s, read: 313.3 MiB/s, write: 18.7 MiB/s
INFO:   6% (4.1 GiB of 64.0 GiB) in 12s, read: 374.7 MiB/s, write: 41.3 MiB/s
INFO:   7% (5.1 GiB of 64.0 GiB) in 15s, read: 338.7 MiB/s, write: 45.3 MiB/s
INFO:   9% (6.1 GiB of 64.0 GiB) in 18s, read: 357.3 MiB/s, write: 64.0 MiB/s
INFO:  11% (7.1 GiB of 64.0 GiB) in 21s, read: 328.0 MiB/s, write: 20.0 MiB/s
INFO:  12% (8.0 GiB of 64.0 GiB) in 24s, read: 301.3 MiB/s, write: 58.7 MiB/s
INFO:  13% (8.9 GiB of 64.0 GiB) in 27s, read: 324.0 MiB/s, write: 40.0 MiB/s
INFO:  16% (10.7 GiB of 64.0 GiB) in 30s, read: 620.0 MiB/s, write: 37.3 MiB/s
INFO:  18% (12.0 GiB of 64.0 GiB) in 33s, read: 432.0 MiB/s, write: 28.0 MiB/s
INFO:  20% (13.3 GiB of 64.0 GiB) in 36s, read: 446.7 MiB/s, write: 32.0 MiB/s
INFO:  23% (14.8 GiB of 64.0 GiB) in 39s, read: 496.0 MiB/s, write: 14.7 MiB/s
INFO:  24% (15.9 GiB of 64.0 GiB) in 42s, read: 388.0 MiB/s, write: 45.3 MiB/s
INFO:  26% (16.7 GiB of 64.0 GiB) in 45s, read: 258.7 MiB/s, write: 10.7 MiB/s
INFO:  27% (17.7 GiB of 64.0 GiB) in 48s, read: 366.7 MiB/s, write: 28.0 MiB/s
INFO:  29% (19.0 GiB of 64.0 GiB) in 51s, read: 433.3 MiB/s, write: 24.0 MiB/s
INFO:  31% (20.0 GiB of 64.0 GiB) in 54s, read: 333.3 MiB/s, write: 22.7 MiB/s
INFO:  32% (20.6 GiB of 64.0 GiB) in 57s, read: 196.0 MiB/s, write: 34.7 MiB/s
INFO:  33% (21.4 GiB of 64.0 GiB) in 1m, read: 302.7 MiB/s, write: 41.3 MiB/s
INFO:  34% (22.3 GiB of 64.0 GiB) in 1m 3s, read: 308.0 MiB/s, write: 32.0 MiB/s
INFO:  36% (23.4 GiB of 64.0 GiB) in 1m 6s, read: 365.3 MiB/s, write: 33.3 MiB/s
INFO:  38% (24.4 GiB of 64.0 GiB) in 1m 9s, read: 325.3 MiB/s, write: 14.7 MiB/s
INFO:  39% (25.3 GiB of 64.0 GiB) in 1m 12s, read: 317.3 MiB/s, write: 34.7 MiB/s
INFO:  40% (26.2 GiB of 64.0 GiB) in 1m 15s, read: 301.3 MiB/s, write: 34.7 MiB/s
INFO:  42% (27.4 GiB of 64.0 GiB) in 1m 18s, read: 400.0 MiB/s, write: 70.7 MiB/s
INFO:  44% (28.4 GiB of 64.0 GiB) in 1m 21s, read: 346.7 MiB/s, write: 34.7 MiB/s
INFO:  46% (29.5 GiB of 64.0 GiB) in 1m 24s, read: 393.3 MiB/s, write: 36.0 MiB/s
INFO:  47% (30.4 GiB of 64.0 GiB) in 1m 27s, read: 292.0 MiB/s, write: 13.3 MiB/s
INFO:  49% (31.4 GiB of 64.0 GiB) in 1m 30s, read: 365.3 MiB/s, write: 50.7 MiB/s
INFO:  51% (32.7 GiB of 64.0 GiB) in 1m 33s, read: 422.7 MiB/s, write: 22.7 MiB/s
INFO:  54% (35.0 GiB of 64.0 GiB) in 1m 36s, read: 792.0 MiB/s, write: 18.7 MiB/s
INFO:  57% (36.9 GiB of 64.0 GiB) in 1m 39s, read: 641.3 MiB/s, write: 26.7 MiB/s
INFO:  64% (41.1 GiB of 64.0 GiB) in 1m 42s, read: 1.4 GiB/s, write: 21.3 MiB/s
INFO:  68% (43.6 GiB of 64.0 GiB) in 1m 45s, read: 850.7 MiB/s, write: 5.3 MiB/s
INFO:  73% (47.3 GiB of 64.0 GiB) in 1m 48s, read: 1.2 GiB/s, write: 12.0 MiB/s
INFO:  75% (48.6 GiB of 64.0 GiB) in 1m 51s, read: 441.3 MiB/s, write: 1.3 MiB/s
INFO:  77% (49.6 GiB of 64.0 GiB) in 1m 54s, read: 333.3 MiB/s, write: 0 B/s
INFO:  80% (51.3 GiB of 64.0 GiB) in 1m 57s, read: 565.3 MiB/s, write: 10.7 MiB/s
INFO:  85% (54.4 GiB of 64.0 GiB) in 2m, read: 1.1 GiB/s, write: 20.0 MiB/s
INFO:  86% (55.3 GiB of 64.0 GiB) in 2m 3s, read: 296.0 MiB/s, write: 29.3 MiB/s
INFO:  87% (56.1 GiB of 64.0 GiB) in 2m 6s, read: 266.7 MiB/s, write: 20.0 MiB/s
INFO:  88% (56.9 GiB of 64.0 GiB) in 2m 9s, read: 280.0 MiB/s, write: 5.3 MiB/s
INFO:  92% (59.0 GiB of 64.0 GiB) in 2m 12s, read: 717.3 MiB/s, write: 4.0 MiB/s
INFO:  95% (60.9 GiB of 64.0 GiB) in 2m 15s, read: 654.7 MiB/s, write: 1.3 MiB/s
INFO:  97% (62.3 GiB of 64.0 GiB) in 2m 18s, read: 480.0 MiB/s, write: 6.7 MiB/s
INFO:  98% (63.2 GiB of 64.0 GiB) in 2m 21s, read: 301.3 MiB/s, write: 86.7 MiB/s
INFO: 100% (64.0 GiB of 64.0 GiB) in 2m 24s, read: 269.4 MiB/s, write: 49.3 MiB/s
INFO: backup is sparse: 22.34 GiB (34%) total zero data
INFO: backup was done incrementally, reused 59.93 GiB (93%)
INFO: transferred 64.00 GiB in 144 seconds (455.1 MiB/s)
INFO: adding notes to backup
INFO: Finished Backup of VM 100 (00:02:24)
INFO: Backup finished at 2026-11-18 21:52:18
INFO: Backup job finished successfully
INFO: skipping disabled matcher 'default-matcher'
INFO: skipping disabled matcher 'email-errors'
INFO: notification was not matched by any matcher
TASK OK

Automated run with fleecing:
Code:
INFO: starting new backup job: vzdump --notification-mode notification-system --fleecing '1,storage=local-lvm' --quiet 1 --all 1 --exclude 347,340,448,140 --mailnotification failure --notes-template '{{guestname}}' --mode snapshot --mailto admin@pve.invalid --storage backup-tnassy
INFO: skip external VMs: 132, 331, 333, 334, 337, 343, 350, 351, 352, 353, 354, 355, 356, 357, 443, 444, 446, 447
INFO: Starting Backup of VM 100 (qemu)
INFO: Backup started at 2026-11-18 22:00:01
INFO: status = running
INFO: VM Name: avocado
INFO: include disk 'scsi0' 'ceph-workloads:vm-100-disk-1' 64G
INFO: include disk 'efidisk0' 'ceph-workloads:vm-100-disk-0' 128K
INFO: backup mode: snapshot
INFO: ionice priority: 7
INFO: creating Proxmox Backup Server archive 'vm/100/2026-11-18T12:00:01Z'
  Logical volume "vm-100-fleece-0" created.
  Logical volume pve/vm-100-fleece-0 changed.
INFO: drive-scsi0: attaching fleecing image local-lvm:vm-100-fleece-0 to QEMU
INFO: issuing guest-agent 'fs-freeze' command
INFO: starting backup via QMP command
INFO: issuing guest-agent 'fs-thaw' command
INFO: started backup task 'ca0819f6-3ab6-4204-a534-0b880face960'
INFO: resuming VM again
INFO: efidisk0: dirty-bitmap status: OK (drive clean)
INFO: scsi0: dirty-bitmap status: OK (2.5 GiB of 64.0 GiB dirty)
INFO: using fast incremental mode (dirty-bitmap), 2.5 GiB dirty of 64.0 GiB total
INFO:  32% (840.0 MiB of 2.5 GiB) in 3s, read: 280.0 MiB/s, write: 261.3 MiB/s
INFO:  58% (1.5 GiB of 2.5 GiB) in 6s, read: 217.3 MiB/s, write: 216.0 MiB/s
INFO:  84% (2.1 GiB of 2.5 GiB) in 9s, read: 224.0 MiB/s, write: 221.3 MiB/s
INFO: 100% (2.5 GiB of 2.5 GiB) in 12s, read: 134.7 MiB/s, write: 126.7 MiB/s
INFO: backup was done incrementally, reused 61.58 GiB (96%)
INFO: transferred 2.51 GiB in 12 seconds (214.0 MiB/s)
INFO: adding notes to backup
INFO: removing (old) fleecing image 'local-lvm:vm-100-fleece-0'
  Logical volume "vm-100-fleece-0" successfully removed.
INFO: Finished Backup of VM 100 (00:00:37)
INFO: Backup finished at 2026-11-18 22:00:38

My VM config now looks like this:
Code:
agent: 1
balloon: 0
bios: ovmf
boot: order=scsi0
cores: 4
cpu: x86-64-v3
description: Home Assistant OS
efidisk0: ceph-workloads:vm-100-disk-0,size=128K
localtime: 1
machine: q35
memory: 8192
meta: creation-qemu=8.1.2,ctime=1705770693
name: avocado
net0: virtio=<some mac address>,bridge=vmbr0,tag=1
net1: virtio=<some mac address>,bridge=vmbr0,tag=99
numa: 0
onboot: 1
ostype: l26
scsi0: ceph-workloads:vm-100-disk-1,discard=on,iothread=1,size=64G,ssd=1
scsihw: virtio-scsi-single
smbios1: uuid=<blah>
sockets: 1
tablet: 0
tags:
vmgenid: <more blah>
 
Last edited:
Hello,

I've updated both PBS and PVE today, but I'm still getting the same error messages during backups. Please find the output of pveversion -v below.

I also enabled maintenance mode on one of the cluster nodes using:
ha-manager crm-command node-maintenance enable <node-name>

Unfortunately, this did not improve the situation and the backup errors are still occurring.

proxmox-ve: 9.2.0 (running kernel: 7.0.14-30-pve)
pve-manager: 9.2.31 (running version: 9.2.31/30a00e01666ece52)
proxmox-kernel-helper: 9.2.1
proxmox-kernel-7.0: 7.0.14-30
proxmox-kernel-7.0.14-30-pve-signed: 7.0.14-30
proxmox-kernel-7.0.14-29-pve-signed: 7.0.14-29
pve-kernel-5.11: 7.0-10
proxmox-kernel-6.17: 6.17.13-21
proxmox-kernel-6.17.13-21-pve-signed: 6.17.13-21
proxmox-kernel-6.14: 6.14.11-9
proxmox-kernel-6.14.11-9-pve-signed: 6.14.11-9
proxmox-kernel-6.11.11-2-pve-signed: 6.11.11-2
proxmox-kernel-6.11: 6.11.11-2
pve-kernel-5.13.19-2-pve: 5.13.19-4
pve-kernel-5.11.22-7-pve: 5.11.22-12
pve-kernel-5.11.22-1-pve: 5.11.22-2
amd64-microcode: 3.20251202.1~bpo13+1
ceph: 19.2.7-pve1
ceph-fuse: 19.2.7-pve1
corosync: 3.2.0-pve1
criu: 4.1.1-1
frr-pythontools: 10.6.1-1+pve3
ifupdown2: 3.3.0-1+pmx14
ksm-control-daemon: 1.5-1
libjs-extjs: 7.0.0-9
libproxmox-acme-perl: 1.7.3
libproxmox-backup-qemu0: 2.0.4
libproxmox-rs-perl: 0.4.3
libpve-access-control: 9.2.2
libpve-apiclient-perl: 3.4.3
libpve-cluster-api-perl: 9.1.11
libpve-cluster-perl: 9.1.11
libpve-common-perl: 9.2.11
libpve-guest-common-perl: 6.0.10
libpve-http-server-perl: 6.0.7
libpve-network-perl: 1.6.10
libpve-notify-perl: 9.1.11
libpve-rs-perl: 0.16.2
libpve-storage-perl: 9.1.18
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-2
proxmox-backup-client: 4.2.12-1
proxmox-backup-file-restore: 4.2.12-1
proxmox-backup-restore-image: 1.1.0
proxmox-enterprise-support-keyring: 1.1
proxmox-firewall: 1.2.5
proxmox-kernel-helper: 9.2.1
proxmox-mail-forward: 1.1.0
proxmox-mini-journalreader: 1.7
proxmox-offline-mirror-helper: 0.8.0
proxmox-widget-toolkit: 5.2.15
pve-cluster: 9.1.11
pve-container: 6.1.24
pve-docs: 9.2.15
pve-edk2-firmware: 4.2026.08-1
pve-esxi-import-tools: 1.0.1
pve-firewall: 6.0.8
pve-firmware: 3.18-9
pve-ha-manager: 5.2.6
pve-i18n: 3.11.0
pve-qemu-kvm: 11.1.3-2
pve-xtermjs: 6.0.0-3
qemu-server: 9.2.19
smartmontools: 7.5-pve2
spiceterm: 3.4.2
swtpm: 0.10.2+pve2
vncterm: 1.9.2
zfsutils-linux: 2.4.4-pve1