On Thu, Feb 06, 2014 at 12:46:38PM -0500, Bob wrote:
I have the same issue. I have assumed it was a Windows configuration issue. I have relied on sync'ing to Internet Time upon each bootup. It would be nice to find a solution to this. My Windows VM consistently comes up exactly 5 hours off, and although NTP is configured the time is never corrected until I manually sync to Internet Time. It certainly appears to be using the wrong TZ (GMT).
I suppose you are seeing https://bugzilla.redhat.com/show_bug.cgi?id=956741 When RHEL VMs are powered off/on time is off by as much as 3 hrs when system comes back up which http://gerrit.ovirt.org/14750 should fix. Which ovirt version are you using? Would you agree to verify the patch once Martin backports it? Dan.
-Bob
On 2/6/2014 11:39 AM, Markus Stockhausen wrote:
Hello,
all my searching/reading left me more confused. My current problem is a Windows VM that has a wrong "timezone" - at least if I do not activate internet time server sync.
Settings are:
- OVirt VM definition - First Run GMT+1 - thats ok - hypervisor host: timezone CET (= GMT+1) - 18:00 - thats ok - Windows VM: timezone CET ( = GMT+1) - 17:00 - thats wrong
I got a thread that suggested to look at vm_dynamic. There we have:
select a.vm_name,b.utc_diff from vm_static a, vm_dynamic b engine-# where a.vm_guid=b.vm_guid; vm_name | utc_diff ------------------+---------- Win7x64_Master | 0
But what should that tell me?
Although we work with timeservers inside the VMs we want to ensure that even without them the VM time should match the hypervisor time.
Has anyone a simple and clear explanation how this should work.
Thanks in advance.
Markus
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users