date/time inaccurate at boot for Linux VMs


  • Hello, we have Debian 8 VMs which get inaccurate date and time when booting. During boot/startup the OS should get time from the host, but this seems to not be the case here, since some VMs get date/time up to 2 months into the future (as can be seen in system logs). This is fatal for some of the services that are running in the VMs (DNS, certificates etc.).

    Just to be clear, I'm not talking about time synchronization once the VM is booted, ie. against NTP or time synchronization via Hyper-V IC, but the the date/time the VM is supposed to get from the host at boot time, since it doesn't have its own hardware RTC.

    The host has correct date/time, Windows VMs get the right date/time at boot, Linux VMs don't. Timezone in the guest is also correct, however even if it wasn't, such large difference couldn't be attributed to wrong timezone anyway.

    How can we fix this?

    Hypervizor: Hyper-V Server 2016 (but the issue was also present on Windows Server 2016 editions and back on Windows Server 2012 R2 too), fully patched

    Wednesday, December 20, 2017 5:54 AM

All replies