http://bugs.winehq.org/show_bug.cgi?id=33788
Bug #: 33788 Summary: The VMs clock is off Product: Wine-Testbot Version: unspecified Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: unknown AssignedTo: wine-bugs@winehq.org ReportedBy: fgouget@codeweavers.com Classification: Unclassified
The issue is that WineTestBot restores running VM snapshots. So when these start their clock is still set to whenever the snapshot was taken which can be months ago. VMware had a special driver that took care of updating the VM clock automatically when starting the snapshot but QEmu/KVM does not.
The VMs may synchronize with an Internet clock eventually depending on thet particular Windows' default configuration and how often they do so.
This has an impact on some tests and causes failures. My understanding is that in particular the certificate tests check that some online certificates have expired. But obviously if the VM's clock is still running months behind it may not consider the certificate to have expired yet.
These tests should arguably compare the system clock with the certificate expiration date and realize that the certificate has not expired yet. However that's not the point of the test.
The solution is to force the VM clock to resynchronize by running a special command when we start the snapshot. These commands depend on the Windows version :-(
Windows >= 2003 w32tm /config /syncfromflags:manual /manualpeerlist:0.pool.ntp.org,1.pool.ntp.org,2.pool.ntp.org,3.pool.ntp.org
Windows XP net time /setsntp:"0.pool.ntp.org 1.pool.ntp.org 2.pool.ntp.org"