Description of problem: Snapshot created while VM is in hibernate will be ignored when VM will be running again and the volume which the VM disk will write on will be the original volume it was running on Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Create VM with OS on it 2. Run the VM 4. hibernate the VM 5. Create snapshot of the VM called "snapshot1" 6. Run the VM again 7. Create folder "first folder" in the VM 8. Stop the VM 9. Preview snapshot "snapshot1" 10. Run the VM Actual results: After VM will run in preview you can see the folder that was created after the snapshot was taken Expected results: The VM should not have the folder while it is running under preview. Additional info: The cause of this might be because on running hibernated VM the engine send hibernatevol which contains the meta data which the VM is working with. VDSM reads from the hibernatevol and ignore the disks which it gets in the createVdsCommand
I wonder if snapshoting a suspended vm should also *clone* the disk containing the RAM
(In reply to comment #1) > I wonder if snapshoting a suspended vm should also *clone* the disk > containing the RAM well if it is suspended of course.
This issue is on engine backend side.
Can you specify the tested RHEVM version? I tried latest oVirt and it seems without problems according to the description.
(In reply to comment #4) > Can you specify the tested RHEVM version? It was latest upstream of 3.2 > > I tried latest oVirt and it seems without problems according to the > description. Did you verify according to the steps? Was the previewed snapshot showed the directory you created before?
Sorry, the hibernate VM in your description means to run SUSPEND command, I used shutdown VM action. It looks like snapshot created from SHUTDOWN or LIVE VM behaves correctly, but snapshot from SUSPENDED state has a problem. Investigating... Scenario 1 (OK): 1. create and run VM 2. create file Hello1 3. shutdown VM 4. create snapshot1 (VM is SHUTDOWN) 5. run VM 6. create file Hello2 7. shutdown VM 8. Select Preview snapshot1 + run VM 9. VM contains just file Hello1 Scenario 2 (OK): 1. run VM 2. remove Hello2 file 3. Create snapshot1 (LIVE) 4. create file Hello2 5. shutdown VM 6. Preview snapshot1 7. VM contains just file Hello1 Scenario 3 (ERROR): 1. run VM 2. remove Hello2 file 3. SUSPEND VM 4. create snapshot1 5. create file Hello2 6. shutdown VM 7. Preview snapshot1 7. VM contains file Hello2, and it shouldn't
If the system allows you to take a snapshot at a suspended VM state, it should be able to perfrom this tasks fully. Therefore it is a bug. As our current design does allows such operation, I would rather see it taken a full snapshot state rahter than block the operation.
Closing old bugs. If this issue is still relevant/important in current version, please re-open the bug.