On Mon, Apr 17, 2017 at 09:49:01AM -0400, Charles Bancroft wrote: > Hi List, > > I have a question about some troubles I am having with virsh on Windows > x64. I am currently running a KVM server on a linux box and need to > allow Windows clients to access it. I have set up the server for access > with: > > ``` > listen_tls = 0 > listen_tcp = 1 > auth_tcp = "none" > ``` I assume you're merely doing this for sake of testing / debugging. This opens libvirtd connections with no access control, which is equivalent to running an SSH server allowing root logins with no password. ie you never want to do this in real deployments. > to allow for remote access while testing things. I have verified that I > can connect remotely from other linux machines, but my windows machine > always reports: > > ``` > error: failed to connect to the hypervisor > error: An error occurred, but the cause is unknown > ``` > > On the server side I see: > ``` > 10435: error : virNetSocketReadWire:1793 : Cannot recv data: Connection > reset by peer > ``` > > This happens no matter what build of virsh for windows I am using. I > have tried 3 different mingw-64 builds and versions and am about to just > build my own from scratch. I have verified that it is not the firewall > or the version of Windows I am using. I am also able to use virsh > within a docker or from the Windows Subsystem for Linux bash prompt. > > Any ideas as to what could be causing this connection reset? It happens > as soon as a connection attempt occurs and I am running out of idea. When running virsh, set 'LIBVIRT_DEBUG=1' environment variable, so we can see some debug logs, which might give a hint as to what is wrong. 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/ :| -- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list
