Bug 506687 - libvir: error : could not connect to qemu:///system
Summary: libvir: error : could not connect to qemu:///system
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: libvirt
Version: 5.4
Hardware: All
OS: Linux
medium
medium
Target Milestone: beta
: ---
Assignee: Daniel Veillard
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-06-18 10:48 UTC by Alex Jia
Modified: 2009-12-14 21:13 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-06-19 05:22:03 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Alex Jia 2009-06-18 10:48:15 UTC
Description of problem:
Failed to open connection to the hypervisor
libvir: error : could not connect to qemu:///system

Version-Release number of selected component (if applicable):
[root@dhcp-66-70-18 tmp]# rpm -qa|grep kvm
kvm-83-76.el5
kvm-qemu-img-83-76.el5
etherboot-zroms-kvm-5.4.4-10.el5
kmod-kvm-83-76.el5
[root@dhcp-66-70-18 tmp]# rpm -qa|grep libvirt
libvirt-cim-0.5.5-2.el5
libvirt-devel-0.6.3-10.el5
libvirt-0.6.3-10.el5
libvirt-debuginfo-0.6.3-10.el5
libvirt-python-0.6.3-10.el5

How reproducible:
virsh list

Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
the issue will been resolved,if we create manually connection to hypervisor,e.g by virt-manager

Comment 1 Daniel Berrangé 2009-06-18 10:56:09 UTC
Please provides steps to reproduce the problem.

Comment 2 Alex Jia 2009-06-18 12:18:50 UTC
1.install latest version os and virtualization component,e.g rhel5.4 and kvm and libvirt.
2.login system and input commands line "virsh list"

Comment 3 Daniel Berrangé 2009-06-18 13:43:18 UTC
Works fine for me with current nightly 5.4 spin  http://qafiler.bos.redhat.com/redhat/nightly/RHEL5.4-Server-20090618.nightly/5/x86_64/os/

Please check whether 'libvirtd' is running. 

If it is running, then stop it and run it manually with debugging 

  LIBVIRT_DEBUG=1 /usr/sbin/libvirtd

And then try to connect against with virsh, also with debugging turned on

  LIBVIRT_DEBUG=1 virsh list

Comment 4 Alex Jia 2009-06-19 04:51:26 UTC
I renew install RHEL5.4-Server-20090618.nightly,and verify again,this issue don't existent,"virsh list" commands run well.

Comment 5 Alex Jia 2009-06-19 04:54:24 UTC
[root@dhcp-66-70-18 ~]# uname -a
Linux dhcp-66-70-18.nay.redhat.com 2.6.18-153.el5 #1 SMP Wed Jun 10 17:53:33 EDT 2009 x86_64 x86_64 x86_64 GNU/Linux
[root@dhcp-66-70-18 ~]# rpm -qa|grep kvm
etherboot-zroms-kvm-5.4.4-10.el5
kvm-qemu-img-83-76.el5
kmod-kvm-83-76.el5
kvm-83-76.el5
[root@dhcp-66-70-18 ~]# rpm -qa|grep libvirt
libvirt-python-0.6.3-10.el5
libvirt-0.6.3-10.el5
libvirt-0.6.3-10.el5
[root@dhcp-66-70-18 ~]# lsmod|grep kvm
kvm_intel              85992  0
kvm                   222368  2 ksm,kvm_intel
[root@dhcp-66-70-18 ~]# virsh list
 Id Name                 State
----------------------------------


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