On Fri, Sep 28, 2012 at 1:11 AM, Daniel P. Berrange <berrange@xxxxxxxxxx> wrote:
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.
Thanks,
Hiren
Try collecting some debugging output usingOn 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.
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.
Thanks,
Hiren
-- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list