On Wed, Mar 26, 2008 at 01:02:00PM +0000, Richard W.M. Jones wrote: > On Tue, Mar 25, 2008 at 01:00:27PM +0100, Felix Krohn wrote: > > I can't find the reason for the following error: > > > > # virsh > > libvir: error : could not connect to xen:/// > > error: failed to connect to the hypervisor > [...] > > Output from `strace -s 1024 -f virsh list --all` is here: > > http://krohnjob.de/files/virsh.strace > > Can't see the reason for the above mentioned error in there... > > Really strange. Is xen configured as a backend > (ie. ./configure --without-xen or something like that?) > > You can also run with debugging enabled, if you configured that: > > LIBVIRT_DEBUG=1 virsh > > which will print a lot more useful info. (We should really enable > debugging support in configure by default ...) We do enable it by default now since 0.4.1 Dan. -- |: Red Hat, Engineering, Boston -o- http://people.redhat.com/berrange/ :| |: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :| -- Libvir-list mailing list Libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list