RE: libvirt remote uri format

The client machine is running macOS. So that explains it. For my case, hard-coding the socket path is not a major problem, although having libvirt "auto-detect" the correct path would certainly be nice. Thanks for your help. - Joe From: Andrea Bolognani <abologna(a)redhat.com&gt; To: Joe Muro <joemuro(a)us.ibm.com&gt;, libvirt-users(a)redhat.com Date: 04/06/2020 04:47 AM Subject: [EXTERNAL] Re: libvirt remote uri format On Fri, 2020-04-03 at 19:37 -0500, Joe Muro wrote: without specifying the socket path, an error occurs. +ssh://myuser@some.kvm.host/system?socket=/var/run/libvirt/libvirt-sock the socket path may be different when connecting to different libvirt hosts. systemd Is the client machine running macOS by any chance? There is a long-standing issue where that platform will use different paths for certain resources, including the libvirtd socket, and the way it currently works is that the default socket path is chosen by the client, so any mismatch will result in something like the above. The plan is to replace our use of nc with a custom virt-nc helper that will link against libvirt on the host side and will thus be able to use the default socket path appropriate for the system; however, as far as I'm aware nobody is currently working on it. -- Andrea Bolognani / Red Hat / Virtualization