I agree with
@drjaymz@ - it is NOT fsfreeze, guest agent or snapshot as such.
I replicate every 15 minutes with no probem.
I have 2 vm that has this issue (and lots that don't). (Ubuntu 20.04 fully updated)
One VM has guest running, with 'freeze-fs-on-backup: Disabled', the other VM with no guest installed and Guest Disabled.
(2 different physical servers in 2 differet locations)
Frozen state:
I can open the VM Console from PVE and I can see the text on the VM console - but it is unresponsive.
From PVE shell:
Code:
root@pm2:~# qm status 303
status: running
So status is 'running' - but this is clearly false, as the vm is frozen.
From PVE on the VM with guest running, I tried
This returns something like 'guest not running' when it is frozen.
When the VM is running normaly I get:
Code:
root@pm2:~# qm guest exec 303 "test"
{
"exitcode" : 1,
"exited" : 1
}
From backup log:
303: 2023-05-25 02:21:04 INFO: Starting Backup of VM 303 (qemu)
303: 2023-05-25 02:21:04 INFO: status = running
303: 2023-05-25 02:21:04 INFO: VM Name: Omstillingsbordet
303: 2023-05-25 02:21:04 INFO: include disk 'scsi0' 'local-zfs:vm-303-disk-0'
303: 2023-05-25 02:21:04 INFO: include disk 'scsi1' 'local-zfs:vm-303-disk-1'
303: 2023-05-25 02:21:04 INFO: backup mode: snapshot
303: 2023-05-25 02:21:04 INFO: ionice priority: 7
303: 2023-05-25 02:21:04 INFO: creating Proxmox Backup Server archive 'vm/303/2023-05-25T00:21:04Z'
303: 2023-05-25 02:21:05 INFO: started backup task 'e37c0716-9016-4a92-b12b-82b75d90a6ec'
303: 2023-05-25 02:21:05 INFO: resuming VM again
303: 2023-05-25 02:21:05 INFO: scsi0: dirty-bitmap status: OK (1.0 GiB of 50.0 GiB dirty)
303: 2023-05-25 02:21:05 INFO: scsi1: dirty-bitmap status: OK (928.0 MiB of 200.0 GiB dirty)
I loose access at 02:21:04 - and a
is necessary.
This freezing is random but (In my case) ALWAYS in connection with a backup to PBS.