| commit | 9a48bcd1b82494671c111109b0eefdb882581499 | |
| author | Alexander Graf <agraf@suse.de> | |
| Fri, 5 Sep 2014 13:52:45 +0000 (5 10:52 -0300) | ||
| committer | Paolo Bonzini <pbonzini@redhat.com> | |
| Tue, 16 Sep 2014 09:11:38 +0000 (16 11:11 +0200) | ||
| tree | ba4f2691dd1d806f617754eb4ee1d5f68ed53008 | treesnapshot (tar.gz zip) |
| parent | 317b0a6d8ba44e9bf8f9c3dbd776c4536843d82c | commitdiff |
kvmclock: Ensure time in migration never goes backward
When we migrate we ask the kernel about its current belief on what the guest
time would be. However, I've seen cases where the kvmclock guest structure
indicates a time more recent than the kvm returned time.
To make sure we never go backwards, calculate what the guest would have seen as time at the point of migration and use that value instead of the kernel returned one when it's more recent.
This bases the view of the kvmclock after migration on the
same foundation in host as well as guest.
Signed-off-by: Alexander Graf <agraf@suse.de>
Cc: qemu-stable@nongnu.org
Reviewed-by: Marcelo Tosatti <mtosatti@redhat.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
When we migrate we ask the kernel about its current belief on what the guest
time would be. However, I've seen cases where the kvmclock guest structure
indicates a time more recent than the kvm returned time.
To make sure we never go backwards, calculate what the guest would have seen as time at the point of migration and use that value instead of the kernel returned one when it's more recent.
This bases the view of the kvmclock after migration on the
same foundation in host as well as guest.
Signed-off-by: Alexander Graf <agraf@suse.de>
Cc: qemu-stable@nongnu.org
Reviewed-by: Marcelo Tosatti <mtosatti@redhat.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
| hw/i386/kvm/clock.c | diffblobblamehistory |