On Fri, Dec 11 2020 at 22:59, Paolo Bonzini wrote:
> On 11/12/20 22:04, Thomas Gleixner wrote:
> The nanosecond and TSC times are sent as part of the paused-VM state at
> the very end of the live migration process.
>
> So it's still true that the time advances during live migration
> brownout; 0.1 seconds is just the final part of the live migration
> process. But for _live_ migration there is no need to design things
> according to "people are happy if their clock is off by 0.1 seconds
> only".
The problem is not the 0.1 second jump of the TSC. That's just a minor
nuisance. The problem is the incorrectness of CLOCK_REALTIME after this
operation which is far larger than 0.1s and this needs to be fixed.
> Again, save-to-disk, reverse debugging and the like are a different
> story, which is why KVM should delegate policy to userspace (while
> documenting how to do it right).
One ready to use option would be suspend to idle. It's fast and readily
available including all the notifications and kernel side handling of
time and whatever.
Thanks,
tglx
