Tomasz Chmielewski wrote:
Why do my guests show Clocksource tsc unstable on bootup?
Linux expects the tsc to be monotonic and to have a 1:1 correspondence
with real time, which isn't easy to achieve with virtualization.
dmesg shows that kvm-clock was set as the primary cpu clock.
Yet a
Avi Kivity schrieb:
Tomasz Chmielewski wrote:
Why do my guests show Clocksource tsc unstable on bootup?
Linux expects the tsc to be monotonic and to have a 1:1 correspondence
with real time, which isn't easy to achieve with virtualization.
But the clocksource is kvm-clock, so why does the
Why do my guests show Clocksource tsc unstable on bootup?
dmesg shows that kvm-clock was set as the primary cpu clock.
Yet a bit later kernel says Clocksource tsc unstable.
Is it something to worry about, or perhaps calculating tsc is hardcoded?
And as such, will be always checked?
Or, is it
