Hi, Somewhere there is an article about the evils of syncing to your system clock, or at least doing it in a very specific way. Unless you run an ntpd on your HostOS, you can't run an ntp client pointing to your Host.' The proper way to implement is to point all your machines (both HostOS and Guests) to some highly available network ntpd. For those running network security, this might be a Domain Controller. For most others, this probably would mean pointing to a ntpd on the Internet. Tony On Mon, Mar 16, 2015 at 4:16 AM, Per Jessen <per@opensuse.org> wrote:
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 guess it's not causing any problems, but I'd like to understand what it means.
Having done some more research, it seems to be due to my not running ntpd on the guests. Is it possible to have a guest ntpd sync'ing directly to the dom0 clock, i.e. without causing any network traffic?
-- Per Jessen, Zürich (9.3°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland.
-- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-virtual+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-virtual+owner@opensuse.org