Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 988229

Summary: cannot start vm snapshotted with ram with libvirt 0.10.2
Product: [Retired] oVirt Reporter: Arik <ahadas>
Component: vdsmAssignee: Arik <ahadas>
Status: CLOSED CURRENTRELEASE QA Contact: Haim <hateya>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: abaron, acathrow, bazulay, ebenahar, gickowic, iheim, mgoldboi, michal.skrivanek, yeylon
Target Milestone: ---   
Target Release: 3.3   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: virt
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-09-23 07:32:15 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:    
Bug Blocks: 960931    

Description Arik 2013-07-25 07:15:55 UTC
Description of problem:
With libvirt 0.10.2 it is possible to take live snapshot with ram, but it is not possible to run the vm after it is reverted to this snapshot. we get the following error in vdsm: 
TypeError: restoreFlags() takes exactly 4 arguments (3 given)
The problem is that in libvirt > 1.0.1, the restoreFlags verb assign default values for its optional arguments (specifically the "flags" attribute), and in 0.10.2 they don't get default values, so when calling this verb with only 3 arguments we get an error.

Version-Release number of selected component (if applicable):
libvirt 0.10.2-18.el6

How reproducible:
100%

Steps to Reproduce:
1. Take live snapshot with ram
2. Power down the vm and revert to that snapshot
3. Run the VM

Actual results:
The run fails with the error mentioned above in vdsm log

Expected results:
The vm run and the memory from the snapshot is restored

Additional info:

Comment 2 Itamar Heim 2013-08-21 16:40:15 UTC
as RC is built, moving to ON_QA (hopefully did not catch incorrect bugs when doing this)

Comment 3 Itamar Heim 2013-09-23 07:32:15 UTC
closing as this should be in 3.3 (doing so in bulk, so may be incorrect)