On 05/02/2016 11:57 AM, Lars Kellogg-Stedman wrote:
> This is frustrating:
>
> $ export LIBVIRT_DEFAULT_URI=qemu+ssh://remotehost/session
> $ virsh list
> error: failed to connect to the hypervisor
> error: no valid connection
> error: Operation not supported: Connecting to session insta
On Mon, May 02, 2016 at 11:57:24AM -0400, Lars Kellogg-Stedman wrote:
> And in either of the above cases, "libvirt-socket-helper" would parse
> the environment and the libvirtd configuration as necessary and
> ultimately act like "nc -U /path/to/some/socket".
In fact, this would be *extra* useful,
This is frustrating:
$ export LIBVIRT_DEFAULT_URI=qemu+ssh://remotehost/session
$ virsh list
error: failed to connect to the hypervisor
error: no valid connection
error: Operation not supported: Connecting to session instance without socket
path is not supported by the ssh connection dr
