Yes, and it isn't. Any ideas why it's not? This patch really just uses
the guest visible kvmclock time rather than the host view of it on
migration.
There is definitely something very broken on the host's side since it
does return a smaller time than the guest exposed interface indicates.
Don't know if helps but here are example values from time_at_migration
and s->clock from your patch.
Tested on 5 restores of saved VM that (used to) hang:
s->clock time_at_migration
157082235125698 157113284546655
157082235125698 157113298196976
157082235125698 157113284615117
157082235125698 157113284486601
157082235125698 157113284479740
Now, when I compare system time on guest with and without patch:
On unpatched qemu vm restores with date: Apr 18 06:56:36
On patched qemu it says: Apr 18 06:57:06
--
mg
