1,798
edits
Changes
no edit summary
So far in [[Xen Virtualization Essentials]] we have focused on running Xen domainU systems using just the text based console to interact with the system. It is not uncommon, however, to need to view and interact with a graphical desktop environment running on the guest operating system. This can be achieved using one of two technologies known as SDL and VNC. Probably the most flexible option is that provided by VNC.
In terms of displaying graphical desktop environments for a Xen guest, VNC offers two approaches. The first approach (covered in this chapter) involves suing using VNC capabilities that are build into the Xen guest domain (domain0) to view and interact with the virtual frame buffer (vfb) of the domainU system. A second option is to run one or more VNC servers directly on the domainU system and connect directly to those servers. This approach will be covered in the next chapter ([[Running and Connecting to VNC Servers on a Xen Guest (domainU) System]]).
== What is VNC? ==
VNC is an acronym for Virtual Network Computing and essentially provides a way to provide remote access to graphical desktop environments. The system consists of one or more VNC servers running on a remote system and VNC viewers running on a local system. The VNC server runs the graphical desktop on the remote system and transmits the appearance of the desktop to the VNC viewer. The VNC viewer in turn transmits user interactions with the desktop to the VNC server where they are relayed to the desktop environment. VNC uses compression algorithms to speed the display process and is supported on a wide range of platforms. This makes it possible, for example, to display a Linux desktop environment on a remote Windows system and vice a versa.
The VNC server and viewer components can communicate over any network connection including the internetallowing desktops to be accessed from anywhere in the world where an internet connection is available.
== VNC Security ==
