Jim Fehlig wrote: > Ralf Müller wrote: > >> Am 29.08.2012 um 17:34 schrieb Jim Fehlig: >> >> >> >>> For some reason, libvirt is insisting on using the qemu driver. What if >>> you explicitly specify xen? E.g. 'virsh -c xen:/// version'? >>> >>> >> # virsh -c xen:/// version >> WARNING: gnome-keyring:: no socket to connect to >> error: internal error libxenlight state driver is not active >> error: failed to connect to the hypervisor >> >> >> >>> I'll try to reproduce this too. >>> >>> >> Tell me if you need information to do that. >> >> > > I'm able to reproduce and looking into it now. >
This turns out to be quite a mess with all the recent upstream changes wrt loadable driver modules. I'll be working with upstream to get this resolved. Stay tuned... > Would you have time to open a bug for tracking? > Please open a bug. Thanks for reporting! Jim -- To unsubscribe, e-mail: [email protected] To contact the owner, e-mail: [email protected]
