On 2016-09-01 16:03, Per Jessen wrote:
Carlos E. R. wrote:
ntpd I taboo in all vmware guest installs per the recommendation from Vmware: the clock should be adjusted and trimmed only on the host CPU, not on the guests.
Funny, exactly the opposite on xen, otherwise systemd keeps complaining about the clock being adjusted.
Ah, I haven't tested that part yet.
systemd keeps saying "Time has been changed".
Not here. linux-qyxj:~ # journalctl | grep "Time has" Aug 31 17:28:42 linux-qyxj systemd[1]: Time has been changed Sep 01 19:26:48 linux-qyxj systemd[1602]: Time has been changed Sep 01 19:26:48 linux-qyxj systemd[1204]: Time has been changed Sep 01 19:26:48 linux-qyxj systemd[1]: Time has been changed linux-qyxj:~ # There is an hibernation in the middle, which explains the lapse.
See perhaps this thread. https://lists.opensuse.org/opensuse-virtual/2015-03/msg00015.html
Well, my knowledge of XEN is very limited.
Removing ntpd causes the installation to halt midprocess and complain of an error. Hitting continue works.
That sounds like a bug.
Ah, possibly.
Just saw it - it says "Error: Cannot adjust 'NTP' service.", it's one of the last steps " Writing NTP Configuration... ".
Yes, that one.
Probably other virtualization technology have the same issue, do not use ntp. I do not know for certain.
With xen, my guests run ntpd and have xen.independent_wallclock=1.
And both host and guest try to adjust the speed of the mother board hardware clock chip? (not the bios clock, that's a very different one).
No, only the Dom0 does that. The guests are independent when you use xen.independent_wallclock=1.
http://www.novell.com/documentation/vmserver/config_options/data/b9qzhq5.htm...
But if you run the ntp daemon on guests, it tries to adjust the speed of the clock there. That's how it works. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)