1. XenServer requires that any Linux installs be specially compiled for Xen. This is due to the way that the Xen guys wrote the code for the HyperVisor. From my understanding (and without going through the lkml) the code was not very ‘clean’ and/or did not conform to the kernel coding guidelines. This resulted in the Xen code not being available in the standard kernel that comes with most distributions.
2. Figuring out how to add an ISO repository and actually have its contents come up when installing a new VM is harder than it probably should be on Xen. When trying to figure this out, I found plenty of examples of how to add a new iSCSI/CIFS repository to the XenServer, but nothing on how to set up an ISO repository on the local storage.
3. Apparently there’s also a way of uploading a Windows XP VM, but this was more complicated to get going than adding the local ISO repository.
Due to these problems it was decided to take one of the existing distributions (Debian Lenny) and install a desktop environment and enable Remote Desktop functionality through the use of one of the below listed technologies. After pissing about for two/three days with these protocols I can honestly say that the NX protocol and the binaries available off the NoMachine site are the easiest to configure and the best working solutions. This is kind of disappointing for me, since I would have loved to see a FLOSS solution out do a propriatary one, but as a programmer you have to give credit where credit is due.
When it comes to Remote Desktop functionality for Linux, there are a few options regarding protocols:
* XDMCP – Basically the original X idea of remote displays hooked up to a mainframe. Couldn’t get it to work for the life of me. Also, found a known, unfixed bug whereby enabling remote login makes the gdm listen only to IPv6 addresses
* VNC – Hard to set up and slow
* RDP – See VNC
* NX (FreeNX) – Awesome. Although FreeNX is a real bastard to set up
UPDATE: Found out that Google released their own NX Server called Neatx.