On 06/29/2009 10:11 PM, Eran Rom wrote:
Nevertheless, the tsc clock is not reliable,
the host can scale it, or
go into
deep sleep state.
indeed my current clock source is tsc
You won't get accurate timing with tsc.
So either use newer kernel with kvmclock (pv)
or change the clock source
into rtc/pit
No rtc/pit in my available clock sources, however,
I assume its a question of kernel compilation parameters,
is that right?
What is the advantage of rtc/pit/kvmclock (pv)over tsc?
They are accurate.
Also, is kvmclock (pv) better than the other two options.
Yes.
the thing is that I am 'confined' to use 2.6.27,
and if I decide on kvmclock, i will need to add it
'manually'
2.6.27 has kvmclock.
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
