Bug 735011
Summary: | virsh hang up with autodestroy domains after doing save operation fail | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Nan Zhang <nzhang> |
Component: | libvirt | Assignee: | Osier Yang <jyang> |
Status: | CLOSED ERRATA | QA Contact: | Virtualization Bugs <virt-bugs> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 6.2 | CC: | dallan, dyuan, eblake, jyang, mzhan, rwu, syeghiay, veillard, yupzhang |
Target Milestone: | rc | Keywords: | Regression |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | libvirt-0.9.4-8.el6 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2011-12-06 11:27:54 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: | 733806 | ||
Bug Blocks: |
Description
Nan Zhang
2011-09-01 07:29:57 UTC
Set Keywords with Regression, since it's not reproduced in libvirt-0.9.4-6.el6.x86_64. Very simple fix, the bug was introduced in the patch for #733806 it's a trivial one line fix, Daniel http://post-office.corp.redhat.com/archives/rhvirt-patches/2011-September/msg00013.html Move to POST. Verify this issue with : libvirt-0.9.4-9.el6.x86_64 qemu-kvm-0.12.1.2-2.185.el6.x86_64 # virsh Welcome to virsh, the virtualization interactive terminal. Type: 'help' for help with commands 'quit' to quit virsh # start rhel6 --autodestroy Domain rhel6 started virsh # save rhel6 rhel6.save error: Failed to save domain rhel6 to rhel6.save error: Requested operation is not valid: domain is marked for auto destroy virsh # list Id Name State ---------------------------------- 3 rhel6 running virsh # exit # /etc/init.d/libvirtd status libvirtd (pid 11948) is running... So change the status to VERIFIED. 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-2011-1513.html |