On 08/12/20 22:20, Thomas Gleixner wrote:
So now life migration comes a long time after timekeeping had set the
limits and just because it's virt it expects that everything works and it
just can ignore these limits.
TBH. That's not any different than SMM or hard/firmware taking the
machine out for lunch. It's exactly the same: It's broken.
I agree. If *live* migration stops the VM for 200 seconds, it's broken.
Sure, there's the case of snapshotting the VM over the weekend. My
favorite solution would be to just put it in S3 before doing that. *Do
what bare metal does* and you can't go that wrong.
In general it's userspace policy whether to keep the TSC value the same
across live migration. There's pros and cons to both approaches, so KVM
should provide the functionality to keep the TSC running (which the
guest will see as a very long, but not extreme SMI), and this is what
this series does. Maxim will change it to operate per-VM. Thanks
Thomas, Oliver and everyone else for the input.
Paolo
