Re: virsh connect to xen:///system fails: "error: internal error: Unexpected driver type 'Xen' opened" ?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, May 04, 2020 at 09:33:47AM -0700, PGNet Dev wrote:
> I've setup for use of modular daemons with systemd sockets, rather than monolithic libvirtd

snip

> 	virsh -c xen:///system?socket=/var/run/libvirt/libvirt-sock
> 		error: failed to connect to the hypervisor
> 		error: internal error: Unexpected driver type 'Xen' opened
> 
> What's missing/incorrect in my config, causing the "Unexpected driver" error, and preventing the connect to local hypervisor?

Looks like you found a bug in the modular deamon code. I've copied you
on a patch that should solve it.

Regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|





[Index of Archives]     [Virt Tools]     [Lib OS Info]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [KDE Users]

  Powered by Linux