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, because of course right now you
simply can't access a remote .../session instance unless you have
either (a) just run a "virsh" comman recently on the remote host, or
(b) otherwise set up a persistent user libvirt instance.
Having a remote helper like this would mean that it could start up the
user libvirt instance just like "virsh" does right now.
--
Lars Kellogg-Stedman <lars@xxxxxxxxxx> | larsks @ {freenode,twitter,github}
Cloud Engineering / OpenStack | http://blog.oddbit.com/
Attachment:
signature.asc
Description: PGP signature
_______________________________________________ libvirt-users mailing list libvirt-users@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvirt-users
