Il 16/05/2014 17:15, Alexander Graf ha scritto:
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,
On 19.05.14 13:31, Paolo Bonzini wrote:
Il 18/05/2014 15:20, Marcelo Tosatti ha scritto:
Reviewed-by: Marcelo Tosatti mtosa...@redhat.com
Thanks Marcelo, applying to uq/master.
Same here, please also CC to stable :).
Alex
--
To unsubscribe from this list: send the line unsubscribe kvm
Il 18/05/2014 15:20, Marcelo Tosatti ha scritto:
Reviewed-by: Marcelo Tosatti mtosa...@redhat.com
Thanks Marcelo, applying to uq/master.
Paolo
--
To unsubscribe from this list: send the line unsubscribe kvm in
the body of a message to majord...@vger.kernel.org
More majordomo info at
On Fri, May 16, 2014 at 05:15:21PM +0200, Alexander Graf wrote:
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
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
