[Pkg-libvirt-maintainers] Bug#706059: Bug#706059: libvirt-bin: libvirt seems unable to connect to xen using unix sockets

[Guido Günther]

On Wed, Apr 24, 2013 at 01:23:12PM +0800, Michael Deegan wrote:
> Package: libvirt-bin
> Version: 0.9.12-11
> Severity: normal
> 
> Hello,
> 
> libvirt seems to default to attempting to connect to xen using the insecure port 8000
> HTTP interface, despite documentation everywhere saying that the HTTP interface
> is bad for security:
> 
>     root at mordac:/home/michael# virsh connect
>     error: Failed to connect to the hypervisor
>     error: unable to connect to 'localhost:8000': Connection refused
> 
> So I've configured xend to use the unix socket interface instead:
> 
>     root at mordac:/home/michael# grep ^[^#].*xend-unix /etc/xen/xend-config.sxp
>     (xend-unix-server yes)
>     (xend-unix-path /var/run/xend/xend.sock)
> 
> However, I am having difficulty convincing libvirt to use this interface. My
> reading of http://libvirt.org/uri.html suggests that these *ought* to work:
> 
>     root at mordac:/home/michael# virsh -c ///var/run/xend/xend.sock
>     error: no connection driver available for No connection for URI /var/run/xend/xend.sock
>     error: failed to connect to the hypervisor
> 
>     root at mordac:/home/michael# virsh -c xen:///var/run/xend/xend.sock
>     error: internal error unexpected Xen URI path '/var/run/xend/xend.sock', try xen:///
>     error: failed to connect to the hypervisor
> 
>     root at mordac:/home/michael# virsh -c xen+unix:///var/run/xend/xend.sock
>     error: internal error unexpected Xen URI path '/var/run/xend/xend.sock', try xen:///
>     error: failed to connect to the hypervisor
> 
>     root at mordac:/home/michael# virsh -c xen+unix:///
>     error: unable to connect to 'localhost:8000': Connection refused
>     error: failed to connect to the hypervisor
> 
>     root at mordac:/home/michael# virsh -c xen:///
>     error: unable to connect to 'localhost:8000': Connection refused
>     error: failed to connect to the hypervisor
> 
> I'm open to the possibility that it is simply a case of error messages being
> incorrect or misleading.

Please check /u/s/doc/libvirt-bin/README.Debian and
http://wiki.debian.org/libvirt/Debugging on howto hopefully track this
down.

That said I'm not sure in what shape Wheezy's libvirt+xen support is
since I'm not testing (yet) auto testing this combination at all (there
are other xen related open bugs waiting for test and feedback). 

Please have a look at the version in experimental since this one is much
more up to date.

Cheers,
 -- Guido