Using virt-viewer for remote systems

Konstantin Ryabitsev

unread,

Sep 12, 2016, 8:06:19 AM9/12/16

to qubes-users

Greetings:

I need to be able to use virt-viewer to access remote systems (e.g. virt-viewer --connect qemu+ssh://some.host/system vm-name), and it would appear that it's impossible to install due to conflicts:

# dnf install virt-viewer
Error: package virt-viewer-2.0-2.fc23.x86_64 requires libvirt.so.0()(64bit), but none of the providers can be installed
(try to add '--allowerasing' to command line to replace conflicting packages)

If I do add --allowerasing it will want to remove qubes-gui-vm and xen-qubes-vm, which seems like it would do bad things.

Any suggestions how I could get virt-viewer installed without clobbering other stuff?

-K

Marek Marczykowski-Górecki

unread,

Sep 12, 2016, 8:44:54 PM9/12/16

to Konstantin Ryabitsev, qubes-users

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

It looks to be because of xen-libs package: Fedora 23 have 4.5, but
Qubes 3.1/3.2 use 4.6. And all the Qubes related packages are linked
with 4.6, while Fedora ones with 4.5.

Try upgrading to Fedora 24, which uses Xen 4.6.

- --
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBCAAGBQJX10v9AAoJENuP0xzK19csvbcH/i+S1amhP4LhrPUZWWKplAFl
mMrdX9+7e9qBrYNI6uII7whIrVcn9yKZ6OFVewKAhGabYzYm6KJgYp8D1HzTRPpI
bQ5hmeorzjtcNnKz9x9tTC/uidIwjQw7zil8yhHhqMIggOqzciliXGT8afvHPWet
iiQGB1MAKlMkD5R7sir2tUXecbpkntl23Kk+jraUlBaK3Bjh4fwwCy5Y2Rci4hT+
oYIB6/2cTHhKrPPPyZNXtj4Ga+8XH8edE13Ymj46Zit7OumW2gatuuMhEu+BzAKl
zji3ByaEKyA4NGPwZ5LXPCVpVKDFWKESmt+c3yKp+EnNDhb/yqItFG+eYUzNN3Q=
=Ruln
-----END PGP SIGNATURE-----

Konstantin Ryabitsev

unread,

Sep 13, 2016, 8:46:01 AM9/13/16

to Marek Marczykowski-Górecki, qubes-users

On Tue, Sep 13, 2016 at 02:44:45AM +0200, Marek Marczykowski-Górecki wrote:
> > I need to be able to use virt-viewer to access remote systems (e.g. virt-viewer --connect qemu+ssh://some.host/system vm-name), and it would appear that it's impossible to install due to conflicts:
> >
> > # dnf install virt-viewer
> > Error: package virt-viewer-2.0-2.fc23.x86_64 requires libvirt.so.0()(64bit), but none of the providers can be installed
> > (try to add '--allowerasing' to command line to replace conflicting packages)
> >
> > If I do add --allowerasing it will want to remove qubes-gui-vm and xen-qubes-vm, which seems like it would do bad things.
> >
> > Any suggestions how I could get virt-viewer installed without clobbering other stuff?
>
> It looks to be because of xen-libs package: Fedora 23 have 4.5, but
> Qubes 3.1/3.2 use 4.6. And all the Qubes related packages are linked
> with 4.6, while Fedora ones with 4.5.
>
> Try upgrading to Fedora 24, which uses Xen 4.6.

That was it, thank you. I am now able to use virt-viewer again.

Best,
--
Konstantin Ryabitsev
Linux Foundation Collab Projects
Montréal, Québec

signature.asc

ludwig jaffe

unread,

Sep 13, 2016, 11:26:10 AM9/13/16

to qubes-users

Can one use virtviewer to give another remote user control about one guest-vm?
This would be a cool feature, if there is authentication of remote users against a role based system, so that remote users are able to run certain VMs on the machine.
How could this be made?

pixel fairy

unread,

Sep 13, 2016, 12:20:33 PM9/13/16

to qubes-users

On Tuesday, September 13, 2016 at 8:26:10 AM UTC-7, ludwig jaffe wrote:

> Can one use virtviewer to give another remote user control about one guest-vm?
> This would be a cool feature, if there is authentication of remote users against a role based system, so that remote users are able to run certain VMs on the machine.
> How could this be made?

are you talking about screen sharing? there are already tools for this. vnc and rdp are the most common.

to directly connect to the vms gui, with the os on the vm, would need access to dom0, and basically break qubes security model.

pixel fairy

unread,

Sep 13, 2016, 12:21:19 PM9/13/16

to qubes-users

meant to say without the os or any software on the vm being involved

ludwig jaffe

unread,

Sep 14, 2016, 3:30:34 PM9/14/16

to qubes-users

From a user point of view:
Just send the red framed applications to another remote user to display them there, after the user authenticated to the machine and his role allow him to see red framed applications of the red VM only.

This would be cool for colaboration.

pixel fairy

unread,

Sep 14, 2016, 5:52:17 PM9/14/16

to qubes-users

On Wednesday, September 14, 2016 at 12:30:34 PM UTC-7, ludwig jaffe wrote:

> From a user point of view:
> Just send the red framed applications to another remote user to display them there, after the user authenticated to the machine and his role allow him to see red framed applications of the red VM only.
>
> This would be cool for colaboration.

this is already possible. you can use vnc or rdp, for example, or services like chrome remote desktop.

for just a text connection you can use gnu screen or tmux.

because of qubes network model, you'll have to port forward either from the network/firewall/proxy vm, or tunnel out with ssh, netcat etc.

for example, you want to share your screen with a collaborator, and you both have a ssh access to ourprivateshell.example.com. in your shared vm, ssh -R 5900:127.0.0.1:5900 ourprivateshell.example.com then your collaborator will ssh -L 5900:1270.0.0.1:5900 ourprivateshell.example.com and run their vncviewer.

for this session, you would want to run that appvm in one screen instead of the usual qubes mixed windows. an hvm is one easy way.

is there an easy way to run an appvm in a single window?

Reply all

Reply to author

Forward