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

Bug 1513996

Summary:	VM is restarted rather than resumed on dehibernation
Product:	[oVirt] ovirt-engine	Reporter:	Milan Zamazal <mzamazal>
Component:	Backend.Core	Assignee:	Arik <ahadas>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Israel Pinto <ipinto>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	4.2.0	CC:	bugs, michal.skrivanek, mzamazal
Target Milestone:	ovirt-4.2.0	Flags:	rule-engine: ovirt-4.2+ rule-engine: blocker+ ahadas: devel_ack+
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:	2017-12-20 10:59:54 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Virt	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Milan Zamazal 2017-11-16 13:01:42 UTC

Description of problem:

When a VM is suspended and then re-run, it's newly started rather than resumed to its last state.

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

oVirt master

How reproducible:

Always.

Steps to Reproduce:
1. Start a VM.
2. Perform some change inside the running VM to distinguish it from a freshly started VM.
3. Use "Suspend" web UI button to suspend it.
4. Once the VM is suspended, run it again with "Run" button again.
5. Look inside the VM and check whether the VM has been resumed to the previous state or newly started.

Actual results:

The VM is newly started.

Expected results:

The VM is resumed from its suspended state.

Additional info:

The problem is that hiberVolHandle parameter is not sent from Engine on VM.create call.

Comment 1 Yaniv Kaul 2017-11-17 06:38:24 UTC

I assume we need to test the flow better in o-s-t?

Comment 2 Milan Zamazal 2017-11-20 08:08:09 UTC

(In reply to Yaniv Kaul from comment #1)
> I assume we need to test the flow better in o-s-t?

Yes, we should check not only for UP status there but also that the inner state of the VM is retained.

Comment 3 Israel Pinto 2017-12-13 13:43:45 UTC

Verify with:
Engine: Software Version:4.2.0.2-0.1.el7
Host:
OS Version:RHEL - 7.4 - 18.el7
Kernel Version:3.10.0 - 693.el7.x86_64
KVM Version:2.9.0 - 16.el7_4.12
LIBVIRT Version:libvirt-3.2.0-14.el7_4.5
VDSM Version:vdsm-4.20.9.1-1.el7ev

Steps:
1. Create vm with OS
2, Start VM and create file with content on VM
3. Suspend VM
4. Resume VM
5. Check File exists on VM

Pass

Comment 4 Sandro Bonazzola 2017-12-20 10:59:54 UTC

This bugzilla is included in oVirt 4.2.0 release, published on Dec 20th 2017.

Since the problem described in this bug report should be
resolved in oVirt 4.2.0 release, published on Dec 20th 2017, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.