Hide Forgot
Description of problem: connect the hypersior without configure tls/tcp environment, just do # virsh -c qemu+tls:///system will report Segmentation fault (core dumped) but libvirtd still alive. So I think it just reports wrong message. Version-Release number of selected component (if applicable): libvirt-0.9.3-6.el6.x86_64 How reproducible: 100% Steps to Reproduce: 1. virsh -c qemu+tls:///system 2. 3. Actual results: reports Segmentation fault (core dumped) Expected results: reports reasonable message like error: Cannot access CA certificate '/etc/pki/CA/cacert.pem': No such file or directory error: failed to connect to the hypervisor Additional info:
on version libvirt-0.9.3-5.el6.x86_64 it is right.
The patch is intended to solve the problem. https://www.redhat.com/archives/libvir-list/2011-July/msg01325.html
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
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 connect to localhost without tls configuration: # virsh -c qemu+tls:///system error: Cannot read CA certificate '/etc/pki/CA/cacert.pem': No such file or directory error: failed to connect to the hypervisor
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