1,798
edits
Changes
→Configuring the Xen domainU Desktop Environment
When the desktop appears you will notice that it doesn't look much like the standard desktop you would expect to see on most modern Linux distributions. In fact it may will look something like the following figure:
[[Image:xen_domainU_remote_desktop_twm.jpg|A basic Xen domainU desktop running twm]]
The problem here is that by default VNC starts a minimal desktop environment (typically using a basic window manager known as ''twm'') so we need to configure the VNC session to launch the correct desktop. To do this exit from vncviewer and then shutdown the VNC desktop session on the domainU system as follows:
Finally, reconnect from the remote system. The full desktop should now appear in the VNC viewer window:
[[Image:xen_vnc_domainU_gnome_desktop.jpg|The GNOME desktop running on a Xen domainU system displaying over VNC]]
If KDE is your preferred desktop simply change the xstartup file so that it executes ''startkde'' instead of ''twm'' or ''gnome-session''.
== Closing Down a domainU VNC Desktop Session ==
As long as the vncserver session is running the desktop will continue to run regardless of whether a ''vncviewer'' instance is connected. this means that you can exit from vncviewer and reconnect later and find the desktop exactly as you left it.
Before closing down the actual VNC server session it is important to verify that any applications running on the desktop in question have been cleanly exited to avoid loss of data. Once all applications are closed log out of the desktop environment in the ''vncviewer'' session and then exit ''vncviewer''.
On the domainU guest system on which the ''vncserver'' server is running execute the ''vncserver'' command with the ''--kill'' option specifying the display to shut down. For example:
<pre>
vncserver -kill :1
</pre>
This will close down the VNC server session on display :1
