Description of problem: I have a fedora 20 VM running on fedora 21 host. WHen I pause VM from vm-manager and then resume the machine, the time as reported by date on the VM is incorrect. It's behind real time as much as the machine stayed paused. The VM is running chronyd and has kvm-clock as the current time source. I believe it's reasonable to expect to see real time in machine to stay correct given kvm-clock is used. Otherwise pausing becomes much less useful.
There's some external info here: https://serverfault.com/questions/334698/how-to-keep-time-on-resumed-kvm-guest-with-libvirt And a libvirt thread about trying to fix this: https://www.redhat.com/archives/libvir-list/2014-February/msg00526.html https://www.redhat.com/archives/libvir-list/2014-February/msg00905.html So it's expected that users need to manually tell the VM to update its time. virt-manager can attempt this automatically though, so reassigning
We should also do this for resume from managedsave. The API is virDomainSetTime
Discussion and patches: https://www.redhat.com/archives/virt-tools-list/2019-November/msg00018.html
Michael's patches were pushed upstream now, they will be in the next release