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.
Description of problem:
Let qemu get hang with kvm hypervisor,run
virsh list --all
cdrom_test running
the guest status is in running state,while the guest can't be operated in virt-viewer
Version-Release number of selected component (if applicable):
qemu-kvm-0.12.1.2-2.128.el6.x86_64
libvirt-0.8.6-1.el6.x86_64
How reproducible:
always
Steps to Reproduce:
1.Start a guest such as cdrom_test
2.stop qemu process with following:
kill -STOP `ps aux | grep qemu | grep -v grep | awk '{print $2}'`
3.run the following command:
virsh list
Id Name State
----------------------------------
9 cdrom_test running
Actual results:
The guest status is in running status,while in fact it has been hanged and can't be operated
Expected results:
Additional info:
The state report is the logical guest lifecycle state, which is unrelated to the QEMU process state. So the fact that you sent SIGSTOP to qemu is not intended to be reported this way.
Comment 2RHEL Program Management
2011-04-04 01:49:32 UTC
Since RHEL 6.1 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.
Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.
Description of problem: Let qemu get hang with kvm hypervisor,run virsh list --all cdrom_test running the guest status is in running state,while the guest can't be operated in virt-viewer Version-Release number of selected component (if applicable): qemu-kvm-0.12.1.2-2.128.el6.x86_64 libvirt-0.8.6-1.el6.x86_64 How reproducible: always Steps to Reproduce: 1.Start a guest such as cdrom_test 2.stop qemu process with following: kill -STOP `ps aux | grep qemu | grep -v grep | awk '{print $2}'` 3.run the following command: virsh list Id Name State ---------------------------------- 9 cdrom_test running Actual results: The guest status is in running status,while in fact it has been hanged and can't be operated Expected results: Additional info: