[libvirt] Trouble with virsh on Windows

[Daniel P. Berrange]

On Tue, Apr 18, 2017 at 01:55:17PM +0100, Daniel P. Berrange wrote:
> On Tue, Apr 18, 2017 at 01:41:27PM +0100, Daniel P. Berrange wrote:
> > On Tue, Apr 18, 2017 at 08:02:35AM -0400, Charles Bancroft wrote:
> > > 2017-04-18 11:46:23.879+0000: 1: debug : virNetClientMarkClose:776 :
> > > client=0000000000faa9a0, reason=1
> > 
> > We're marking the conneciton as closed, due to EOF.
> > 
> > This is the first sign of something wrong.
> > 
> > I'm not 100% sure if this is due to the server closing the
> > connection, or a client side bug in the poll loop.
> > 
> > I'd be interested to see the libvirtd server side logs - if you configure
> > libvirtd.conf with
> > 
> > 
> >   log_outputs="1:file:/var/log/libvirt/libvirtd.log"
> >   log_filters="1:remote 1:rpc 1:event 1:daemon"
> 
> Actually don't bother - I just managed to reproduce the same problem myself
> in a Windows machine. So this looks like a bug in libvirt on Win32.

FYI, I've tracked this down to a likely bug in gnulib. All versions of
libvirt from 1.2.14 onwards are affected & so will fail to connect.

If you don't need the newer APIs, you could try using libvirt 1.2.13 for
your Windows builds - I've tested that at least successfully connects.

Meanwhile we'll aim to get this fixed in the next release (v3.3.0)

Regards,
Daniel
-- 
|: http://berrange.com      -o-    http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org              -o-             http://virt-manager.org :|
|: http://entangle-photo.org       -o-    http://search.cpan.org/~danberr/ :|