Bug 800896 - virt-manager should start libvirtd if not yet started
Summary: virt-manager should start libvirtd if not yet started
Keywords:
Status: CLOSED DUPLICATE of bug 791152
Alias: None
Product: Fedora
Classification: Fedora
Component: virt-manager
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Cole Robinson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-03-07 13:34 UTC by Stef Walter
Modified: 2012-06-06 20:08 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-06-06 20:08:02 UTC
Type: ---


Attachments (Terms of Use)

Description Stef Walter 2012-03-07 13:34:02 UTC
Description of problem:

After installing virt-manager and libvirt, and then starting virt-manager for the first time I see a dialog with this message:

Unable to connect to libvirt.

Verify that the 'libvirtd' daemon is running.

Libvirt URI is: qemu:///system

Traceback (most recent call last):
  File "/usr/share/virt-manager/virtManager/connection.py", line 1185, in _open_thread
    self.vmm = self._try_open()
  File "/usr/share/virt-manager/virtManager/connection.py", line 1167, in _try_open
    flags)
  File "/usr/lib64/python2.7/site-packages/libvirt.py", line 102, in openAuth
    if ret is None:raise libvirtError('virConnectOpenAuth() failed')
libvirtError: Failed to connect socket to '/var/run/libvirt/libvirt-sock': No such file or directory

Version-Release number of selected component (if applicable):

Name        : virt-manager
Arch        : noarch
Version     : 0.9.1
Release     : 2.fc17


How reproducible:

Every time


Steps to Reproduce:
1. Install virt-manager and libvirt
2. Double click on "localhost (QEMU)"
  
Actual results:

See the technical message.

Expected results:

virt-manager should start libvirtd if it's not yet started, whether by dbus or via systemd.

Comment 1 Cole Robinson 2012-06-06 20:08:02 UTC

*** This bug has been marked as a duplicate of bug 791152 ***


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