Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
It seems we should rather report it as "crashed" instead of "failed" when we
cannot connect to qemu monitor but with qemu version for which we don't use
-no-shutdown, we fail to connect to monitor also after the guest correctly shut
down when libvirtd was stopped.
Comment 2Martin Kletzander
2012-06-07 06:51:08 UTC
Moving to POST:
commit bda2f17d7e673f4dd7fc1a03389ca7d8f4e1646e
Author: Martin Kletzander <mkletzan>
Date: Wed Jun 6 16:43:41 2012 +0200
qemu: better detection of crashed domains
This request was resolved in Red Hat Enterprise Linux 7.0.
Contact your manager or support representative in case you have further questions about the request.
Description of problem: Stop libvirtd,then kill the guest,after that,start libvirtd and run virsh domstate --reason,it cannot detect crashed domains correctly Version-Release number of selected component (if applicable): libvirt-0.9.4-19.el6.x86_64 qemu-kvm-0.12.1.2-2.200.el6.x86_64 kernel-2.6.32-211.el6.x86_64 How reproducible: always Steps to Reproduce: 1.#virsh start rhel6-test 2.#service libvirtd stop Stopping libvirtd daemon: [ OK ] 3.# nc -U /var/lib/libvirt/qemu/rhel6-test.monitor {"QMP": {"version": {"qemu": {"micro": 1, "minor": 12, "major": 0}, "package": "(qemu-kvm-0.12.1.2)"}, "capabilities": []}} {"execute":"qmp_capabilities"} {"return": {}} {"execute":"q"} {"return": {}} {"timestamp": {"seconds": 1319591214, "microseconds": 534506}, "event": "SHUTDOWN"} Or kill the guest with #kill -9 $VM_PID 4.# service libvirtd start Starting libvirtd daemon: [ OK ] 5.# virsh domstate rhel6-test --reason shut off (failed) Actual results: shut off (failed) Expected results: shut off (crashed) Additional info: More info,please refer to bug 617890.