Hide Forgot
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.
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.
Moving to POST: commit bda2f17d7e673f4dd7fc1a03389ca7d8f4e1646e Author: Martin Kletzander <mkletzan> Date: Wed Jun 6 16:43:41 2012 +0200 qemu: better detection of crashed domains
Steps same as comment0 pkgs: libvirt-1.0.0-1.el7 It's verified.
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.