Find the current memory setting for dom0 – XenServer 6.5

I'd really like to say that you should avoid using any G3 ProLiant in 2013... especially for virtualization... Anywho, the XenServer HCL does not include the G3 ProLiants. You need a 64-bit CPU per the XenServer software requirements.

One or more 64-bit x86 CPU(s), 1.5 GHz minimum, 2 GHz or faster multicore CPU recommended

The HP ProLiant DL360 G3 systems were introduced in 2003 and went end-of-life around 2005. These are Pentium 4 Xeon processors. There are only two parallel SCSI drives. They're 32-bit only. At this juncture ANY modern computer will perform better (even a desktop).

Ok, so eventually I found the answer to the problem I was facing. It turned out I must have had a corrupt install of XenServer, and after downloading the .iso again and reinstalling, I found that by executing xe template-list output a long list of useful templates.

The next hurdle I had to cross was running a VM in PV mode, as the tower unit I was using did not support HVM. It actually turns out that all 32-bit Linux Distributions are compatible out of the box with PV (as a general rule of thumb, anything old is compatible eg. Ubuntu 12.04 and 10.Whatever 32-bit; Debian Squeeze and Wheezy 32-bit), and so you are able to launch a VM in exactly the same way using the following commands:

xe sr-list outputs the list of storage repositories; the storage repository 'local storage' of type 'ext' provided for me a location where I could store the disks of each VM respectively.

xe template-list outputs the list of templates accessible on the XenServer host.

xe vm-install template=<template> new-name-label=<name_for_vm> sr-uuid=<storage_repository_uuid> 'installs' a VM based off the template onto the machine, however no actual installation occurs at this point. This then outputs the UUID of the VM in the console. By executing the command xe vm-list you can see a list of VMs which are currently installed on the host, displaying UUIDs for each and their current state.

xe network-list bridge=xenbr0 --minimal outputs the UUID of the bridge xenbr0 which is the default bridge for a fresh install of XenServer. If you are using a different bridge or want to attach the VM to a different adapter, then you can define a different name in place (however you need to make sure you've created one first :P).

xe vif-create vm-uuid=<vm_uuid> network-uuid=<network_uuid> mac=random device=0 creates a virtual network interface for the VM with a random MAC address.

xe vm-param-set uuid=<vm_uuid> other-config:install-repository=<http://server/redhat/5.0> defines the install location for the net installer of the OS. Personally, I found that by searching for mirrors on the internet for the specific flavour of OS, I was able to find the mirror. Then instead of guessing what the install repository was, I searched through the repository until I found the folder marked xen with the file vmlinuz contained within. I copied this address in, and then ran xe vm-start uuid=<vm_uuid> receiving an error that the URL was incorrect. Within this URL, some of it will be repeated so remove the repeated part and run the 'xe vm-param-set ...' command again. For Ubuntu 12.04, the mirror I used was http://http://archive.ubuntu.com/ubuntu/dists/precise-updates/.

xe vm-start uuid=<vm_uuid> will power on the VM and it will launch. This process will take a fair amount of time as it actually downloads the installer, but it should in practise only take around 2 minutes.

Congratulations! You've started your own VM running on your rubbish non-HVM tower unit, however the next step is to actually connect to it.

In order to connect, run the command xe console uuid=<vm_uuid>. This will then bring up a dialogue saying that you've connected to the console of your VM. The first time I tried this, I received no sort of output, and was perplexed, however a swift tap of the enter key sorted it out, and the setup began.

If you need any more help with setting up your VMs, then there is a great document on Citrix's website http://docs.vmd.citrix.com/XenServer/5.0.0/1.0/en_gb/guest.html that explains the process fairly thoroughly (but also not very simply either).

I sincerely hope that this has cleared up the process of launching a VM on a non HVM machine, and that this actually becomes fairly useful.

Good luck trying to get the installer to connect to the internet... (might just be me running in VirtualBox), Oli.