Bug 620780 - libvirtd blocks on crashed qemu guests
libvirtd blocks on crashed qemu guests
Status: CLOSED INSUFFICIENT_DATA
Product: Virtualization Tools
Classification: Community
Component: libvirt (Show other bugs)
unspecified
All Linux
low Severity high
: ---
: ---
Assigned To: Libvirt Maintainers
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2010-08-03 09:28 EDT by Sebastian Hetze
Modified: 2015-03-18 05:06 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2015-03-18 05:06:52 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Sebastian Hetze 2010-08-03 09:28:29 EDT
Description of problem:


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
Comment 1 Sebastian Hetze 2010-08-03 09:37:55 EDT
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.

Note You need to log in before you can comment on or make changes to this bug.