On 06/05/10 01:19 PM, Guido Günther wrote:
On Wed, May 05, 2010 at 08:14:13PM -0400, Gary Dale wrote:
Package: virt-manager
Version: 0.8.4-2
Severity: grave
Tags: squeeze
Justification: renders package unusable
I recently reinstalled Debian/Squeeze from scratch (kept my /home
partition though). After reinstalling virt-manager, I found that I
was no longer able to connect to my virtual machine (a Windows XP
raw virtual disk). When I try to connect to qemu, I get the above
error which I was not getting before the new Squeeze install. I
can't find any fix for it via Google (just lots of people
experiencing the problem) and I'm a bit of newbie at virtualization.
Qemu-kvm is able to directly launch my virtual machine and it runs
fine, but after using virt-manager to manage the sessions, I find it
preferrable (better mouse handling, doesn't kill the KDE
screensaver, etc.).
Please see:
http://wiki.debian.org/libvirt#Bugreports.2BAC8-Debugging
for some information on howto debug this.
Cheers,
-- Guido
See attached. As noted, libvirtd is running (as root, process #2445 -
/usr/sbin/libvirtd -d) so I have no idea what the problem is.
[Wed, 05 May 2010 19:47:03 virt-manager 5123] INFO (virt-manager:161)
Application startup
[Wed, 05 May 2010 19:47:04 virt-manager 5123] WARNING (keyring:31) No support
for gnome-keyring
[Wed, 05 May 2010 19:47:04 virt-manager 5124] DEBUG (engine:338) About to
connect to uris ['qemu:///system']
[Wed, 05 May 2010 19:47:04 virt-manager 5124] DEBUG (engine:628) window counter
incremented to 1
[Wed, 05 May 2010 19:47:07 virt-manager 5124] DEBUG (connection:836) Scheduling
background open thread for qemu:///system
[Wed, 05 May 2010 19:47:07 virt-manager 5124] DEBUG (connection:981) Background
thread is running
[Wed, 05 May 2010 19:47:07 virt-manager 5124] DEBUG (connection:1019)
Background open thread complete, scheduling notify
[Wed, 05 May 2010 19:47:07 virt-manager 5124] DEBUG (connection:1024) Notifying
open result
[Wed, 05 May 2010 19:47:07 virt-manager 5124] DEBUG (error:86) Uncaught Error:
Unable to open a connection to the libvirt management daemon.
Libvirt URI is: qemu:///system
Verify that:
- The 'libvirtd' daemon has been started
: Unable to open connection to hypervisor URI 'qemu:///system':
unable to connect to '/var/run/libvirt/libvirt-sock', libvirtd may need to be
started: Permission denied
Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/connection.py", line 971, in
_try_open
None], flags)
File "/usr/lib/python2.5/site-packages/libvirt.py", line 111, 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: Permission denied
[Wed, 05 May 2010 19:47:29 virt-manager 5124] DEBUG (engine:632) window counter
decremented to 0