VM 300 qmp command 'cont' failed - unable to connect to VM 300 qmp socket - timeout after 450 retries

O

ollibraun

Member
Proxmox Subscriber
Jan 28, 2023
68
16
13
Hallo,

ich habe einen PBS 9.1.2 installiert (in einer VM unter PVE 9.1.2) und versuche erstmalig eine Sicherung auszuführen, einen Windows Server 2019 (VirtIO 0.1.285-1).

Es kommt reproduzierbar dieser Fehler; in welche Richtung muss ich denn hier wegen Ursachensuche denken?

Code: 
INFO: starting new backup job: vzdump 300 --mode snapshot --storage F-T-PBS --fleecing 0 --prune-backups 'keep-all=1' --notification-mode notification-system --node proxmox --notes-template '{{guestname}}' --all 0
INFO: Starting Backup of VM 300 (qemu)
INFO: Backup started at 2025-12-22 17:41:21
INFO: status = running
INFO: VM Name: Server
INFO: include disk 'scsi0' 'local-lvm:vm-300-disk-1' 144G
INFO: include disk 'scsi1' 'local-lvm:vm-300-disk-2' 200G
INFO: include disk 'scsi2' 'pve-daten:vm-300-disk-0' 2499G
INFO: include disk 'efidisk0' 'local-lvm:vm-300-disk-0' 4M
INFO: include disk 'tpmstate0' 'local-lvm:vm-300-disk-3' 4M
INFO: backup mode: snapshot
INFO: ionice priority: 7
INFO: creating Proxmox Backup Server archive 'vm/300/2025-12-22T16:41:21Z'
INFO: attaching TPM drive to QEMU for backup
INFO: issuing guest-agent 'fs-freeze' command
INFO: issuing guest-agent 'fs-thaw' command
ERROR: VM 300 qga command 'guest-fsfreeze-thaw' failed - got timeout
INFO: started backup task 'd19b8fdb-571c-469e-b0ee-870229ab6feb'
INFO: resuming VM again
ERROR: VM 300 qmp command 'cont' failed - unable to connect to VM 300 qmp socket - timeout after 450 retries
INFO: aborting backup job
INFO: resuming VM again
ERROR: Backup of VM 300 failed - VM 300 qmp command 'cont' failed - unable to connect to VM 300 qmp socket - timeout after 450 retries
INFO: Failed at 2025-12-22 17:46:08
INFO: Backup job finished with errors
INFO: notified via target `mail-to-root`
TASK ERROR: job errors

Vielen Dank für Eure Unterstütung,
Oliver
 
Last edited:
ollibraun said:
Hallo,

ich habe einen PBS 9.1.2 installiert (in einer VM unter PVE 9.1.2) und versuche erstmalig eine Sicherung auszuführen, einen Windows Server 2019 (VirtIO 0.1.285-1).

Es kommt reproduzierbar dieser Fehler; in welche Richtung muss ich denn hier wegen Ursachensuche denken?

Code: 
INFO: starting new backup job: vzdump 300 --mode snapshot --storage F-T-PBS --fleecing 0 --prune-backups 'keep-all=1' --notification-mode notification-system --node proxmox --notes-template '{{guestname}}' --all 0
INFO: Starting Backup of VM 300 (qemu)
INFO: Backup started at 2025-12-22 17:41:21
INFO: status = running
INFO: VM Name: Server
INFO: include disk 'scsi0' 'local-lvm:vm-300-disk-1' 144G
INFO: include disk 'scsi1' 'local-lvm:vm-300-disk-2' 200G
INFO: include disk 'scsi2' 'pve-daten:vm-300-disk-0' 2499G
INFO: include disk 'efidisk0' 'local-lvm:vm-300-disk-0' 4M
INFO: include disk 'tpmstate0' 'local-lvm:vm-300-disk-3' 4M
INFO: backup mode: snapshot
INFO: ionice priority: 7
INFO: creating Proxmox Backup Server archive 'vm/300/2025-12-22T16:41:21Z'
INFO: attaching TPM drive to QEMU for backup
INFO: issuing guest-agent 'fs-freeze' command
INFO: issuing guest-agent 'fs-thaw' command
ERROR: VM 300 qga command 'guest-fsfreeze-thaw' failed - got timeout
INFO: started backup task 'd19b8fdb-571c-469e-b0ee-870229ab6feb'
INFO: resuming VM again
ERROR: VM 300 qmp command 'cont' failed - unable to connect to VM 300 qmp socket - timeout after 450 retries
INFO: aborting backup job
INFO: resuming VM again
ERROR: Backup of VM 300 failed - VM 300 qmp command 'cont' failed - unable to connect to VM 300 qmp socket - timeout after 450 retries
INFO: Failed at 2025-12-22 17:46:08
INFO: Backup job finished with errors
INFO: notified via target `mail-to-root`
TASK ERROR: job errors

Vielen Dank für Eure Unterstütung,
Oliver
Click to expand...
Teste mal wie im Wiki Beschrieben die Option 5
https://pve.proxmox.com/wiki/VM_Backup_Consistency
 
Schau mal bitte im Windows Eventlog ob da ein Fehler steht.
Sonst bleibt nur den Guest Freeze abzuschalten.
 
You must log in or register to reply here.
Top Bottom