libvirt users - Jun 2014 - Connecting to session instance without socket path is not supported by the ssh connection driver

Hi all,

I have setup some Virtualbox VMs under my normal user session. When I 
try to list the vbox machines locally I get:

$ virsh -c vbox:///session list
  Id    Name                           State
----------------------------------------------------
  3     Ubuntu-MASS-controller         running

When I try to list the machines from a remote location I get:

$ virsh -c vbox+ssh://theodotos@10.0.2.2/session list
setlocale: No such file or directory
error: failed to connect to the hypervisor
error: Operation not supported: Connecting to session instance without socket
path is not supported by the ssh connection driver

I have setup public key authentication between the remote machine and 
the VBox host.

Any idea what am I doing wrong?

On 06/25/2014 12:13 PM, Theodotos Andreou wrote:
> Hi all,
>
> I have setup some Virtualbox VMs under my normal user session. When I
> try to list the vbox machines locally I get:
>
> $ virsh -c vbox:///session list
>  Id    Name                           State
> ----------------------------------------------------
>  3     Ubuntu-MASS-controller         running
>
> When I try to list the machines from a remote location I get:
>
> $ virsh -c vbox+ssh://theodotos@10.0.2.2/session list
> setlocale: No such file or directory
> error: failed to connect to the hypervisor
> error: Operation not supported: Connecting to session instance without
> socket path is not supported by the ssh connection driver
That pretty much explains it ^^^. Remote connections to session
(non-privileged) instances of libvirtd are not supported.
>
> I have setup public key authentication between the remote machine and
> the VBox host.
>
> Any idea what am I doing wrong?
You'll either need to use system libvirtd, or do management locally
(that is, the libvirt client->server connection must be local; what goes
on on top of that is up to you).

On 25/06/2014 02:53 μμ, Laine Stump wrote:
> On 06/25/2014 12:13 PM, Theodotos Andreou wrote:
>> Hi all,
>>
>> I have setup some Virtualbox VMs under my normal user session. When I
>> try to list the vbox machines locally I get:
>>
>> $ virsh -c vbox:///session list
>>   Id    Name                           State
>> ----------------------------------------------------
>>   3     Ubuntu-MASS-controller         running
>>
>> When I try to list the machines from a remote location I get:
>>
>> $ virsh -c vbox+ssh://theodotos@10.0.2.2/session list
>> setlocale: No such file or directory
>> error: failed to connect to the hypervisor
>> error: Operation not supported: Connecting to session instance without
>> socket path is not supported by the ssh connection driver
> That pretty much explains it ^^^. Remote connections to session
> (non-privileged) instances of libvirtd are not supported.
>
>> I have setup public key authentication between the remote machine and
>> the VBox host.
>>
>> Any idea what am I doing wrong?
> You'll either need to use system libvirtd, or do management locally
> (that is, the libvirt client->server connection must be local; what goes
> on on top of that is up to you).
>
Thanks for the Laine. I will reconfigure the VMs to be managed by the 
system instead of user session.