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:
In libvirt QEMU driver locking whole domain is not desired, esp. during sleeps we came up with so called job conditions. That is, after obtaining lock for domain we try to set a job on it. During setting job, domain might get unlocked, thus its state might get changed. Therefore, after every successful job acquire we need to check if domain is still alive. Okay, there are a few exceptions (e.g. starting a domain). Otherwise, if we don't check we might end up trying to lock/access NULL monitor.

Version-Release number of selected component (if applicable):
libvirt-0.9.4-17.el6

How reproducible:
100%

Steps to Reproduce:
1. run attached reproducer and pass it a domain name
2. observe daemon crash
3.
  
Actual results:
libvirtd crashes


Expected results:
libvirtd will not crash

Additional info:

Created attachment 527909 [details]
repro.sh

Moving to POST:

http://post-office.corp.redhat.com/archives/rhvirt-patches/2011-October/msg00398.html

Bug verified.

rpm packages version:
libvirt-0.9.4-18.el6.x86_64
qemu-kvm-0.12.1.2-2.197.el6.x86_64
kernel-2.6.32-210.el6.x86_64

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2011-1513.html