RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 915354 - vdsm: cannot run a vm with several snapshots
Summary: vdsm: cannot run a vm with several snapshots
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: libvirt
Version: 6.4
Hardware: x86_64
OS: Linux
high
urgent
Target Milestone: rc
: ---
Assignee: Eric Blake
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On: 903248
Blocks: 879167
TreeView+ depends on / blocked
 
Reported: 2013-02-25 15:09 UTC by Chris Pelland
Modified: 2018-12-01 16:47 UTC (History)
28 users (show)

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
Clone Of:
Environment:
Last Closed: 2013-03-21 14:05:55 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 331503 0 None None None Never
Red Hat Product Errata RHBA-2013:0664 0 normal SHIPPED_LIVE libvirt bug fix and enhancement update 2013-03-21 17:37:54 UTC

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
Note You need to log in before you can comment on or make changes to this bug.