[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] VM Remote access options

> Just to error test my own thinking here, there seems to be the following
> options for remote graphical access to a running domian vm.  Besides the
> normal network service via a port and a raw console, the options are 
> straight X, VNC, and XN.
> X - supports a single X window running on a local XServer, tied to a single
> process on the remote system.  No remote desktop

Checkout the Xnest server. It allows you to run an Xserver
displaying to an Xwindow (which can be full screen).

> VNC - comes in two flavors of server.  The original at&t server supports a
> primative window manager and no desktop to the remote system.  A more
> recent server is krfb found in the KDE tree.  This is the basis for so
> called 'desktop sharing' features.  krfb forks the io on running kde
> environment to the remote VNC client and thus depends on a running login
> session.  It can not start a new login session.

RealVNC seems to work well. I suspect you can elide the login
session issue with a suitable script.

> When I mentioned bad performance of XN in an earlier post, I was refering
> to test on a xen domain.   Over a regular network, it is quite snappy, and
> over the internet, it is simple amazing.  It does not seem to be happy on a
> domain system, however.  I've got some more things to try.  But the client
> is gagging and stops responding after a connection has been established and
> a session started.

I'm not sure why it would have problems -- it's just using a TCP
connection, right?


This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an Apple iPod Mini FREE for your judgement on
who ports your project to Linux PPC the best. Sponsored by IBM.
Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php
Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.