Hide Forgot
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
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