OpenVZ Virtuozzo Containers Wiki - User contributions [en]

Application Templates

2010-03-02T21:05:42Z

SHaggY caT: /* Step 3: Package the Software */ Fix broken command

===Abstract===
Application Templates (AT's) are commonly found when using Virtualization as a means to try out new software without having to perform a full manual install. Unfortunately, OpenVZ, as of yet, doesn't have any precreated AT's for people to try out, which might be attributed to the lack of documentation on how to create them. The primary goal of this howto is to give an overview of how an AT can be created for OpenVZ without too much trouble. This howto assumes the user is familiar with basic OpenVZ terminology and operation, so basic tasks such as setting VE memory, networking parameters, package repositories, etc are not covered here.

===Introduction===
There are two ways to create an AT: as a full VE template, or an interactive shell script/installer that installs the software into an existing VE. The second method is more advanced, and will be very specific to the individual applications, so is out of the scope of this document.

===Step 1: The Base===
Choose the base OS you'd like to use and find an existing VE template to use (or create your [{{fullurl:Category:Templates}} own]). For this document, I'm using the [http://download.openvz.org/template/precreated/contrib/centos-5-x86_64-default-5.2-20081107.tar.gz CentOS 5 x86_64] template and will be installing Ruby-on-Rails.
====Creating the bare VE====
<pre>vzctl create 3000 --ostemplate centos-5-x86_64-default-5.2-20081107 --hostname RoR-AT
vzctl set 3000 --userpasswd root:<whatever> --save</pre>

===Step 2: Software Installation===
This is the part where you'll follow the application specific installation procedures. Make sure that you install all the dependancies and do a proper configuration so that the application is usable.
In regards to Ruby-on-Rails, I found a good guide on installing RoR on CentOS [http://wiki.rubyonrails.org/rails/pages/RailsOnCentos here].

===Step 3: Package the Software===
Once you have everything installed and configured, packaging is a simple procedure:
*Remove any unecessary files (e.g. /tmp /var/tmp /usr/src/, any downloaded files, etc)
*Stop the VE
:<pre>vzctl stop 3000</pre>
*Create a tar.gz of the /vz/private/$VEID directory
:<pre>tar cfvz /vz/template/cache/centos-5-x86_64-RoR-AT-11152008.tar.gz ./ </pre>
*Done

===Step 4: Deployment/Distribution===
To do rapid deployment of your new AT, you can utilize for/while loops to create multiple VE's as shown [[Demo scripts | here]].

As for distribution, please share any of the AT's you create [http://download.openvz.org/template/precreated/contrib/ here]

[[Category:HOWTO]]
[[Category:Templates]]

Install vzpkg2 and pkg-cacher

2009-03-19T13:16:09Z

SHaggY caT: This packege did'nt install by you for dependenses, and, Debian/Ubuntu template cahe did'nt created

=== Introduction ===

Robert Nelson has created a couple new utilities to make managing and updating templates and containers easier, vzpkg2 pkg-cacher. So far they will create and update a large range of containers, including both 32bit and 64bit of the following:

* Centos 4 and 5,
* Fedora 7, 8 and 9,
* Debian Sarge and Etch,
* Ubuntu Feisty, Gutsy and Hardy.

Pkg-cacher is a transparent caching proxy daemon optimized for Debian and RPM packages. In other terms, pkg-cacher is a service that runs on a machine that other machines and containers, or "clients", use to update themselves instead of each of them directly hitting the package repositories. Pkg-cacher only downloads a file once and then gives that to all its clients, instead of each of the clients downloading the file from the Internet at large. It is based on [http://www.nick-andrew.net/projects/apt-cacher/ apt-cacher], available with Debian. This version has been modified to understand RedHat RPM repositories. It also adds support for the HTTP Range header and deals correctly with files which have the same name but different content on different distributions or in some cases different versions of the same distribution.

Robert has setup repositories for Fedora, CentOS and Debian.

====Screencast====

Scott Dowdle has recorded a good screencast overview of vzpkg2 and pkg-cacher at:

http://www.montanalinux.org/vzpkg2-screencast.html

===Installation===

====Centos & Fedora installs:====

=====Remove Old Packages=====
If this is an '''existing''' install, uninstall your vzpkg and vztmpl-* packages:

yum remove vzpkg vztmpl-*

and backup & remove your current template directory:

tar cjf /some/backup/location/old_templates.tbz /vz/template
rm -r /vz/template

If this is a '''new''' install, you should probably review the [http://download.openvz.org/doc/OpenVZ-Users-Guide.pdf OpenVZ User's Guide] and the wiki's [[Quick installation]] page. The only way you would vary your installation setups is declining to install the default vzpkg package, and instead using vzpkg2 here.

=====Download the repository file for your OS=====

For CentOS:
wget http://repo.opensource-sw.net/centos/ossw.repo -P /etc/yum.repos.d

For Fedora:
wget http://repo.opensource-sw.net/fedora/ossw.repo -P /etc/yum.repos.d

You may wish to edit the repository file, perhaps to add a priorities setting.

=====Install vzpkg2 and pkg-cacher=====

Once the repository is added in /etc/yum.repos.d, you can now install the new vzpkg2 and pkg-cacher from it:

yum install vzpkg2 vztmpl2-centos vztmpl2-fedora vztmpl2-debian vztmpl2-ubuntu
yum install pkg-cacher-sa debootstrap

=====Configure vzpkg2=====

Open /etc/vz/vzpkg.conf in an editor. Replace 'hostname' with the hostname or IP of the machine you are installing this on for VZPKG_CACHE_HOST, make sure not to use 'localhost', because this name is what OpenVZ Containers will use to access the pkg-cacher daemon:

VZPKG_CACHE_HOST=hostname:3142

While you are here, review this file to ensure it makes sense for your setup. In particular, you will probably have to update the VZPKG_DNS line with IP addresses of DNS servers you use.

VZPKG_DNS=192.168.1.2,192.168.1.3

=====Configure pkg-cacher=====

Edit /etc/pkg-cacher/pkg-cacher.conf. You should read the included documentation in the file to ensure it is appropriate for your setup. Mostly the defaults will work just fine. By default pkg-cacher will let any system use its cache. You will probably want to limit it to your own systems on the line:

allowed_hosts=*

Once you have checked and updated pkg-cacher.conf, simply restart it by running as root:

service pkg-cacher restart

=====Generate the new template cache=====

Now everything should be ready to go! Make sure both the 'vz' service and 'pkg-cacher' service are running.

To build an individual OS Template just run the 'vzpkgcache' command and pass it the name of the OS Template you want to build. For a list of OS Templates you can build, run the 'vzpkgls' command. Example:

vzpkgcache centos-5-i386-default

If you'd like to build all OS Templates available, just run the 'vzpkgcache' command without any parameters. Example:

vzpkgcache

vzpkg2 should get to work generating your initial caches. Now you can run 'vzctl create' and use them.

====Debian Installs:====

=====Remove Old Packages=====
If this is an '''existing''' install, uninstall your vzpkg and vztmpl-* packages:

apt-get erase vzpkg vzctl-ostmpl-*

and backup & remove your current template directory:

tar cjf /some/backup/location/old_templates.tbz /vz/template
rm -r /vz/template

If this is a '''new''' install, you should probably review the [http://download.openvz.org/doc/OpenVZ-Users-Guide.pdf OpenVZ User's Guide] and the wiki's [[Installation on Debian]] page. The only way you would vary your installation setups is declining to install the default vzpkg package, and instead using vzpkg2 here.

=====Add the deb repositories to your /etc/apt/sources.list:=====

Add the following lines to your /etc/apt/sources.list:

Etch:
deb http://repo.opensource-sw.net/debian/ etch openvz
deb-src http://repo.opensource-sw.net/debian/ etch openvz

Sarge:
deb http://repo.opensource-sw.net/debian/ sarge openvz
deb-src http://repo.opensource-sw.net/debian/ sarge openvz

Then do:
apt-get update
apt-get install pkg-cacher-sa vzpkg2

=====Adding New Templates:=====

Install the desired OS Template Metadata packages:

apt-get install vztmpl2-centos vztmpl2-fedora vztmpl2-ubuntu vztmpl2-debian

=====Configure vzpkg2=====

Open /etc/vz/vzpkg.conf in an editor. Replace 'hostname' with the hostname or IP of the machine you are installing this on for VZPKG_CACHE_HOST, make sure not to use 'localhost', because this name is what OpenVZ Containers will use to access the pkg-cacher daemon:

VZPKG_CACHE_HOST=hostname:3142

While you are here, review this file to ensure it makes sense for your setup. In particular, you will probably have to update the VZPKG_DNS line with IP addresses of DNS servers you use.

VZPKG_DNS=192.168.1.2,192.168.1.3

=====Configure pkg-cacher=====

Edit /etc/pkg-cacher/pkg-cacher.conf. You should read the included documentation in the file to ensure it is appropriate for your setup. Mostly the defaults will work just fine. By default pkg-cacher will let any system use its cache. You will probably want to limit it to your own systems on the line:

allowed_hosts=*

Once you have checked and updated pkg-cacher.conf, simply restart it.

=====Generate the new template cache=====

Now everything should be ready to go! Make sure both the 'vz' service and 'pkg-cacher' service are running

To get a list of what OS Templates you may now use, type the following:

vzpkgls

That will produce a list of available OS Templates. Use any name given in the list as a parameter to vzpkgcache to build that OS Template. Example:

vzpkgcache centos-5-i386-default

If you want to build all OS Templates you can simply run vzpkgcache without any paramters:

vzpkgcache

vzpkg2 should get to work generating your initial caches. Now you can run 'vzctl create' and use them.

===Source===

The source for the new vzpkg2 and templates is available on http://git.opensource-sw.net. In order to clone the updated source use the command:
git clone http://git.opensource-sw.net/git/vzpkg

The templates are available using:
git clone http://git.opensource-sw.net/git/vztmpl

Package managers

2008-10-18T11:07:06Z

SHaggY caT: /* Commands */ name "Mandrike" RIP, now uses "Mandriva"

With OpenVZ, you can run many different Linux distributions on a single box. One particular thing in which distributions differ is package management. This article summarizes how to perform various common package management tasks on a different distributions.

== Commands ==
{| class="wikitable"
! align="center" | Action
! RPM RHEL, Fedora, CentOS, Mandriva, SUSE, ...
! DEB Debian, Ubuntu
! Ebuild Gentoo, Sabayon
|-
! colspan="4" align="center" | <big>'''Basic queries'''</big>
|-
! List of all installed packages
|| <code>rpm -qa</code>
|| <code>dpkg -l</code>
|| <code>equery list</code>
|-
! List of installing packages matching ''substr''
|| <code>rpm -qa ''\*substr\*''</code>
|| <code>dpkg -l ''\*substr\*''</code>
|| <code>equery list ''substr''</code>
|-
! Basic information about an installed ''package''
|| <code>rpm -qi ''package''</code>
|| <code>dpkg -p ''package''</code>
|| <code>-???-</code>
|-
! List of files in a given ''package''
|| <code>rpm -ql ''package''</code>
|| <code>dpkg -L ''package''</code>
|| <code>equery files ''package''</code>
|-
! colspan="4" align="center" | <big>'''Advanced queries'''</big>
|-
! Which package a ''file'' belongs to?
|| <code>rpm -qf ''file''</code>
|| <code>dpkg -S ''file''</code>
|| <code>equery belongs ''file''</code>
|-
! Check the hash (i.e. MD5 etc.) sums of an installed package
|| <code>rpm -V ''package''</code>
|| <code>debsums -ca ''package''</code>
|| <code>equery check ''package''</code>
|-
! Show pre/post install/uninstall scripts from a ''package''
|| <code>rpm -q --scripts ''package''</code>
|| <code>less /var/lib/dpkg/info/''package''.{pre,post,config}*</code>
|| <code>-???-</code>
|-
! Show change log for a ''package''
|| <code>rpm -q --changelog ''package''</code>
|| <code>zcat /usr/share/doc/package/changelog.Debian.gz</code> <code>aptitude [-t release] changelog package</code>
|| <code>-???-</code>
|-
! colspan="4" align="center" | <big>'''Local package installation/upgrade/removal'''</big>
|-
! Install a package from local ''package_file''
|| <code>rpm -ihv ''package_file*.rpm'' yum localinstall ''package_file*.rpm''<ref name="localinstall">In case there are unsatisfied dependencies for ''package_file'', yum will try to get and install it from known repositores.</ref></code>
|| <code>dpkg -i ''package_file*.deb'' <ref name="apt">Usually it is not necessary to download packages manually and install them. Use apt-cache search ''name'' to search for package in configured repositories and apt-get install ''package'' to install package and all it's dependencies</ref></code>
|| <code>-???-</code>
|-
! Upgrade a package from local ''package_file''
|| <code>rpm -Uhv ''package_file*.rpm''</code>
|| <code>dpkg -i ''package_file*.deb'' <ref name="apt"/></code>
|| <code>-???-</code>
|-
! Remove an installed ''package''
|| <code>rpm -e ''package''</code> 
<code>yum remove|erase ''package''<ref name="yum-remove">This will also remove any packages which depend on the ''package''</ref></code>
|| <code>dpkg -r ''package''</code> 
<code>dpkg -P ''package''</code>
|| <code>emerge --unmerge ''package''</code> 
<code>emerge --prune ''package''</code>
|-
! colspan="4" align="center" | <big>'''Package installation from repositories'''</big>
|-
! Install a ''package''
|| <code>yum install ''package''</code> 
<code>urpmi ''package''</code>
|| <code>apt-get update && apt-get install ''package''</code> 
<code>aptitude update && aptitude install ''package''</code>
|| <code>emerge -av ''package''</code>
|-
! Only download a ''package'' from repository, do not install
|| First install the yum-downloadonly plugin by running: <code>yum install yum-downloadonly</code> And then: <code>yum install|update ''package'' -y --downloadonly --downloaddir=/opt</code>
|| <code>apt-get install --download-only --reinstall ''package''</code><ref name="dpkgdir">Package will reside in /var/cache/apt/archives.</ref> <code>aptitude download ''package''</code>
|| <code>emerge -avf ''package''</code><ref name="distfiles">Package sources will reside in /usr/portage/distfiles.</ref>
|-
! colspan="4" align="center" | <big>'''Get information about package interdependencies'''</big>
|-
! What a given ''package'' provides?
|| <code>rpm -q --provides ''package''</code>
|| <code>dpkg-query -W -f='${Provides}\n' ''package''</code>
|| <code>-???-</code>
|-
! What a given ''package'' requires?
|| <code>rpm -q --requires ''package''</code>
|| <code>dpkg-query -W -f='${Depends}\n' ''package''</code>
|| <code>-???-</code>
|-
! Which installed package(s) provide a given ''dependency''<ref name="dep">In rpm world, a ''dependency'' can be a package name, a file, or a special atom like <code>perl(IO::Zlib)</code> for a perl module. In deb world, this can be either real or virtual package name.</ref>?
|| <code>rpm -q --whatprovides ''dependency''</code>
|| <code>dpkg-query -W -f='${Package}: ${Provides}\n' '*' | grep ': .*package'</code>
|| <code>-???-</code>
|-
! Which installed package(s) require a given ''dependency''<ref name="dep"/>?
|| <code>rpm -q --whatrequires ''dependency''</code>
|| <code>dpkg-query -W -f='${Package}: ${Depends}\n' '*' | grep ': .*package'</code> <code>aptitude why package</code><ref name="why">Actualy shows the whole dpendency situation that leads to install this package</ref>
|| <code>-???-</code>
|-
! Show what prevents installation of a package
|| <code>-???-</code>
|| <code>aptitude why-not package</code>
|| <code>-???-</code>
|-
! Get package source files
|| <code>-???-</code>
|| <code>apt-get source ''package''</code>
|| <code>-???-</code>
|-
! colspan="4" align="center" | <big>'''Working with package files'''</big>
|-
! Unpack a package ''file'' to local directory
|| <code>rpm2cpio ''file.rpm'' | cpio -id</code>
|| <code>dpkg -x ''file.deb'' .</code>
|| N/A
|-
! Check package file integrity (checksums, signatures...)
|| <code>rpm -K ''file.rpm''</code>
|| -???-
|| N/A
|-
! colspan="4" align="center" | <big>'''Repository queries'''</big>
|-
! Find a package which <code>/some/file</code> belongs to
|| <code>yum provides ''/some/file''</code>
|| First run: <code>apt-file update</code> and then: <code>apt-file search ''/some/file''</code>
|| N/A
|}

== Relevant directories and files ==

=== Red Hat, Fedora, CentOS ===

* yum config: <code>/etc/yum.conf</code>.
* yum repos: <code>/etc/yum.repos.d/</code>.
* rpm configs and macros: <code>/etc/rpm/</code>, <code>/usr/lib/rpm/</code>,
* rpm DB: <code>/var/lib/rpm/</code>

=== Debian/Ubuntu ===

* List of repositories and mirror sites: <code>/etc/apt/sources.list</code>, <code>/etc/apt/sources.list.d/</code>.

=== Gentoo ===

* emerge configs: <code>/etc/make.conf</code>, <code>/etc/portage/</code>.
* Portage tree: <code>/usr/portage</code>.

== Notes==
<references/>

== See also ==
=== Debian ===
* [http://www.debian.org/doc/FAQ/ch-pkgtools.en.html Debian FAQ: package management tools]
* [http://www.debian.org/doc/manuals/apt-howto/ APT HOWTO]

[[Category: HOWTO]]
[[Category: Templates]]
[[Category: Debian]]
[[Category: Ubuntu]]
[[Category: Gentoo]]

User:SHaggY caT

2008-10-04T07:58:55Z

SHaggY caT: New page: Hi! My Name is Galia, i'm live in Moscow, Russia. I work in one big Internet-company, and, I very intresting virtualization technologies.

Hi! My Name is Galia, i'm live in Moscow, Russia.
I work in one big Internet-company, and, I very intresting virtualization technologies.

X inside VE

2008-10-04T07:52:37Z

SHaggY caT: /* See also */ fix link

There are several ways to run X applications inside your [[container]].

== X forwarding ==

=== Single application ===

To run an X application inside a [[container]], one need simply to connect to a container with '''ssh -X''':
<pre>
host# ssh -2 -c blowfish -X user@address
</pre>

After login to container check that <code>$DISPLAY</code> variable is set and X11 forwarding is enabled:
<pre>
ve# echo $DISPLAY
localhost:10.0
</pre>

In case <code>$DISPLAY</code> is not set, make sure that X forwarding is enabled in <code>sshd</code> config inside container. In most Linux distros sshd configuration is stored in <code>/etc/ssh/sshd_config</code>. You should set parameter <code>X11Forwarding</code> to <code>yes</code>. Also container should contain <code>xauth</code> package, thus install <code>xauth</code> if it is missing (in Debian this is part of the xbase-clients package). After that, restart your sshd daemon:
<pre>
ve# /etc/init.d/sshd restart
</pre>

{{Note|Don't forget to reconnect after this}}

Now you can run X applications from your container:
<pre>
ve# firefox
</pre>

=== Desktop ===

Note : If you want to run complete X window environment (including window manager), you should kill local window manager and run only pure X server. Secondly you should use '''-Y''' option when invoking ssh. And if you want to run gnome/kde/..., don't forget to increase [[UBC]] limits, 'cause default values are certainly too small for these monsters. ;)

You can run a desktop with ''xinit'' (on the node):

<pre>
xinit -e ssh -XCc blowfish user@ip_address "/usr/bin/xfce4-session &" -- :1 & disown
</pre>

* Substitute the window manager of choice
* Once xfce has started, you can then close the xterm if you like

Your node will be on Ctrl-Alt-F7

And your VM on Ctrl-Alt-F8

== VNC for X desktop ==
First, one need to run '''Xvnc''' server inside container. The easiest way for this is to run
'''vncserver''' script. This scripts starts all the required services
and small http daemon which provides graphical web access to your desktop (via Java applet).

<pre>
ve# vncserver -name mydesktop
New 'mydekstop' desktop is ve:1

Starting applications specified in ~/.vnc/xstartup
Log file is ~/.vnc/ve:1.log
</pre>

Now when your desktop is up and running you can connect to it
using '''vncviewer''' command:
<pre>
host# vncviewer <container_IP>:1
</pre>

If the VNC desktop is the same size or larger than your X desktop, you will see scroll bars on the bottom and the side. This is often inconvenient. You may reduce your VNC desktop to a more reasonable size like this:
<pre>vncserver -geometry 1000x650</pre>
This setting works quite well for a 1024 by 768 X desktop setting.

=== Starting KDE desktop with VNC ===
To start KDE desktop instead of default twm one replace <code>twm &</code> line with <code>startkde &</code> in user's
<code>~/.vnc/xstartup</code> file on the container.

=== Connecting with VNC from firewalled network ===
VNC uses 590x TCP ports for its connections. These ports can be firewalled in
many networks so in order to be able to connect to remote side one need to tunnel VNC connections somehow.
A usual '''ssh''' can be used for tunneling VNC connections as described below.

<pre>
localhost# ssh -L 5900:localhost:5900 <remote host>
</pre>

where <remote host> is the name of the system you want to connect to. When you are asked for a username and password enter your normal username and password. Then start the VNC session to localhost, i.e.

<pre>
localhost# vncviewer localhost
</pre>

== Using Xephyr ==

Xephyr gives you nested X windows.

First, install Xephyr on your host.

Start Xephyr

<pre>Xephyr -ac -screen 1280x1024 -br -reset -terminate :1 &</pre>

Change your display settings (don't forget to change them back after you establish a connection)

<pre>DISPLAY=:1,0</pre>

Forward your application or desktop over ssh to Xephyr

<pre>ssh -XfC -c blowfish user@server xfce4-session</pre>

If you use an alternate window manager, substitute "startkde", "gnome-session", "startfluxbox", etc. as needed.

[http://cafelinux.org/OptickleArt/albums/userpics/Xephyr.png Screenshot]

== Using XDM with XDMCP ==
This method will give you a graphical login prompt remotely similar to VNC, but with some differences. Most notably, XDMCP is faster than VNC (due to the way each deals with screen handling) and but you CANNOT connect to existing sessions like you can with VNC. Each time you logout, your programs are closed. XDMCP is better suited in situations where you don't have a local display (or dumb terminals/clients) but want to run X11 programs

=== container Configuration ===
Install your desktop environment as you'd like (kde/gnome/xfce/etc) and ensure you install at least XDM. You can opt to use GDM/KDM as they also do the same job as XDM. The configuration for KDM/GDM is different than XDM's and I was only able to find one link on configuring GDM (more below).

===== XDM =====
Configuring XDM requires editing 3 files: /etc/X11/xdm/xdm-config, /etc/X11/xdm/Xservers, /etc/X11/xdm/Xaccess

In xdm-config, comment out the line where it says '''DisplayManager.requestPort: 0'''

In Xservers, comment out the line ''':0 local /usr/bin/X :0 vt7'''' (this starts a local X server, which will fail)

In Xaccess, uncomment the line with ''' * #any host can get a login window'''
(Please keep in mind the security implications by the above line. Read the comments found in the file and set it appropriately)

To provide the possibility to run sound applications from container, /dev/dsp device file needs to be exported in container:
<pre>
vzctl set 221 --devnodes dsp:rw --save
</pre>

Finally, if you intend to make xdm invoking a heavy desktop like kde, it is reasonable to increase the amount of memory available for allocation inside this container:
<pre>
vzctl set 221 --privvmpages 500M:600M --save
</pre>
For light desktop like icewm this is not needed.

Once these changes have been made, start your xdm server by the appropriate startup script (typically similar to /etc/init.d/xdm start). That concludes the XDM setup in the container.

===== GDM =====
Edit the '''gdm.conf''' file and in xdmcp section, comment out the 0=standard line under the [servers] section - this will prevent gdm from trying to launch an X server on the local machine - it will simply listen for xdmcp requests. Also, change from VCAllocation=true to VTAllocation=false and comment out the FirstVT=7 line. Change the access restrictions (if any) to suit your needs and then start GDM.

=== Client/Host Configuration ===

On the Client/Host (whatever machine you are connecting from to the container), you need to install ONLY a bare Xserver as per your OS instructions (use yum, emerge, apt, whatever). A desktop environment like XFCE/GNOME/KDE is entirely optional on the client, but keep in mind that it won't be used while you're connecting to the desktop on the container.

To get access to the XDM server, just start an Xserver with '''X -query <remote IP> :0''' (where :0 is the local display...set to :1 if you already have an X session running, or use Xnest)

There are guides online on howto securely tunnel XDMCP over the Internet (typically vpn as XDMCP can't be tunneled over ssh afaik), in an otherwise INSECURE protocol.

=== Errata ===
On a side note, as of December 2007, I was never able to successfully get an Xserver to run inside a container and have the display output onto virtual-terminal 7 (the Xserver default), However, you can get an Xserver running on the hostnode to display output on virtual-terminal 7 without any special configuration (as the hostnode has direct access to all necessary devices).

== See also ==
* [[NX inside VE]]

== External links ==
* http://forum.openvz.org/index.php?t=tree&th=235&mid=1115&&rev=&reveal=
* http://ait.web.psi.ch/services/linux/software/local/by_task/desktop_sharing/index.html
* http://ait.web.psi.ch/services/ssh/vnc-ssh.html
* http://www.vnc.com/pipermail/vnc-list/2002-July/031831.html
* http://www.linuxjournal.com/article/5499
* http://www.realvnc.com/pipermail/vnc-list/2002-March/029502.html
* http://www.redhat.com/archives/rhl-list/2003-December/msg01859.html
* http://faq.gotomyvnc.com/fom-serve/cache/56.html

[[Category: HOWTO]]
[[Category: Networking]]
[[Category: X]]