Bug 915354

Summary:	vdsm: cannot run a vm with several snapshots
Product:	Red Hat Enterprise Linux 6	Reporter:	Chris Pelland <cpelland>
Component:	libvirt	Assignee:	Eric Blake <eblake>
Status:	CLOSED ERRATA	QA Contact:	Virtualization Bugs <virt-bugs>
Severity:	urgent	Docs Contact:
Priority:	high
Version:	6.4	CC:	abaron, acathrow, bazulay, cpelland, dallan, dron, dyasny, dyuan, eblake, gwatson, hateya, iheim, jentrena, juzhang, lpeer, michele, mzhan, pep, pkrempa, pm-eus, pspacek, pzhukov, rwu, sgrinber, whuang, ydu, ykaul, zhpeng
Target Milestone:	rc	Keywords:	Regression, ZStream
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	libvirt-0.10.2-18.el6_4.1	Doc Type:	Bug Fix
Doc Text:	Cause: libvirt followed relative backing chains differently than qemu Consequence: missing sVirt permissions when libvirt couldn't follow the chain Fix: relative backing files are now treated identically in libvirt and qemu Result: vdsm use of relative backing files works again	Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-03-21 14:05:55 UTC	Type:	---
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:	903248
Bug Blocks:	879167

Description Chris Pelland 2013-02-25 15:09:31 UTC

This bug has been copied from bug #903248 and has been proposed
to be backported to 6.4 z-stream (EUS).

Comment 6 Eric Blake 2013-02-25 23:22:19 UTC

In POST:
http://post-office.corp.redhat.com/archives/rhvirt-patches/2013-February/msg00228.html

Comment 9 Gordon Watson 2013-03-13 22:27:54 UTC

FYI. We have recently observed the same symptoms when a customer created a VM from a template, took a snapshot of this, and then the VM would not start thereafter. They also had some other similar scenarios that they tested that also failed, details of which can be provided, if necessary.

What they found was that this worked fine on their RHEL6.3 hosts. They then upgraded to 6.4, or at least to some 6.4 components, e.g. vdsm, libvirt, and then experienced the problem.

We have also reproduced this in our lab. The sequence doesn't specifically match the one outlined in the original bug, 903248, but the symptoms (in failure of execution, vdsm log and libvirtd log entries) are identical.

GFW.

Comment 13 Huang Wenlong 2013-03-18 03:08:39 UTC

Verify this bug with: 
libvirt-0.10.2-18.el6_4.1.x86_64
qemu-kvm-rhev-0.12.1.2-2.355.el6_4.2.x86_64
vdsm-4.10.2-1.8.el6ev.x86_64

Steps:

1) need  RHEVM env and ISCSI storage  

2) start a vm  

3) create 3 live snapshot via rhevm 

4) kill -9 vm's pid 

5) try to start vm ,vm can start up without error

Comment 14 Huang Wenlong 2013-03-19 05:22:50 UTC

Retest it with :
libvirt-0.10.2-18.el6_4.2.x86_64 

steps as comment13  :
 PASS

Comment 16 errata-xmlrpc 2013-03-21 14:05:55 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/RHBA-2013-0664.html