Changes

Before proceeding it is important to note that VNC itself does not include any security measures. If a default VNC session is used over the internet, therefore, the session is subject susceptible to eavesdropping. It is, however, possible to use secure tunneling techniques to protect VNC sessions. Both the secure and insecure methods of using VNC will be covered in this chapter.

where ''<IP Address of Xen Host>'' is the IP address or host name of the ''Xen host '' system on which the guest domainU system is runningand not the IP address of the domainU guest. if The reason for this is that we are accessing the desktop via VNC services provided by domain0 on the host and not by VNC servers running on the guest. For details on running and accessing VNC servers on a domainU guest read the chapter entitled [[Running and Connecting to VNC Servers on a Xen Guest (domainU) System]]. If vncviewer is being run on teh the Xen host then ''localhost'' will suffice.

If a password was specified in the Xen domainU configuration file then vncviewer will prompt for this before the graphical console is displayed:

[[Image:vncpasswd.jpg|The vncviewer tool asks for a password is if one was specified in the Xen domainU configuration file.]] Assuming that vncviewer is able to connect to the server the graphical console will appear. Note that at this point no desktop is running so all that will be displayed is output from the boot process of the domainU guest. the follwoing figure show a typical graphical console before a desktop environment has been launched: [[Image:xen_vnc_no_desktop.jpg|A vncviewer session before a desktop has been launched on the Xen domainU guest]] At this point there should be both a Xen text console and the VNC viewer session running and visible. The next step is to start a desktop environment. == Starting a Graphical Desktop on the Xen domainU Guest ==