Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

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.

Created attachment 470171 [details]
backtrace at segfault

Description of problem:
Suddently, on a particular host, libvirt refuses to initialize due to segfault during virStateInitialize(). I don't know yet what device combination prompted this, but it should never happen.

Version-Release number of selected component (if applicable):
libvirt-0.8.1-27.el6_0.2.x86_64

How reproducible:
on one host.

Steps to Reproduce:
1. log into tiggy.usersys and start libvirt

Created attachment 470172 [details]
/var/log/libvirtd.log which does not say much (iptables is off)

Dan, can you enable debugging of node_device_udev and reproduce and upload the libvirtd.log?  Thanks, Dave

The commands to enable udev debugging are:

service libvirtd stop
export LIBVIRT_DEBUG=3
export LIBVIRT_LOG_OUTPUTS="1:file:/var/log/libvirt_debug.log"
export LIBVIRT_LOG_FILTERS="1:udev"
/sbin/libvirtd

See also:

http://libvirt.org/logging.html

Per IRC conversation with Dan Kenigsberg, the problem went away after the box was rebooted.  :(

I hate to do this, but we just don't have enough information to do anything with this BZ, so I'm closing it and I expect it will be reopened if the problem reappears.

Given the backtrace, I believe this is a duplicate of 696651.

*** This bug has been marked as a duplicate of bug 696651 ***