Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
On 2015-03-16 12:05, Per Jessen wrote:
Yamaban wrote:
A hunch: the 'internal' clock in the xen guest runs to fast/slow, compared to RTC and is reset/corrected by ntp once a minute. Thus the 'MONOTONIC' is broken (a time stamp occures twice), and the message is send.
I'm not running ntp on the xen guests - it seems to be superfluous when the host is keeping the clock sync'ed. Maybe that assumption is flawed?
I think it is correct. I'm not familiar with xen, but I read a similar recommendation from vmware people: do not run ntpd on guests, but instead use guest tools to sync time with host.
That sounds a bit contradictory. Anyway, I did a lot of googling and reading yesterday - afaict, running ntpd on the guest and having xen.independent_wallclock=1 is the best/most common way. It is a little confusing to be honest.
How xen handle things I do not know, but I guess that, similarly, you should not try to discipline its clock.
I've got ntpd running fine on the host, no problems. -- Per Jessen, Zürich (9.7°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org