On Thu, Nov 09, 2006 at 04:39:27PM -0500, Dan B. Phung wrote: > I'm using virt-manager-0.2.5 on a Debian system. I installed these > packages per the prerequisites using aptitude: > aptitude install python-gtk2 python-gtk2-dev python-gnome2 > python-gnome2-dev python-dbus python-vte python-glade2 python-urlgrabber > > I installed libvirt from the cvs sources and I aliened and installed > python-virtinst-0.96.0-1.noarch.rpm. > > 'make check' for virt-manager complained about some rhpl exceptions, so > I commented out these lines. > > src/virtManager/create.py > - from rhpl.exception import installExceptionHandler > - from rhpl.translate import _, N_, textdomain, utf8 I've no idea how this got into the python code - those imports are some Red Hat specific python helper modules, which I was explicitly trying to avoid in virt-manager. I'm about to put up a 0.2.6 release which will remove this crack rock :-) Removing them was a safe thing to do. > So I do a 'make install' and try running it and try to connect to the > local Xen host and get: > Unable to open a connection to the Xen hypervisor/daemon. > > Verify that: > - A Xen host kernel was booted > - The Xen service has been started > > I have verified that I'm booted in Xen and that xend has been started. > > here's my log: > blade06:~:) cat .virt-manager/virt-manager.log > Thu, 09 Nov 2006 16:42:16 WARNING No support for gnome-keyring > Thu, 09 Nov 2006 16:42:16 WARNING Could not connection to session bus, > disabling DBus service exceptions.RuntimeError DBus session/starter bus > address not defined > Thu, 09 Nov 2006 16:42:34 ERROR Unable to open connection to > hypervisor URI 'xen': libvirt.libvirtError virConnectOpenReadOnly() > failed no support for hypervisor Check the /etc/xen/xend-config.sxp file. Is it configured to have either of these settings set to yes: (xend-http-server yes) (xend-unix-server yes) I strongly recommend setting unix to yes & http to no nbecause http server has *zero* authentication :-( Once you've done this, also make sure that $prefix/libexec/libvirt_proxy is made setuid root - this allows virt-manager to run as an unprivileged user in read-only mode. You still need to run virt-manager as root if you want to do read-write operations. Regards, Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| -- Fedora-xen mailing list Fedora-xen@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-xen
