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.
>From http://wiki.xensource.com/wiki/Xen_FAQ_DomU : > I have problem with domU clock. It lose 30 minutes each day. How can i > synchronize it with dom0 clock? > > Is this PV domU? If yes, setting /proc/sys/xen/independent_wallclock > to 0 (the default) should make it sync with dom0. You only need ntp on > dom0, and domUs will follow. This is the setup I started out with, and where I see systemd reporting "Time has been changed" about once a minute. OTOH, that same paragraph also says: > The alternative, set /proc/sys/xen/independent_wallclock to 1 and run > ntp on domU. Which is what I am doing now. No systemd messages. Most confusing, to be honest. -- Per Jessen, Zürich (8.6°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: [email protected] To contact the owner, e-mail: [email protected]
