When rolling back a VM snapshot that includes RAM/state, the guest resumes with the old in-guest clock from the snapshot time.
This is problematic for AD/Kerberos, databases, logs, monitoring, certificates, clusters, scheduled jobs, and any time-sensitive workload.
Other hypervisor handles this by syncing guest time after revert/resume.
Proxmox could do the same when QEMU Guest Agent is enabled by issuing guest-set-time after stateful rollback?
Suggested flow:
Option enabled:
After successful rollback of a VM snapshot with vmstate:
if VM is running after rollback
and QEMU Guest Agent is enabled
and guest agent responds to ping
then call QGA guest-set-time with host time.
This is problematic for AD/Kerberos, databases, logs, monitoring, certificates, clusters, scheduled jobs, and any time-sensitive workload.
Other hypervisor handles this by syncing guest time after revert/resume.
Proxmox could do the same when QEMU Guest Agent is enabled by issuing guest-set-time after stateful rollback?
Suggested flow:
Option enabled:
After successful rollback of a VM snapshot with vmstate:
if VM is running after rollback
and QEMU Guest Agent is enabled
and guest agent responds to ping
then call QGA guest-set-time with host time.