Olaf Hering wrote: > On Mon, Mar 16, Per Jessen wrote: > >> After having migrated a number of systems to a xen setup, I am seeing >> this "Time has been changed" message from systemd twice a minute in >> the guest systems (once per systemd daemon). The host is running >> ntpd, the guests aren't. Both host and guests are using openSUSE >> 13.2 + latest updates. > > I remember such systemd output, looks like a bug in that component. > > I dont know much about time keeping. My understanding is that Xen does > a reasonable good job of keeping dom0 and domU time in sync. I think > the only requirement or recommendation is that dom0 runs ntpd.
That's what I thought too. With that setup, I get $SUBJ though. > There is some knob to make a domU not use dom0 time, not sure if you > have that enabled for your domUs. But such knob may only apply to PV > guests. For the time being (no pun intended), I've set xen.independent_wallclock=1 on my guests and started ntpd on them too. What do other people here do? I can't help thinking ntp might/could have an option for sync'ing to the dom0, maybe a special server a la : server 127.127.1.0 # local clock (LCL) -- Per Jessen, Zürich (8.4°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: [email protected] To contact the owner, e-mail: [email protected]
