Bug 620780
Summary: | libvirtd blocks on crashed qemu guests | ||
---|---|---|---|
Product: | [Community] Virtualization Tools | Reporter: | Sebastian Hetze <s.hetze> |
Component: | libvirt | Assignee: | Libvirt Maintainers <libvirt-maint> |
Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | |
Severity: | high | Docs Contact: | |
Priority: | low | ||
Version: | unspecified | CC: | crobinso, hzguanqiang, jtomko, xen-maint |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2015-03-18 09:06:52 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Sebastian Hetze
2010-08-03 13:28:29 UTC
hit return by accident, so the empty form fired off by accident. Here we go again: Description of problem: we occasionally get libvirtd into a blocked state after the quemu guest has run into some crash condition. The quemu process is still running and uses 100% CPU while the guest is not reachable in any way. Any attempt to use libvirt is blocked in this situation. virsh list, virsh stop guest or anything alike does not give any messages nor does it return. Version-Release number of selected component (if applicable): utuntu host and guest libvirt 0.8.2 and 0.7.2 How reproducible: Unfortunately, this behaviour is not reproducable at will. However, playing arround I found that stopping a guest with SIGSTOP and calling virsh list brings at least one thread into a blocked state: kill -19 `pidof -s qemu-system-x86_64`; virsh list If we are lucky and this is related we might get our real problem fixed if we get the latter solved. |