Bug 956741

Summary:	When RHEL VMs are powered off/on time is off by as much as 3 hrs when system comes back up
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Allie DeVolder <adevolder>
Component:	ovirt-engine	Assignee:	Martin Polednik <mpoledni>
Status:	CLOSED ERRATA	QA Contact:	Lukas Svaty <lsvaty>
Severity:	high	Docs Contact:
Priority:	high
Version:	3.1.0	CC:	acathrow, batkisso, chetan, cpelland, dornelas, dossow, iheim, jkt, jraju, lpeer, lyarwood, mavital, michal.skrivanek, mpoledni, pstehlik, Rhev-m-bugs, rhodain, sbonazzo, sdodson, sherold, yeylon
Target Milestone:	---	Keywords:	ZStream
Target Release:	3.3.2
Hardware:	All
OS:	Linux
Whiteboard:	virt
Fixed In Version:	is35	Doc Type:	Release Note
Doc Text:	Previously, the time zone for a Red Hat Enterprise Linux virtual machine could be set in the Initial Run tab of the New or Edit Virtual Machine window. Now, the default time zone which is Etc/GMT is used, and it cannot be changed via the administration portal. After an upgrade, the time zones of all Red Hat Enterprise Linux virtual machines are reset to Etc/GMT. If you are using a Linux virtual machine with a non-default time zone, adjust its hardware clock to your desired time zone.	Story Points:	---
Clone Of:
Clones:	967861 (view as bug list)		Environment:
Last Closed:	2014-04-09 17:52:54 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1062615
Bug Blocks:	967861

Description Allie DeVolder 2013-04-25 14:15:29 UTC

Description of problem:
When RHEL VMs are powered off/on time is off by as much as 3 hrs when system comes back up

Version-Release number of selected component (if applicable):
3.1

How reproducible:
haven't managed to reproduce it locally

Steps to Reproduce:
1. Stop VM
2. Restart VM
3. Check time in guest
  
Actual results:
Time is off by exactly 1 or 3 hours, depending on VM

Expected results:
Time in VM should be correct

Comment 7 Saveliev Peter 2013-04-29 14:34:21 UTC

I also did not manage to reproduce the issue. Could you please submit as well qemu and libvirt logs from the hypervisor to make post-mortem analisys? It is needed to review qemu startup command line.

I suspect, the issue can be caused not by RHEV at all, but by the guest.

Comment 18 Saveliev Peter 2013-05-15 14:05:27 UTC

The fix was proposed.

Comment 23 Michal Skrivanek 2013-05-27 12:46:45 UTC

we need our side then, libvirt is just updating doc

Comment 24 Michal Skrivanek 2013-05-28 10:54:07 UTC

we need a solution for upgrade as well. At least a process how to reset it to correct value.

After discussion with Andy we rather should not allow Linux OSes to configure TZ as they all assume UTC by default anyway and there's no point in setting anything else as a HW clock base. And for Windows we should perhaps re-use the TZ setting from Initial Run tab to be actually applied all the time (or use Guest Agent for monitoring the current one in the guest) and supply it for every power up operation instead of tracking and storing rtc updates. For time drift difference it may also be preferable to actually correct the time instead of carrying over the wrong drift.

Comment 31 Michal Skrivanek 2014-02-24 14:49:51 UTC

Note for a complete fix bug 1062615 would need to get in as well. Without it the TZ is not changeable

Comment 35 errata-xmlrpc 2014-04-09 17:52:54 UTC

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.

http://rhn.redhat.com/errata/RHBA-2014-0384.html