On Wed, 22 Oct 2014, Mike Surcouf wrote:
> I get that NTP can be installed locally. This is how I regulate time
> on my guests. I agree the admin argument probably doesn't stand up.
>
> The problem is hyperv_clocksource (pluggable time source used by
> hyperv guests) is systematically fast in my environment. by around
> -250 PPM.
> I get away with NTP (just).
> However others have had to use tickadj to get hyperv_clocksource close
> enough for NTP to work i.e. inside +/-500 PPM. (This IS outside normal
> admin tasks)
>
> So if we are going to use NTP as the solution for hyperv guests (which
> is a valid one) the systematic drift of hyperv_clocksource in
> different environments will need to be addressed. Maybe this patch
> could be modified to tune the tick count on boot before NTP starts and
> then leave it alone so NTP can take over.
How about fixing hyperv_clocksource in the first place?
Thanks,
tglx
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
