Hi there,
when running backups on vms which have qemu-guest-agent enabled the vms will regularly crash. This seems to be a well known problem with qemu guest agent which is described like this:
The only workaround I found is disabling qemu-guest-agent entirely. If i do this i never have a crash.
Couldn't we either fix the bug or add an option to proxmox to not use fs freeze when running backup and have guest agent enabled ?
Or are there better workarounds ?
when running backups on vms which have qemu-guest-agent enabled the vms will regularly crash. This seems to be a well known problem with qemu guest agent which is described like this:
Code:
When VM backup is invoked, Qemu agent freezes the file systems, so no single change will be made during the backup. But Qemu agent does not respect the loop* devices in freezing order (we have checked its sources), which leads to the next situation:
1) freeze loopback fs
---> send async reqs to loopback thread
2) freeze main fs
3) loopback thread wakes up and trying to write data to the main fs, which is still frozen, and this finally leads to the hung task and kernel crash.
I believe this is the culprit:
/dev/loop0 /tmp ext3 rw,nosuid,noexec,relatime,data=ordered 0 0
/dev/loop0 /var/tmp ext3 rw,nosuid,noexec,relatime,data=ordered 0 0
The only workaround I found is disabling qemu-guest-agent entirely. If i do this i never have a crash.
Couldn't we either fix the bug or add an option to proxmox to not use fs freeze when running backup and have guest agent enabled ?
Or are there better workarounds ?