Description of problem: Version-Release number of selected component (if applicable): Libvirt build 1.2.14 and up. Versions 1.2.13 and lower do not produce this error How reproducible: Build libvirt from source 1.2.14 or higher using mingw64. Build on Fedora 22 with updated libraries Steps to Reproduce: 1) sudo dnf install -y autoconf automake gcc gcc-c++ mingw64-gcc mingw64-gcc-c++ mingw64-zlib mingw64-libxml2 mingw64-portablexdr mingw32-gcc mingw32-gcc-c++ mingw32-zlib mingw32-libxml2 mingw32-portablexdr 2) Download libvirt-1.2.14.tar.gz from ftp://libvirt.org/libvirt/ 3) mingw64-configure 4) sudo make 5) sudo make install 6) copy /usr/x86_64_w_64-mingw32/sys-root/mingw/bin contents to a windows machine and try to connect using virsh.exe using connect qemu+tcp://192.168.0.21/system Actual results: virsh # connect qemu+tcp://192.168.0.21/system error: Failed to connect to the hypervisor error: internal error: received hangup / error event on socket Expected results: virsh # connect qemu+tcp://192.168.0.21/system virsh # Additional info: I download and build libvirt version 1.2.13 using the same process as above and I am able to connect without issue. Building any version higher than 1.2.13 causes the socket hangup to occur. I have setup a ubuntu 14.04 as the host with no authentication turned on for tcp which I am able to use in 1.2.13 without issue.
Can you find the change between v1.2.13 and v1.2.14 that causes this to break? Check out 'git bisect'
Unfortunately, I don't know the libvirt codebase at all, so tracking the bug down would be pretty much impossible for me. I understand if you guys are too busy to fix the bug, I just thought that I would report it.
The socket hangup still persists in the latest 1.2.17 build
Sorry no one got to this, none of the core libvirt devs use windows. Do you know if this is still relevant with the latest version? If so, maybe try mailing libvir-list, someone might chime in
Since there's no response, closing as DEFERRED. But if anyone is still affected with newer libvirt versions, please re-open and we can triage from there
Hi, I have downloaded pre-compiled Windows MSI packages and I have the same erorr message - error: received hangup / error event on socket. Is it possible to log or trace what exactly is going on there? I am using version 1.2.16