On Fri, Sep 28, 2012 at 08:51:40AM -0700, hiren panchasara wrote:
On Fri, Sep 28, 2012 at 8:40 AM, Daniel P. Berrange <berrange@redhat.com>wrote:
On Fri, Sep 28, 2012 at 08:37:54AM -0700, hiren panchasara wrote:
On Fri, Sep 28, 2012 at 1:11 AM, Daniel P. Berrange <berrange@redhat.com wrote:
On Thu, Sep 27, 2012 at 11:15:56PM -0700, hiren panchasara wrote:
I've installed libvirt-0.9.13 from ports on my freebsd machine.
I started libvirtd:
$ ps awwux | grep libvirtd root 11470 0.0 0.4 103100 31948 - I 10:41PM 0:00.35 libvirtd -v -d
$ sudo virsh --connect qemu:///system error: no connection driver available for No connection for URI qemu:///system error: failed to connect to the hypervisor
I am sure I am missing something obvious.
Try collecting some debugging output using
LIBVIRT_DEBUG=1 sudo virsh --connect qemu:///system
It should give a better idea why it failed.
Not getting any useful info:
$ ps awwux | grep libvirtd root 3396 0.0 0.4 103100 32248 - I 8:24AM 0:01.05 libvirtd -v -d
$ LIBVIRT_DEBUG=1 sudo virsh --connect qemu:///system error: no connection driver available for No connection for URI qemu:///system error: failed to connect to the hypervisor
Tried 1-4 debug levels with the same response.
Sounds like sudo is stripping the env variable. Try running it as root directly, without sudo.
Aah, right, o/p is huge so putting it in pastebin: http://pastebin.com/YVrK0fRb
Looks somewhat like your libvirt has been built without support for the QEMU driver Daniel -- |: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :| |: http://libvirt.org -o- http://virt-manager.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :|