Clock skew after resume on virtual machine

Hi, I'm a relatively experienced Windows user and have a Windows 10 system set up as a virtual machine guest on a Linux system host, and when the computer (and Windows 10 guest) resume from suspend, the clock is wrong and never resets automatically. It's necessary for me to right-click on the clock in the lower-right corner, and navigate to "Internet Time" where I can update it manually using "update now" on one of the time servers.

The system is set to use time.windows.com, but it apparently doesn't sync frequently enough to update the time after it's resumed from suspend.

I've checked to make sure the "Windows Time" service is running (it is, and set to Automatic at startup). I've also verified w32tm is configured to use time.windows.com (w32tm /query /source)

I've also gone through steps in guides similar to this one:
FULL FIX: Windows time service not running on Windows 10

Is this something that other users using Win10 as a virtual machine experience? Should it be necessary to set up a task that executes upon the system resuming? Perhaps a task that just syncs the clock every few minutes?

Linux sets the real clock (RTC) as UTC (GMT time) and windows sets the RTC as local time (LTC).

In Linux, UTC sets RTC. RTC is converted to LTC using Time zone to show on the taskbar.

In Windows, UTC is converted to LTC using Time zone and sets the RTC. What you see in the taskbar is the same as the RTC.

I don't know if it's Windows that enters sleep mode or if it is Linux.

How many minutes is the difference when you wake up from sleep?

Megahertz said:

Linux sets the real clock (RTC) as UTC (GMT time) and windows sets the RTC as local time (LTC).

In Linux, UTC sets RTC. RTC is converted to LTC using Time zone to show on the taskbar.

In Windows, UTC is converted to LTC using Time zone and sets the RTC. What you see in the taskbar is the same as the RTC.

I don't know if it's Windows that enters sleep mode or if it is Linux.

How many minutes is the difference when you wake up from sleep?

I don't believe it's a timezone issue. I do increasingly believe it's a problem with how Linux is setting the clock for the virtual machine.

The time difference is more than just a timezone difference. I think the initial time reflects the time the virtual host was last suspended. In other words, after it resumes, it either never receives an update from the host on the current time or it never probes the time server after resuming for the current time.

Hi there

@gossamer


I think in the Virtual Bios ( The BIOS set by the VM) -- to get into it depending on the Virtual Software you are using go into "Boot into Firmware" or equivalent on the VM menu. From there you can set the time for the virtual machine -- might depend on the VM software you are using.

I use Linux Hosts regularly for running Windows VM's -- no probs at all with timezones.

Check on your Linux Host that the timezone is being set correctly -- and of course from the Host Machine's BIOS as well.

Cheers
jimbo

gossamer: If you have Vmware Tools (or equivalent) installed, try to disable timesync in VM properties; it can interfere with timezone & ntp.