Bug 723843 - [libvirt] virsh list produced segmentation fault when libvirtd is not running
Summary: [libvirt] virsh list produced segmentation fault when libvirtd is not running
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: libvirt
Version: 6.2
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: rc
: 6.2
Assignee: Michal Privoznik
QA Contact: Virtualization Bugs
URL:
Whiteboard:
: 723912 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-07-21 11:10 UTC by Haim
Modified: 2014-01-13 00:49 UTC (History)
9 users (show)

Fixed In Version: libvirt-0.9.3-8.el6
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-12-06 11:17:26 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2011:1513 0 normal SHIPPED_LIVE libvirt bug fix and enhancement update 2011-12-06 01:23:30 UTC

Description Haim 2011-07-21 11:10:25 UTC
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

Comment 1 Michal Privoznik 2011-07-21 11:14:04 UTC
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

Comment 3 Daniel Berrangé 2011-07-21 14:30:38 UTC
*** Bug 723912 has been marked as a duplicate of this bug. ***

Comment 4 xhu 2011-07-26 08:31:17 UTC
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

Comment 5 errata-xmlrpc 2011-12-06 11:17:26 UTC
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


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