Setting up GUI Desktop on a VM: Difference between revisions
(updating links) |
(added intro, removed draft flag) |
||
Line 2: | Line 2: | ||
<!--T:1--> | <!--T:1--> | ||
<languages /> | <languages /> | ||
Some software that you can install on your virtual machine (VM, or instance) are only, or best accessed, through their graphical user interface (GUI). It is possible to use a GUI through SSH + X11 forwarding. However, you may observe better performance when using VNC to connect to a remote desktop running on your VM. | |||
Below, we outline steps for setting a remote desktop with VNC. Please note that these instructions are for a VM running a Ubuntu operating system. | |||
<ol> | <ol> | ||
<li>Install a GUI Desktop on your VM.<br/> | <li>Install a GUI Desktop on your VM.<br/> |
Revision as of 20:08, 23 November 2022
Some software that you can install on your virtual machine (VM, or instance) are only, or best accessed, through their graphical user interface (GUI). It is possible to use a GUI through SSH + X11 forwarding. However, you may observe better performance when using VNC to connect to a remote desktop running on your VM.
Below, we outline steps for setting a remote desktop with VNC. Please note that these instructions are for a VM running a Ubuntu operating system.
- Install a GUI Desktop on your VM.
There are lots of different Desktop packages available. For example some common Desktop packages available for the Ubuntu operating system are:- ubuntu-unity-desktop
- ubuntu-mate-desktop
- lubuntu-desktop
- xubuntu-desktop
- xfce4
- ubuntu-desktop
- kde-plasma-desktop
- ubuntu-desktop-minimal
- cinnamon
- icewm
[name@server ~]$ sudo apt update [name@server ~]$ sudo apt upgrade -y [name@server ~]$ sudo apt install ubuntu-mate-desktop
During the installation of the
ubuntu-mate-desktop
package it will ask you to choose the default display manager, a good option islightdm
. Installing theubuntu-mate-desktop
package can take a fair amount of time (something like 15-30 mins). - Install TigerVNC server.
This software runs on your VM and allows you to use the GUI desktop you installed in step 1. remotely using a client software.[name@server ~]$ sudo apt install -y tigervnc-common tigervnc-standalone-server
This command will install the TigerVNC server and some supporting software. For details about using VNC servers and clients see our docs on VNC.
- Start the vnc server
The first time you start a vnc server it will ask you to set a password. This password is used later when connecting to the vnc desktop. You don't need a view-only password. The
[name@server ~]$ vncserver -> enter a password -> enter "n" for view-only password
vncpasswd
command can later be used to change your password. - Open port
5901
and test connection (see security groups for more information about opening ports to your VMs with OpenStack). However, this is not secure as the data sent to and from your VM will not be encrypted. - Connect using an SSH tunnel (see SSH_tunnelling). There is an example of creating an SSH tunnel to a VNC server running on a compute node of one of our clusters here: VNC#Compute_Nodes.
- Instructions for connecting using an SSH tunnel for linux or mac:
- Open your terminal
- type the following: SSH -i filepathtoyoursshkey/sshprivatekeyfile.key -L5901:localhost:5901 ubuntu@ipaddressofyourVM
- Download and run the latest tigerVNC-x.y.z.dmg package installer. Configure the default viewer settings by clicking the desktop TigerVNC Viewer icon. In the "VNC Viewer: Connection Details" window that appears click "Options -> Security" then tick all boxes. To save the settings click OK and then click Connect. If Connect is not clicked, the settings will not be saved.
- open the tigervnc viewer application and in the VNC server field enter: localhost:5901.
- your GUI desktop for your remote session should now open
- Close port 5901. Once you are connected to your VNC server using an SSH tunnel, you no longer require port 5901 open so it is recommended that you remove this rule from your security groups. (see Managing_your_cloud_resources_with_OpenStack#Security_Groups security groups for more information).
- To stop the vncserver
[name@server ~]$ vncserver -kill :1