Bug 960931

Summary:	PRD33 - RFE: live snapshot with cpu/memory/disk status
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	jwang
Component:	RFEs	Assignee:	Arik <ahadas>
Status:	CLOSED ERRATA	QA Contact:	Meital Bourvine <mbourvin>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	unspecified	CC:	aburden, acanan, acathrow, ahadas, gickowic, iheim, lpeer, mbourvin, michal.skrivanek, nlevinki, yeylon
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	3.3.0
Hardware:	All
OS:	Linux
URL:	http://www.ovirt.org/Features/RAM_Snapshots
Whiteboard:	virt
Fixed In Version:	is6	Doc Type:	Enhancement
Doc Text:	It is now possible to save the state of a virtual machine's memory when creating a live snapshot, and restore a virtual machine's memory to the state captured in the snapshot.	Story Points:	---
Clone Of:
Clones:	976625 (view as bug list)		Environment:
Last Closed:	2014-01-21 17:20:36 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:	970559, 988229
Bug Blocks:	976625, 978140, 978143, 1019470

Comment 1 jwang 2013-05-08 10:30:50 UTC

See also:
https://docspace.corp.redhat.com/docs/DOC-144006

Comment 2 jwang 2013-05-08 10:38:00 UTC

1. Proposed title of this feature request
create live snapshot with cpu/memory/disk status and restore from snapshot with cpu/memory/disk status when vm is running.

Comment 3 Michal Skrivanek 2013-05-10 05:44:50 UTC

adding feature page

Comment 4 Michal Skrivanek 2013-07-12 06:50:45 UTC

merged to master:
http://gerrit.ovirt.org/gitweb?p=ovirt-engine.git;a=commit;h=5785814aba161d69deb50679679fa4ed67f58a18
http://gerrit.ovirt.org/gitweb?p=vdsm.git;a=commit;h=340bcc16f5f7b07399446adbfb34cb72f1859bbf
http://gerrit.ovirt.org/gitweb?p=ovirt-engine.git;a=commit;h=e2f630e4c74763347573fa3849172a515c69c845
http://gerrit.ovirt.org/gitweb?p=ovirt-engine.git;a=commit;h=1f6619da7eaacaea19a8e9a5f7e6f673983599fe
http://gerrit.ovirt.org/gitweb?p=ovirt-engine.git;a=commit;h=0b60711ca05a6e3d8e32bd726a8930c1dc0490f0
http://gerrit.ovirt.org/gitweb?p=ovirt-engine.git;a=commit;h=c7557e019c04e5767b5277b8ee18a5456b56fa8f
http://gerrit.ovirt.org/gitweb?p=ovirt-engine.git;a=commit;h=0bed76fad17b71cd7278d97e01cb8ea83d5d0827
http://gerrit.ovirt.org/gitweb?p=ovirt-engine.git;a=commit;h=582faec605018a86d6e489e3facf74e5d66d7416
http://gerrit.ovirt.org/gitweb?p=ovirt-engine.git;a=commit;h=4ae4e0b62c9d141f84ca39fd963f765d9592aeca
http://gerrit.ovirt.org/gitweb?p=ovirt-engine.git;a=commit;h=436787cb1491bd823ab2094e45e1785f502b4669
http://gerrit.ovirt.org/gitweb?p=ovirt-engine.git;a=commit;h=7b008a311957e32bb11e8975fce6ecbd473d1360
http://gerrit.ovirt.org/gitweb?p=ovirt-engine.git;a=commit;h=f8e2f0e39a341b29803d47b36696084139e52495
http://gerrit.ovirt.org/gitweb?p=ovirt-engine.git;a=commit;h=62ac2f6d41beb9e69be2cd8227c3763b30c4bcad
http://gerrit.ovirt.org/gitweb?p=ovirt-engine.git;a=commit;h=bd56587588ba3a5bc2e26003129db0dce502001e
http://gerrit.ovirt.org/gitweb?p=ovirt-engine.git;a=commit;h=88a18702e97e8dc74702f050f4e3d85d57f99b86
http://gerrit.ovirt.org/gitweb?p=ovirt-engine.git;a=commit;h=6710c5d81c359957be203712a0061212de2db78f

Comment 6 Aharon Canan 2013-09-08 07:53:33 UTC

marking as verified following https://tcms.engineering.redhat.com/run/81383/

Comment 7 Charlie 2013-11-28 00:12:37 UTC

This bug is currently attached to errata RHEA-2013:15231. If this change is not to be documented in the text for this errata please either remove it from the errata, set the requires_doc_text flag to minus (-), or leave a "Doc Text" value of "--no tech note required" if you do not have permission to alter the flag.

Otherwise to aid in the development of relevant and accurate release documentation, please fill out the "Doc Text" field above with these four (4) pieces of information:

* Cause: What actions or circumstances cause this bug to present.
* Consequence: What happens when the bug presents.
* Fix: What was done to fix the bug.
* Result: What now happens when the actions or circumstances above occur. (NB: this is not the same as 'the bug doesn't present anymore')

Once filled out, please set the "Doc Type" field to the appropriate value for the type of change made and submit your edits to the bug.

For further details on the Cause, Consequence, Fix, Result format please refer to:

https://bugzilla.redhat.com/page.cgi?id=fields.html#cf_release_notes 

Thanks in advance.

Comment 9 errata-xmlrpc 2014-01-21 17:20:36 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/RHSA-2014-0038.html