Yamaban wrote:
On Mon, 16 Mar 2015 09:46, Per Jessen wrote:
Per Jessen wrote: [snip]
systemd appears to be monitoring it:
from src/core/manager.c:
/* Uses TFD_TIMER_CANCEL_ON_SET to get notifications whenever * CLOCK_REALTIME makes a jump relative to CLOCK_MONOTONIC */
I won't pretend to understand what that means :-(
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 don't really like having each guest run ntpd and sync'ing with an external source, when the host's clock is already synced - maybe there's a way of having ntpd sync with the xen dom0 clock? -- Per Jessen, Zürich (8.8°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