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.
Description of problem:
when libvirtd is not running, virsh list produces segmentation fault:
#0 0x00007ffff75e7eb7 in pthread_mutex_lock () from /lib64/libpthread.so.0
#1 0x00007ffff7af30d5 in virNetClientClose () from /usr/lib64/libvirt.so.0
#2 0x00007ffff7ae5cbf in doRemoteOpen () from /usr/lib64/libvirt.so.0
#3 0x00007ffff7ae7d61 in remoteOpen () from /usr/lib64/libvirt.so.0
#4 0x00007ffff7aa6c81 in do_open () from /usr/lib64/libvirt.so.0
#5 0x00007ffff7aa8f96 in virConnectOpenAuth () from /usr/lib64/libvirt.so.0
#6 0x0000000000425400 in main ()
repro:
- connect to 'qemu:///system'
- no libvirtd running
moving to POST:
commit b14800af14f8c13f2ca80f0a912fbb94d68628e8
Author: Guannan Ren <gren>
Date: Wed Jul 20 15:20:18 2011 +0100
Don't try to close a NULL virNetClientPtr
* src/rpc/virnetclient.c: Skip close attempt if virNetClientPtr
is NULL
v0.9.3-203-gb14800a
I have verified it on RHEL6u2 server with the following component and it passed:
libvirt-0.9.3-8.el6
qemu-kvm-0.12.1.2-2.172.el6
kernel-2.6.32-171.el6
The steps are as follows:
1 stop libvirtd daemon
# service libvirtd stop
Stopping libvirtd daemon: [ OK ]
2 list the guest
# virsh list
error: Failed to reconnect to the hypervisor
error: no valid connection
error: Failed to connect socket to '/var/run/libvirt/libvirt-sock': Connection refused
3 start libvirtd daemon
# service libvirtd start
Starting libvirtd daemon: [ OK ]
4 list the guest
# virsh list --all
Id Name State
----------------------------------
- rhel6 shut off
- RHEL6-1 shut off
- vr-win7-i386-kvm shut off
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