REMOTE-VIEWER(1) | Virtualization Support | REMOTE-VIEWER(1) |
remote-viewer - a simple remote desktop client
remote-viewer [OPTIONS] -- [URI]
remote-viewer is a simple remote display client. The supported protocols are SPICE and VNC.
Starting remote-viewer without URI will open a simple dialog with an entry and a list of previously successfully accessed URI.
The URI can also point to a connection settings file, see the CONNECTION FILE section for a description of the format.
If URI is '-', then remote-viewer will read the standard input as a connection settings file and attempt to connect using it.
The following options are accepted when running "remote-viewer":
If supported, the remote display will be reconfigured to match the physical client monitor configuration, by enabling or disabling extra monitors as necessary. This is currently implemented by the Spice backend only.
To specify which client monitors are used in fullscreen mode, see the CONFIGURATION section below.
--hotkeys=toggle-fullscreen=shift+f11,release-cursor=shift+f12 --hotkeys=release-cursor=ctrl+alt
Note that hotkeys for which no binding is given are disabled. Although the hotkeys specified here are handled by the client, it is still possible to send these key combinations to the guest via a menu item.
Note that it can't offer a complete secure solution by itself. Your kiosk system must have additional configuration and security settings to lock down the OS. In particular, you must configure or disable the window manager, limit the session capabilities, use some restart/watchdog mechanism, disable VT switching etc.
A key binding combination is described by a series of key strings separated by '+' that must be pressed together in order to activate the associated action.
It must be composed of modifiers (shift, ctrl or alt) and a non-modifier key. For example, "shift+f11".
remote-viewer connection file is of INI file format, with a mandatory [virt-viewer] group and "type" key.
Opening a file with the following content will start remote-viewer in fullscreen and connect to the host "betsiboka" using the SPICE protocol:
[virt-viewer] type=spice host=betsiboka port=5900 fullscreen=1
The version format accepted is a list of integers separated by '.'. It can be followed by a dash '-' and an additional build number with the same format.
Version comparison is done by comparing each integer from the list one by one. If any of the component is not a number, the version comparison will fail and consider that the 2 versions are considered to be the same.
The current SPICE channels are: main, display, inputs, cursor, playback, record, smartcard, usbredir.
The effects that can be disabled with SPICE are: wallpaper, font-smooth, animation or all.
"class,vendor,product,version,allow"
Use -1 for class/vendor/product/version to accept any value.
And the rules themselves are concatenated like this:
"rule1|rule2|rule3"
The current SPICE channels are: main, display, inputs, cursor, playback, record, smartcard, usbredir.
At the time of writing this documentation, the only supported proxy method with Spice is HTTP CONNECT.
For example, to tunnel connection through foobar host HTTP proxy on port 8080, use the value "http://foobar:8080".
The connection file can also carry some oVirt-specific options when oVirt support is compiled in. These options are used to interact with oVirt REST API. This is currently only used in order to show a menu allowing to change the CD image being used by the virtual machine from remote-viewer user interface. These options go in an optional [ovirt] group.
A small number of configuration options can be controlled by editing the settings file located in the user configuration directory:
<USER-CONFIG-DIR>/virt-viewer/settings
This file is a text file in INI format, with application options in the [virt-viewer] group and per-guest options in a group identified by the guest's UUID. The application options should not be edited manually. There is also a special [fallback] group which specifies options for all guests that don't have an explicit group.
For each guest, the initial fullscreen monitor configuration can be specified by using the monitor-mapping key. This configuration only takes effect when the -f/--full-screen option is specified.
The value of this key is a list of mappings between a guest display and a client monitor. Each mapping is separated by a semicolon character, and the mappings have the format <GUEST-DISPLAY-ID>:<CLIENT-MONITOR-ID>.
For example, to map guest displays 1 and 2 to client monitors 2 and 3 for the guest with a UUID of e4591275-d9d3-4a44-a18b-ef2fbc8ac3e2, use:
[e4591275-d9d3-4a44-a18b-ef2fbc8ac3e2] monitor-mapping=1:2;2:3
The monitor-mapping must contain ids of all displays from 1 to the last desired display id, e.g. "monitor-mapping=3:3" is invalid because mappings for displays 1 and 2 are not specified.
To connect to SPICE server on host "makai" with port 5900
remote-viewer spice://makai:5900
To connect to VNC server on host "tsingy" with port 5900
remote-viewer vnc://tsingy:5900
To connect to a virtual machine named "toliara" on an oVirt server at example.org
remote-viewer ovirt://[username@]example.org/toliara
Report bugs to the mailing list "http://www.redhat.com/mailman/listinfo/virt-tools-list"
Copyright (C) 2012-2014 Red Hat, Inc., and various contributors. This is free software. You may redistribute copies of it under the terms of the GNU General Public License "https://www.gnu.org/licenses/gpl-2.0.html". There is NO WARRANTY, to the extent permitted by law.
"virt-viewer(1)", "spice-client(1)", the project website "http://virt-manager.org"
2018-07-27 | perl v5.26.2 |