Bug 701923

Summary: RFE: start libvirtd if connection to localhost/QEMU fails and it is not running
Product: Red Hat Enterprise Linux 6 Reporter: David Jaša <djasa>
Component: virt-managerAssignee: Cole Robinson <crobinso>
Status: CLOSED NOTABUG QA Contact: Virtualization Bugs <virt-bugs>
Severity: low Docs Contact:
Priority: medium    
Version: 6.2CC: bsarathy, dyuan, mzhan
Target Milestone: rcKeywords: FutureFeature
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-06-10 22:24:16 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description David Jaša 2011-05-04 10:10:58 UTC
Description of problem:
SSIA

Version-Release number of selected component (if applicable):
virt-manager-0.8.6-4.el6.noarch

How reproducible:
always

Steps to Reproduce:
1. stop libvirtd if it is running
2. start virt-manager
3. double click "localhost (QEMU) - Not Connected" line
  
Actual results:
virt-manager throws error popup saying that connection could not be established and asking user to check if it is running

Expected results:
virt-manager starts libvirtd and connects to it

Additional info: 
Traceback in error popup:

unable to connect to '/var/run/libvirt/libvirt-sock', libvirtd may need to be started: No such file or directory

Traceback (most recent call last):
  File "/usr/share/virt-manager/virtManager/connection.py", line 1022, in _try_open
    None], flags)
  File "/usr/lib64/python2.6/site-packages/libvirt.py", line 102, in openAuth
    if ret is None:raise libvirtError('virConnectOpenAuth() failed')
libvirtError: unable to connect to '/var/run/libvirt/libvirt-sock', libvirtd may need to be started: No such file or directory

Comment 2 Cole Robinson 2011-06-10 22:24:16 UTC
Problem is that most of the time virt-manager is not running with sufficient privileges to start libvirtd, since it is usually run as a regular user and not root. We could attempt, but I think it would cause more confusion than it's worth. Closing as NOTABUG