There are quite a few solutions that can act as a GUI for XCP-XAPI.

Note that prior to installing a virtual machine, you'll need to setup your storage repositories.

Can be installed as an “appliance”:

  • Import it in your XenServer installation by doing “xe vm-import filename=xoa3.xva” or import it with XenCenter
  • Start it (“xe vm-start vm=XOA” or with XenCenter). Remember this VM uses DHCP.
  • Then you can go on http://your-vm-ip in your browser.

Import the Virtual Appliance (.xva)

Download the .xva file:

> mkdir -p /var/opt/xen/LocalXVA/
> cd /var/opt/xen/LocalXVA/
> wget dev1.vates.fr/xoa_3.3.xva

Import the VM to the XCP host:

> xe vm-import filename=xoa_3.3.xva

It takes a little time (unzipping the image).

Connect the VM to the Desired Network

Remove the imported virtual interface and network

> xe vif-list vm-name-label=XOA --minimal
> xe vif-destroy uuid=<uuid-of-vif>
> xe network-list

From the last command, identify network to use, and note the network UUID. The import may have created an extra virtual network, if so, you can destroy this using

> xe network-destroy uuid=<uuid_of_unwanted_network>

Now find the uuid of the appliance VM

> xe vm-list name-label=<name_of_your_appliance> --minimal

Connect the VM to your chosen network using

> xe vif-create vm-uuid=<uuid_of_vm> network-uuid=<uuid_of_network> device=0

Run the Appliance on a Selected Host

Now, find the UUID of the host serveur you're willing to run the appliance on:

> xe host-list

Start the appliance on this host without VNC console

> xe vm-param-set uuid=<uuid_of_vm> other-config:disable_pv_vnc=1
> xe vm-start uuid=<uuid_of_vm> on=<name_label_of_host>

To display appliance's (VM) console from your login session on this host server

> xe vm-list params=dom-id name-label=XOA
> /usr/lib/xen-4.1/bin/xenconsole <dom_id>

Login as “root” user (passwd: root).
Issuing an ifconfig command will let you find out the DHCP allocated IP of your VM…

Pay attention to the fact that connecting to the VM's console is a one way ticket. This means that once in the VM's console, you won't be able to get back to the host's console.

In case you're working directly from the server's keyboard and screen (not over ssh), this might lock you out!

Working through a ssh connection to the server will still let you open another session, but if you are to use the server's keyboard and screen you might find it useful to install the “screen” software.

To have a quick overview of what screen can do, have a look at this page: http://www.tecmint.com/screen-command-examples-to-manage-linux-terminals/

Autostart a VM

First activate auto-start option on the pool you need it: the process is to identify the pool on which you want to activate auto-start and modify the auto_poweron parameter.

> xe pool-list
uuid ( RO)                : <YOUR-POOL-UUID>

> xe pool-param-set uuid=<YOUR-POOL-UUID> other-config:auto_poweron=true

Then identify the VM you want to auto-start and also modify it's auto_poweron parameter:

> xe vm-list name-label=XOA
uuid ( RO)           : <YOUR-VM-UUID>

> xe vm-param-set uuid=<YOUR-VM-UUID> other-config:auto_poweron=true