Bug 876785 - Virtual Machine Manager Connection Failure
Summary: Virtual Machine Manager Connection Failure
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: virt-manager
Version: 18
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: Cole Robinson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-11-15 00:05 UTC by M. Edward (Ed) Borasky
Modified: 2012-11-17 04:10 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2012-11-17 04:10:23 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Output of 'yum history info' for the update that fixed the issue (33.98 KB, text/plain)
2012-11-16 09:48 UTC, M. Edward (Ed) Borasky
no flags Details

Description M. Edward (Ed) Borasky 2012-11-15 00:05:16 UTC
Description of problem:
I've got a laptop running Fedora 18 x86_64. virt-manager has recently (exact date unknown) started throwing errors trying to connect to libvirtd. It *used* to authenticate and connect, but now it appears to either be trying to connect without authenticating or failing some existence test on the daemon being alive.

As soon as it starts, I get a dialog box that says:

Unable to connect to libvirt.

Verify that the 'libvirtd' daemon is running.

with a details box that says:

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 1027, in _open_thread
    self.vmm = self._try_open()
  File "/usr/share/virt-manager/virtManager/connection.py", line 1009, 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': Permission denied



Version-Release number of selected component (if applicable):
Name        : virt-manager
Arch        : noarch
Version     : 0.9.4
Release     : 3.fc18
Size        : 1.7 M
Repo        : installed
From repo   : updates-testing
Summary     : Virtual Machine Manager
URL         : http://virt-manager.org/
License     : GPLv2+
Description : Virtual Machine Manager provides a graphical tool for
            : administering virtual machines for KVM, Xen, and QEmu. Start,
            : stop, add or remove virtual devices, connect to a graphical or
            : serial console, and see resource usage statistics for existing VMs
            : on local or remote machines. Uses libvirt as the backend
            : management API.


How reproducible:
Every time


Steps to Reproduce:
1. Start virt-manager as a non-root user.

Actual results:
See above

Expected results:
1. Authenticate
2. Connect to libvirtd and work with VMs

Additional info:

Comment 1 M. Edward (Ed) Borasky 2012-11-15 00:08:37 UTC
The daemon *is* running:

$ service libvirtd status
Redirecting to /bin/systemctl status  libvirtd.service
libvirtd.service - Virtualization daemon
	  Loaded: loaded (/usr/lib/systemd/system/libvirtd.service; enabled)
	  Active: active (running) since Wed, 2012-11-14 07:49:07 PST; 8h ago
	Main PID: 1319 (libvirtd)
	  CGroup: name=systemd:/system/libvirtd.service
		  └ 1319 /usr/sbin/libvirtd --listen

and the modules are loaded

$ lsmod | grep kvm
kvm_intel             132762  0 
kvm                   419458  1 kvm_intel

Comment 2 M. Edward (Ed) Borasky 2012-11-16 09:47:39 UTC
This is now working on one machine! I just did a 'yum update' - here's what was installed. It doesn't appear to have changed virt-manager but it did update quite a few libvirt packages. It now works the way it used to - it authenticates on startup and connects to the qemu-kvm hypervisor. I've attached the yum history.

Comment 3 M. Edward (Ed) Borasky 2012-11-16 09:48:49 UTC
Created attachment 646269 [details]
Output of 'yum history info' for the update that fixed the issue

Comment 4 M. Edward (Ed) Borasky 2012-11-17 04:10:23 UTC
I'm going to close this. I rebuilt the machine with the F18 TC9 Desktop ISO file, re-installed the Virtual Machine Manager and everything is now working.


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