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

To run an X application inside a [[VEcontainer]], one need needs simply to connect to a VE container with '''ssh -X''':

After login to VE container check that <code>$DISPLAY</code> variable is set and X11 forwarding is enabled:

In case <code>$DISPLAY</code> is not set, make sure that X forwarding is enabled in <code>sshd</code> config inside VEcontainer. 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 VE 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:

Now you can run X applications from your VEcontainer:

First, one need to run '''Xvnc''' server inside VEcontainer. The easiest way for this is to run

host# vncviewer <VE_IPcontainer_IP>:1

<code>~/.vnc/xstartup</code> file on the VEcontainer.

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

== Using xdm XDM with XDMCP ==First offThis method will give you a graphical login prompt remotely similar to VNC, as of December 2007but with some differences. Most notably, I was never able XDMCP is faster than VNC (due to successfully get an Xserver to run inside a VE and have it's display output onto virtual-terminal 7 (the Xserver defaultway each deals with screen handling)and but you CANNOT connect to existing sessions like you can with VNC. Each time you logout, However, your programs are closed. XDMCP is better suited in situations where you can get an Xserver running on the hostnode to don't have a local display output on virtual-terminal 7 without any special configuration (as the hostnode has direct access or dumb terminals/clients) but want to all necessary devices).run X11 programs

=== VE container Configuration ===

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 VEcontainer.

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. Insert '''0=inactive''' in [servers] section. Insert '''Enable=1''' in [xdmcp] section. Also, change from VCAllocation=true to VTAllocation=false and comment out the FirstVT=7 lineif that lines exists. Change the access restrictions (if any) to suit your needs and then start GDM.

=== Hostnode Client/Host Configuration === On the HNClient/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 are is entirely optional (and not recommended as on the client, but keep in mind that itwon'll unnecessarily just chew up resources) t be used while you're connecting to the desktop on the HNcontainer.

There are guides online on howto securely tunnel XDMCP over the Internet (typically vpn as XDMCP settings can't be tunneled over ssh giving you securityafaik), in an otherwise INSECURE protocol. This approach has some major benefits over the VNC method described above === Errata ===On a side note, as of December 2007, but also has I was never able to successfully get an Xserver to run inside a couple of major drawbacks. The biggest pro being XDMCP is faster than VNC container and have the display output onto virtual-terminal 7 (due 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 way each deals hostnode has direct access to all necessary devices). Another user has done this with screen handling) XDM and X. Just follow the directions on the biggest con being that you CANNOT connect to existing sessions like you can with VNCwiki. Each time you logout, your programs are closed It is possible. == See also ==* [[NX inside VE]]

* http://ait.web.psi.ch/services/linux/kde-desktop-sharingsoftware/local/by_task/desktop_sharing/index.htmhtml