Bug 1370230

Summary:	Restore current timestamp after restore
Product:	[Community] Virtualization Tools	Reporter:	David Ashley <w.david.ashley>
Component:	libvirt	Assignee:	Libvirt Maintainers <libvirt-maint>
Status:	NEW ---	QA Contact:
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	unspecified	CC:	libvirt-maint
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description David Ashley 2016-08-25 16:26:58 UTC

Description of problem: Currently when a domain is restored from a saved state the current time in the new running state is relative to the saved state i.e. when the domain is restored the current time in the running domain is incorrect.


Version-Release number of selected component (if applicable): N/A


How reproducible: Always.


Steps to Reproduce:
1. Save a running domain using either a managed save or a file/save.
2. Sometime later restore the domain.
3. The current time in the running domain will be relative to the saved state, not the real time or date.

Actual results: The time in the domain is never updated after a restore. Even if the domain is running the ntp daemon.


Expected results: The time in the domain should be reset to reflect the current real time.


Additional info: This should actually be easy to fix by adding a qemu-ga command after the restore (guest-set-time) so that the correct time is used by the domain. Of course, this may have consequenses for users who actually expect the time to not be reset in a restored domain. But I think this will be a small minority of users and most users would actually expect the time to changes after a restore to the current time.