Per Jessen wrote: > Carlos E. R. wrote: > >> On 2016-09-02 16:00, Per Jessen wrote: >>> Continued from opensuse-factory: >> >> (by the way, this was >> https://bugzilla.novell.com/show_bug.cgi?id=773323) > > I didn't know that one, but it seems to be about local vs UTC time? > >>>> But if you run the ntp daemon on guests, it tries to adjust the >>>> speed of the clock there. That's how it works. >>> >>> Of course, that's what you want it to do. You want the guest clock >>> synchronized. It would appear to be a good idea to have ntp on the >>> xen Dom0 govern the clock for all the guests, but in my experience >>> systemd does not like that. >> >> Yes, we want the clock synchronized, but not by adjusting the speed >> on guests. Just copied from the host. It adds load on the virtualized >> hardware. > > Yes, the obvious way seems to be to just leave the guests to trust the > synchronized clock from the Dom0. The load is negligible, especially > on a typical virtual host.
I don't know if anybody cares much, but on a xen guest running Leap422b1 with ntp disabled, I no longer see those "Time has been changed" messages apart from once or twice. (I used to have them twice a minute). I'll leave it running for a while and see what happens. Does anyone here have an opinion on the matter? -- Per Jessen, Zürich (21.1°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: [email protected] To contact the owner, e-mail: [email protected]
