Red Hat Bugzilla – Bug 609060
[vdsm] [libvirt intg]Libvirt failed to start after selinux enforcing was changed and libvirt was killed
Last modified: 2010-11-11 09:47:49 EST
Created attachment 427638 [details]
gdb backtrace and config files
Description of problem:
libvirt was crashing right after it start - happened after changing the selinux to enforce, killing libvirt and restart the service. backtrace and config files attached, host reboot seems to overcome the problem.
Version-Release number of selected component (if applicable):
happened on libvirt-0.8.1-10.el6.x86_64 which afterwords upgraded to libvirt-0.8.1-11.el6.x86_64
libvirt failed to start till reboot, wasn't reproducible since
Steps to Reproduce:
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release. Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release. This request is not yet committed for
I think this has the same root cause as this upstream bug. When libvirt fails to connect to the QEMU monitor, it can cause a double-unref of an object
Created attachment 427645 [details]
Avoid invoking the destroy callback if QEMU monitor open fails
libvirt-0_8_1-12_el6 has been built in RHEL-6-candidate with the fix.
verified on libvirt-0_8_1-27
Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.