Concepts and feature scope
This reference page explains which component you are working with, what the version numbers mean, and what this version includes. It has no steps to follow. Use it before you rely on a feature, or when you report a problem.
xoa-image-20261022-a280852, package v5.113.2_e281c536-ce40 (Xen Orchestra 5.113.2). Based on the released code; not yet tested on a lab system.Components and addresses
| Component | What it does | Where you reach it |
|---|---|---|
| Hypervisor host or pool | Runs the VMs and provides the XAPI management interface | The host’s management address |
| XO Lite CE | A browser interface served by the host. It deploys and finds the appliance | The host’s HTTPS address |
| XOA-HL appliance | A separate VM that runs xo-server, the XO 5 web interface and Redis | The appliance’s HTTPS address |
To see how these parts fit together, read the architecture and deployment guide. Manage each host or pool with only one supported manager. Read Hosts and pools before you move a connection. Host updates and appliance updates are separate, with their own targets and schedules: see the update guide.
VMs, storage and protection
A VM runs on a host in a pool. A storage repository (SR) stores virtual disks. A VM’s network interface connects to a pool network. Names are only labels: use object IDs in automation.
A snapshot saves the state of a VM at one point in time, on the same storage. A backup copies the data to a separate backup destination (a remote). A snapshot alone does not protect you if that storage is lost, and a successful backup job still needs a restore test.
For more, see the glossary, Storage and networks and Back up and restore a VM.
Version numbers
| Version | What it means |
|---|---|
XO 5.113.2, upstream commit e281c536 | The Xen Orchestra version of the application and web interface. It was chosen on purpose: this is not XO 6 |
xo-server 5.193.1 | The server package version in that same release. It uses a different numbering |
v5.113.2_e281c536-ce40 | The XOA-HL package release, with its set of patches |
xoa-image-20261022-a280852 | The build of the appliance image. It is a separate number: updating the application does not change it |
Note the installed values as described in appliance maintenance. The release matrix lists the versions that shipped together; it does not mean that they passed integration tests. The installation ISO does not fix which appliance image you get: the image is chosen later, when you deploy the appliance.
What this version includes
| Area | In the code of this version | Before you rely on it |
|---|---|---|
| VM power, snapshots, disks and networks | The XO 5 actions and screens are present | The everyday guides are not yet tested on a lab system |
| Users and object permissions (ACLs) | The released build keeps the upstream default plan (OpenSource). The ACL screens are in the code | Check the installed interface, and test in a separate session signed in as a normal user |
| Full backup and restore | An NFS procedure is documented, based on the code | A real backup and an isolated restore are not yet tested |
| Appliance updates | XOA-HL update API, stable and testing channels, and schedules you can set | Follow the update guide for your release |
| Hub, the Vates XOA section, backup proxies and XOSTOR menus | A menu patch in this package hides these entries | A hidden menu does not make a supported feature. It does not prove that the matching API is gone either |
This package release declares 16 patches. They do not mean that every upstream option has been tested. Vates subscription plans, commercial support and XO 6 interfaces do not apply to this package. Before you rely on a feature, check Users and permissions and the guide for that task.
Related pages
- Service settings: the xo-server configuration files.
- Automation with xo-cli: read inventory from the command line with a short-lived token.
- Configuration export: save the settings and records of the web interface.
- xoa-hl and build-xoa-hl: how the package is made. Product builds run only in CI.
When you suggest a change to this documentation, include the image and package versions that you use.
Sources
- Versions, patches and build: upstream XO version (
UPSTREAM_XO), list of patches, menu patch that hides entries, package definition, xo-server package version, web interface build.