On Tue, Oct 18, 2016 at 10:52:14PM +0200, Radim Krčmář wrote:
> The main problem is that QEMU changes virtual_tsc_khz when migrating
> without hardware scaling, so KVM is forced to get nanoseconds wrong ...
> If QEMU doesn't want to keep the TSC frequency constant, then it would
> be better if it didn't expose TSC in CPUID -- guest would just use
> kvmclock without being tempted by direct TSC accesses.

Isn't enough to simply not expose invtsc? Aren't guests expected
to assume the TSC frequency can change if invtsc isn't set on


Reply via email to