Description of problem:
Windows 2012 guest reports incorrect time in a random manner and also after a restart.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Create a new Windows 2012 VM with Time Zone - (GMT-05:00) Central Standard Time (Mexico)
2. Start the VM
3. Verify the time on the Window guest and correct if necessary.
4. Shutdown or Poweroff the VM.
5. Start the VM and verify the time.
The time on the Windows 2012 VM is not set to correct time, it changes to UTC +0.
The time on the VM should correct based on the timezone selected in the RHEV Web UI and as per the configuration inside the OS.
For the random changes we've asked customer to disable "Internet Time Sync" inside the Windows guest and let RHEV to manage the offsets
it's not taken from utc_diff, but derived from the time zone (which should be those 18000s). So every time you start the VM it should start with offeset relative to UTC on host
how random is the time? is NTP really disabled - then it should not vary
The problem is the mapping, there's a missing mapping to the right timezone. The used timezone is valid, however internally it can't get mapped to the right java timezone, which needed to get the offset value.
I'll be having a patch for this soon and some unit test to validate this for the future.
Windows 2012x64 VM
1. Create Windows 2012 VM and install RHEV-Tools on it.
2. Run VM, Verify what is current time zone on it (in my case UTC-08:00 Pacific Time US&Canada).
3. Open VM console and navigate to date and time configuration, disable "synchronize with an internet time server").
3. Edit VM > System tab and change time zone to GMT-03:00 Greenland Standard.
4. Shut Down VM and run it again.
5. Open VM console and verify VM time shifted to GMT-03:00 (although in windows configuration it remains UTC-08:00)
Please do the verification with the reported time. Any other time should work, the problematic one was "(GMT-05:00) Central Standard Time (Mexico)"
If you do use Greenland time, that ofc works, as this wasn't broken.
OK.. I verified it again this time using "(GMT-06:00) Central Standard Time (Mexico)", which for some reason on my setup does not appear as GMT-05:00 as you mentioned.
Just to be sure I also verified it with "(GMT-05:00) Eastern Standard Time".
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.