From: Kay Sievers Date: Sun, 15 Mar 2015 18:44:59 +0000 (+0100) Subject: timesyncd: enable timesyncd in virtual machines X-Git-Tag: v219.0~297 X-Git-Url: https://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?p=elogind.git;a=commitdiff_plain;h=4b16233e59b3edd8338819dad275cc94b5e5f6e7 timesyncd: enable timesyncd in virtual machines On Fri, Mar 13, 2015 at 8:25 PM, Michael Marineau wrote: > Currently systemd-timesyncd.service includes > ConditionVirtualization=no, disabling it in both containers and > virtual machines. Each VM platform tends to deal with or ignore the > time problem in their own special ways, KVM/QEMU has the kernel time > source kvm-clock, Xen has had different schemes over the years, VMware > expects a userspace daemon sync the clock, and other platforms are > content to drift with the wind as far as I can tell. > > I don't know of a robust way to know if a platform needs a little > extra help from userspace to keep the clock sane or not but it seems > generally safer to try than to risk drifting. Does anyone know of a > reason to leave timesyncd off by default? Otherwise switching to > ConditionVirtualization=!container should be reasonable. --- diff --git a/units/systemd-timesyncd.service.in b/units/systemd-timesyncd.service.in index 39edafc8d..8219c95a0 100644 --- a/units/systemd-timesyncd.service.in +++ b/units/systemd-timesyncd.service.in @@ -9,7 +9,7 @@ Description=Network Time Synchronization Documentation=man:systemd-timesyncd.service(8) ConditionCapability=CAP_SYS_TIME -ConditionVirtualization=no +ConditionVirtualization=!container DefaultDependencies=no RequiresMountsFor=/var/lib/systemd/clock After=systemd-remount-fs.service systemd-tmpfiles-setup.service systemd-sysusers.service