Bug 869222
| Summary: | [Libvirt] - libvirt in deadlock while trying to destroy qemu process while it can't communicate with its monitor socket | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | David Botzer <dbotzer> | ||||||||||
| Component: | libvirt | Assignee: | Libvirt Maintainers <libvirt-maint> | ||||||||||
| Status: | CLOSED DUPLICATE | QA Contact: | Virtualization Bugs <virt-bugs> | ||||||||||
| Severity: | high | Docs Contact: | |||||||||||
| Priority: | high | ||||||||||||
| Version: | 6.3 | CC: | acathrow, bazulay, dyasny, hateya, iheim, pstehlik, ykaul | ||||||||||
| Target Milestone: | rc | ||||||||||||
| Target Release: | --- | ||||||||||||
| Hardware: | x86_64 | ||||||||||||
| OS: | Linux | ||||||||||||
| Whiteboard: | |||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||
| Doc Text: | Story Points: | --- | |||||||||||
| Clone Of: | Environment: | ||||||||||||
| Last Closed: | 2012-10-23 10:36:34 UTC | Type: | Bug | ||||||||||
| Regression: | --- | Mount Type: | --- | ||||||||||
| Documentation: | --- | CRM: | |||||||||||
| Verified Versions: | Category: | --- | |||||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||||
| Embargoed: | |||||||||||||
| Attachments: |
|
||||||||||||
Created attachment 632014 [details]
qemu-cmd
Created attachment 632015 [details]
libvirt-debug
Created attachment 632016 [details]
engine-logs-just-in-case
*** This bug has been marked as a duplicate of bug 859712 *** |
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