Releases
Xen Orchestra is distributed in two ways: as a turnkey virtual appliance (XOA) and from the sources on GitHub. Both contain the same Xen Orchestra, including its two web interfaces (XO 6 and XO 5), the REST API and the backup engine.
Host compatibility list
Xen Orchestra connects to hosts running XCP-ng or XenServer (formerly Citrix Hypervisor), and only those: XO is agent-less and talks to the XAPI toolstack directly, so a Xen hypervisor installed from a regular Linux distribution will not work (see the architecture section).
Installation
Deploying Xen Orchestra takes a few minutes XOA is just another VM.
From source
Xen Orchestra is fully open source: you can build and run it yourself, for free, from its Git repository. This is the method of choice for home labs and evaluation on your own terms.
Configuration
Once Xen Orchestra is installed, you can configure some parameters in the configuration file. Let's see how to do that.
Updates
All updates are pushed through the updater, which is the central piece that keeps your XO Appliance running the latest Xen Orchestra code.
Replace your XOA
Replacing your appliance with a fresh one takes three steps users, ACLs, connected pools, backup jobs, remotes and settings.
Troubleshooting
This page covers the problems you may encounter with your XOA, and how to get out of them.
Architecture
Xen Orchestra (XO) is built as one server and several clients: the two web interfaces (XO 6 and XO 5), the command line client xo-cli, and anything speaking the REST API. The server, xo-server, is the only piece that talks to your infrastructure.