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.
Created attachment 632013[details]
VDS-logs
Description of problem:
libvirt in deadlock while trying to destroy qemu process while it can't communicate with its monitor socket
Version-Release number of selected component (if applicable):
3.1/si21
====
libvirt-lock-sanlock-0.9.10-21.el6_3.5.x86_64
libvirt-debuginfo-0.9.10-21.el6_3.5.x86_64
libvirt-python-0.9.10-21.el6_3.5.x86_64
libvirt-0.9.10-21.el6_3.5.x86_64
libvirt-client-0.9.10-21.el6_3.5.x86_64
====
vdsm-python-4.9.6-38.0.el6_3.x86_64
vdsm-4.9.6-38.0.el6_3.x86_64
vdsm-cli-4.9.6-38.0.el6_3.noarch
----
How reproducible:
always
Steps to Reproduce:
1.Installed rhevm+dwh+reports
2.Created setup - DC, Host, Storage(iscsi), vms
3.Changed engine & vds date to 31/12/12
Actual results:
All VMs show "Not Responding"
Host CPU jumps to 99%
libvirt in deadlock while trying to destroy qemu process while it can't communicate with its monitor socket
Expected results:
Should recover
Additional info:
logs
Created attachment 632013 [details] VDS-logs Description of problem: libvirt in deadlock while trying to destroy qemu process while it can't communicate with its monitor socket Version-Release number of selected component (if applicable): 3.1/si21 ==== libvirt-lock-sanlock-0.9.10-21.el6_3.5.x86_64 libvirt-debuginfo-0.9.10-21.el6_3.5.x86_64 libvirt-python-0.9.10-21.el6_3.5.x86_64 libvirt-0.9.10-21.el6_3.5.x86_64 libvirt-client-0.9.10-21.el6_3.5.x86_64 ==== vdsm-python-4.9.6-38.0.el6_3.x86_64 vdsm-4.9.6-38.0.el6_3.x86_64 vdsm-cli-4.9.6-38.0.el6_3.noarch ---- How reproducible: always Steps to Reproduce: 1.Installed rhevm+dwh+reports 2.Created setup - DC, Host, Storage(iscsi), vms 3.Changed engine & vds date to 31/12/12 Actual results: All VMs show "Not Responding" Host CPU jumps to 99% libvirt in deadlock while trying to destroy qemu process while it can't communicate with its monitor socket Expected results: Should recover Additional info: logs