-----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. How xen handle things I do not know, but I guess that, similarly, you should not try to discipline its clock. However, ntpd on the host should be changing the clock so slowly that nothing should notice it. Otherwise, the logs on the host might tell something about those changes. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlUHF3kACgkQja8UbcUWM1y0cAD/dJ30tbVHmVZ46uhQEPxJut8A a+VHvrvvXmemU2tnF9QA/i2ol2DSVQOrMQ0x6pzuW4RNax9BdPEyB9DPrs8SSrt3 =Flli -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org