Finally just finished our migration from VMware to XCP-NG.

VMs - 34 mix windows server and ubuntu linux.
Pools - 3
Host - 6
Dell R660 - 2
Dell R640 - 4

@rzr Installed latest update and no issues to report. I dont hvae any 2tb+ drives in my vms. converting from vhd to qcow2 and backups all working.

@rzr

installed updates will report back.

Update - I had migrated vms back over to vhd prior to update release. I have migrated 2 vms back over to qcow2 and the initial backup ran successfull. Ran a second delta backup and that as well was successful with out issues. Backups happen very quickly now. But it appears the % and progress bar are working.

When CBT is enabled on the vm vdi. They show up as needing to be coalesced. VMs without CBT enabled the vdis are coalesced.

Will continue to monitor.

Once the coalesence hits 2 for the vm. The vm is skipped form future backups until cleared. (shutting down the vm will allow the coalescence to happen.
2026-04-23T19_52_34.694Z - backup NG.txt

@olivierlambert Created new topic.

@rzr

Updated my to AMD Ryzen host in my home lab. No issues with update will monitor and report back any issues.

@julienXOvates

Ok that was in xo from sources and yes issue is fixed...

Confirmed is working in XOA in 6.4.1

While this project is more for myself it is open to others to use. Please use at your own risk. As always review the script before using in a production environment. Please leave any feedback or suggestions. https://github.com/acebmxer/install_xen_orchestra/
https://forums.pozzatech.com - You can read more about this project and other things over in my personal forums.

Automated installation and management of Xen Orchestra from source.

Update 5/15/26 - This update only applies to anyone using older version of script. See note. Also added option to Adjust Xen Orchestra Memory Allocation. It will look at the system memory and suggest setting for XO based off the official documentation.

⚠️ Upgrading from an earlier version of this script? Read this first.
This version bumps the config schema to v2 (adds PUBLIC_URL and ENCRYPT_REDIS_CREDENTIALS) and corrects two config.toml generation bugs. Your xo-config.cfg is migrated automatically and non-destructively, but the corrected /etc/xo-server/config.toml is only written by --reconfigure.

Run --reconfigure once before resuming normal updates:

./install-xen-orchestra.sh --reconfigure
This regenerates config.toml with the fixes (your old file is backed up first; data in /var/lib/xo-server is untouched). It is strongly recommended if you set both REDIRECT_TO_HTTPS=true and REVERSE_PROXY_TRUST — that combination previously produced a duplicate [http] section and silently dropped one of the settings.

Afterwards, run --update as normal for routine XO updates — --update does not need to be preceded by --reconfigure again.

Available Functions

Function	CLI Flag	Description
Install	--install	Fresh install of Xen Orchestra
Update	--update	Update existing installation (with backup)
Restore	--restore	Restore from a previous backup
Rebuild	--rebuild	Fresh clone + clean build, preserves settings
Reconfigure	--reconfigure	Apply config changes without rebuilding
XO Proxy	--proxy	Deploy XO Proxy to a Xen pool master
Edit Config	(menu only)	Open xo-config.cfg in your preferred editor
Rename Config	(menu only)	Rename sample-xo-config.cfg to xo-config.cfg

Running without flags launches an interactive menu. All flags also work directly:

./install-xen-orchestra.sh           # interactive menu
./install-xen-orchestra.sh --update  # run update directly
./install-xen-orchestra.sh --help    # show all options

Interactive Menu

Running the script with no arguments opens a two-column menu with keyboard navigation:

  ╔══════════════════════════════════════════════════════════════════════════════════╗
  ║              Install Xen Orchestra from Sources Setup and Update                 ║
  ╚══════════════════════════════════════════════════════════════════════════════════╝

                        Current Script Commit : 693f4 (Branch: main)
                        Master Script Commit  : 693f4 (Branch: main)
                        Current XO Commit     : a1b2c (Branch: master)
                        Master XO Commit      : d4e5f (Branch: master)
                        Current Node          : v24.15.0

  ──────────────────────────────────────────────────────────────────────────────────

  ▸ [✓] Install Xen Orchestra                   [ ] Reconfigure Xen Orchestra
    [ ] Update Xen Orchestra                    [ ] Rebuild Xen Orchestra
    [ ] Rename Sample-xo-config.cfg             [ ] Edit xo-config.cfg
    [ ] Install XO Proxy                        [ ]  Restore Backup
                         [ ] Adjust Xen Orchestra Memory Allocation

  ──────────────────────────────────────────────────────────────────────────────────

  Selected: 1

  ↑↓←→ Navigate   SPACE Select/Deselect   ENTER Confirm   Q Quit

Select one or more items with SPACE, then press ENTER to run them.

Quick Start

git clone https://github.com/acebmxer/install_xen_orchestra.git
cd install_xen_orchestra
cp sample-xo-config.cfg xo-config.cfg
nano xo-config.cfg   # edit to your liking
./install-xen-orchestra.sh

Do NOT run with sudo. Run as a normal user with sudo privileges — the script handles sudo internally.

If xo-config.cfg doesn't exist, it will be created automatically from the sample.

Configuration

All settings live in xo-config.cfg. See sample-xo-config.cfg for full documentation of every option.

Key settings:

Option	Default	Description
HTTP_PORT	80	HTTP port
HTTPS_PORT	443	HTTPS port
INSTALL_DIR	/opt/xen-orchestra	Installation directory
GIT_BRANCH	master	Git branch or tag
NODE_VERSION	24.15.0	Node.js version
SERVICE_USER	xo-service	Service user (set to root for VMware V2V import)
BACKUP_KEEP	5	Number of backups to retain
BIND_ADDRESS	0.0.0.0	Bind address
REVERSE_PROXY_TRUST	false	Trust X-Forwarded headers from proxy IP

Note on BACKUP_KEEP rotation: The retention policy only applies to backups created by the current version of the script. Backups made by older script versions may use a different naming convention and will not be counted or pruned by the rotation logic. If you are upgrading from an older version, manually review your backup directory (BACKUP_DIR in config, default /var/lib/xo-backups) and remove any legacy-named archives you no longer need.

Default Credentials

After installation, access the web interface at https://your-server-ip.

• Username: admin@admin.net
• Password: admin

Change the default password immediately after first login.

Supported Operating Systems

• Debian 10/11/12/13
• Ubuntu (all supported versions)
• RHEL / CentOS / AlmaLinux / Rocky
• Fedora

Running Task Detection (Update Safety)

Before applying an update, the script queries the Xen Orchestra REST API for active tasks (e.g. running backups, VM exports). If any are found, the update is aborted to prevent data loss or corruption.

Authentication

Only admin-level XO accounts can access the REST API. Authentication is resolved in priority order:

Priority	Method	Source
1	Auth token	XO_TASK_CHECK_TOKEN in xo-config.cfg
2	Credentials	XO_TASK_CHECK_USER / XO_TASK_CHECK_PASS in xo-config.cfg
3	Interactive	Prompted at runtime (press Enter to skip)

Recommended: Dedicated XO Account

It is recommended to create a dedicated XO web UI account solely for the task check (e.g. task-checker@local.net). This account:

• Must have Admin privileges (required by the REST API)
• Exists only within the XO web interface — no shell access, SSH keys, or OS-level permissions are needed
• Provides a clear audit trail separate from personal accounts
• Prevents shared credentials from being used for unrelated actions

You are free to use any admin account you choose, but a dedicated account is the safest approach.

Using an Auth Token (Recommended)

Tokens are more secure than storing a password — they can be revoked independently and expire after 30 days by default.

1. Log into the XO web UI with the dedicated account
2. Generate a token:

   curl -X POST -u 'task-checker@local.net:yourpassword' \
     https://localhost/rest/v0/users/me/authentication_tokens -k
   

3. Copy the id field from the response
4. Add to xo-config.cfg:

   XO_TASK_CHECK_TOKEN=UlTBEnFeL12XocK-7Qx-DKvOYbPn0eG7Z2oMvOniNjg
   

Using Credentials

Alternatively, store the account credentials directly:

XO_TASK_CHECK_USER=task-checker@local.net
XO_TASK_CHECK_PASS=changeme

If neither token nor credentials are configured, the script will prompt interactively during each update.

Environment Variables

Variable	Description
XO_DEBUG=1	Enable debug mode (set -x)
XO_NO_SELF_UPDATE=1	Skip automatic script self-update

Troubleshooting

Check service logs:

sudo journalctl -u xo-server -n 50

If the build is broken, rebuild (takes a backup first):

./install-xen-orchestra.sh --rebuild

Build fails with OOM / out-of-memory error

The Yarn build is memory-intensive. On hosts with less than 2 GB RAM the Node.js process can be killed by the kernel OOM killer mid-build, leaving an incomplete install.

Add or increase swap to give the build room:

sudo fallocate -l 2G /swapfile
sudo chmod 600 /swapfile
sudo mkswap /swapfile
sudo swapon /swapfile

Re-run the install or --rebuild after the swap is active. To make it permanent across reboots, add /swapfile none swap sw 0 0 to /etc/fstab.

NodeSource GPG key failure (air-gapped / offline hosts)

On hosts without internet access (or with strict egress firewall rules) the NodeSource repository setup script fails because it cannot reach keyserver.ubuntu.com or deb.nodesource.com.

Option A — pre-download and import the key manually, then copy the .deb/.rpm packages to the host.

Option B — set NODE_VERSION to a specific patch version (e.g. 24.15.0) in xo-config.cfg. The script will then download a pre-built binary directly from nodejs.org instead of using the NodeSource package repository.

git reports "dubious ownership" and exits

Recent versions of Git refuse to operate on a repository owned by a different user than the one running the command. This can happen when sudo is used inconsistently or when the install directory was created by root but the script is run as a normal user.

Fix it by resetting ownership to match your SERVICE_USER:

sudo chown -R xo-service:xo-service /opt/xen-orchestra

Replace xo-service with the value of SERVICE_USER in xo-config.cfg. Re-running the script afterwards will resolve the rest.

RedHat / Rocky / AlmaLinux: SELinux denials or systemd capability errors

On SELinux-enforcing systems the xo-server service may fail to bind ports or access network resources. Check for AVC denials:

sudo ausearch -m avc -ts recent | grep xo-server

If denials are present, generate and apply a local policy module:

sudo ausearch -m avc -ts recent | audit2allow -M xo-server-local
sudo semodule -i xo-server-local.pp

Alternatively, set the service to permissive mode while investigating:

sudo semanage permissive -a xo_server_t

audit2allow and semanage are provided by the policycoreutils-python-utils package on RHEL/Rocky/Alma.

License

This project is licensed under the MIT License. Xen Orchestra itself is licensed under AGPL-3.0.

Credits

• Xen Orchestra by Vates
• Installation Documentation

Confirm commit 1a7b5 backups completed successfully.

@simonp

[info] Updating Xen Orchestra from 'cb85e44ae' to 'eed3d72f7'

First log is from automatic schedule before latest update.
2026-02-17T18_00_00.012Z - backup NG.txt

latest log after update. Backup completed successfully.
2026-02-17T18_22_52.199Z - backup NG.txt

Updated AMD Ryzen pool at home and update two Intel Dell r660 and r640 pools at work. No issues to report back.

@simonp

With node = 22.22.3

with node = 24.15.0

❯ sudo journalctl -u xo-server -n 75
May 19 10:26:15 xo-ce xo-server[77015]: 2026-05-19T10:26:15.516Z xo:plugin INFO register sdn-controller
May 19 10:26:15 xo-ce xo-server[77015]: 2026-05-19T10:26:15.517Z xo:plugin INFO register test-plugin
May 19 10:26:15 xo-ce xo-server[77015]: 2026-05-19T10:26:15.517Z xo:plugin INFO register transport-email
May 19 10:26:15 xo-ce xo-server[77015]: 2026-05-19T10:26:15.518Z xo:plugin INFO register transport-icinga2
May 19 10:26:15 xo-ce xo-server[77015]: 2026-05-19T10:26:15.518Z xo:plugin INFO register transport-nagios
May 19 10:26:15 xo-ce xo-server[77015]: 2026-05-19T10:26:15.519Z xo:plugin INFO register transport-slack
May 19 10:26:15 xo-ce xo-server[77015]: 2026-05-19T10:26:15.519Z xo:plugin INFO register transport-xmpp
May 19 10:26:15 xo-ce xo-server[77015]: 2026-05-19T10:26:15.519Z xo:plugin INFO register usage-report
May 19 10:26:15 xo-ce xo-server[77015]: 2026-05-19T10:26:15.520Z xo:plugin INFO register web-hooks
May 19 10:26:15 xo-ce xo-server[77015]: 2026-05-19T10:26:15.890Z xo:xo-server-openmetrics INFO Plugin initialized
May 19 10:26:15 xo-ce xo-server[77015]: 2026-05-19T10:26:15.936Z xo:plugin INFO successfully register auth-github
May 19 10:26:15 xo-ce xo-server[77015]: 2026-05-19T10:26:15.936Z xo:plugin INFO successfully register auth-google
May 19 10:26:15 xo-ce xo-server[77015]: 2026-05-19T10:26:15.936Z xo:plugin INFO successfully register auth-oidc
May 19 10:26:15 xo-ce xo-server[77015]: 2026-05-19T10:26:15.936Z xo:plugin INFO successfully register auth-saml
May 19 10:26:15 xo-ce xo-server[77015]: 2026-05-19T10:26:15.936Z xo:plugin INFO successfully register auth-ldap
May 19 10:26:15 xo-ce xo-server[77015]: 2026-05-19T10:26:15.936Z xo:plugin INFO successfully register netbox
May 19 10:26:15 xo-ce xo-server[77015]: 2026-05-19T10:26:15.936Z xo:plugin INFO successfully register test-plugin
May 19 10:26:15 xo-ce xo-server[77015]: 2026-05-19T10:26:15.936Z xo:plugin INFO successfully register transport-icinga2
May 19 10:26:15 xo-ce xo-server[77015]: 2026-05-19T10:26:15.936Z xo:plugin INFO successfully register transport-slack
May 19 10:26:15 xo-ce xo-server[77015]: 2026-05-19T10:26:15.936Z xo:plugin INFO successfully register transport-nagios
May 19 10:26:15 xo-ce xo-server[77015]: 2026-05-19T10:26:15.936Z xo:plugin INFO successfully register transport-xmpp
May 19 10:26:15 xo-ce xo-server[77015]: 2026-05-19T10:26:15.936Z xo:plugin INFO successfully register usage-report
May 19 10:26:15 xo-ce xo-server[77015]: 2026-05-19T10:26:15.936Z xo:xo-server-openmetrics INFO Starting OpenMetrics server { port: 9004, bindAddress: 'localhost' }
May 19 10:26:15 xo-ce xo-server[77015]: 2026-05-19T10:26:15.942Z xo:plugin INFO successfully register web-hooks
May 19 10:26:15 xo-ce xo-server[77015]: 2026-05-19T10:26:15.942Z xo:plugin INFO successfully register backup-reports
May 19 10:26:15 xo-ce xo-server[77015]: 2026-05-19T10:26:15.942Z xo:plugin INFO successfully register load-balancer
May 19 10:26:15 xo-ce xo-server[77015]: 2026-05-19T10:26:15.942Z xo:plugin INFO successfully register transport-email
May 19 10:26:15 xo-ce xo-server[77015]: 2026-05-19T10:26:15.942Z xo:plugin INFO successfully register perf-alert
May 19 10:26:15 xo-ce xo-server[77015]: 2026-05-19T10:26:15.952Z xo:plugin INFO successfully register audit
May 19 10:26:16 xo-ce xo-server[77015]: 2026-05-19T10:26:16.020Z xo:plugin INFO successfully register sdn-controller
May 19 10:26:16 xo-ce xo-server[77015]: 2026-05-19T10:26:16.034Z xo:plugin INFO successfully register openmetrics
May 19 10:26:16 xo-ce xo-server[77015]: 2026-05-19T10:26:16.035Z xo:main INFO Setting up /v5 → /opt/xen-orchestra/packages/xo-web/dist
May 19 10:26:16 xo-ce xo-server[77015]: 2026-05-19T10:26:16.035Z xo:main INFO Setting up /v6 → /opt/xen-orchestra/@xen-orchestra/web/dist
May 19 10:26:16 xo-ce xo-server[77015]: 2026-05-19T10:26:16.035Z xo:main INFO Setting up / → /opt/xen-orchestra/@xen-orchestra/web/dist
May 19 10:26:16 xo-ce sudo[77059]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=999)
May 19 10:26:16 xo-ce sudo[77059]: xo-service :  PWD=/opt/xen-orchestra/packages/xo-server ; USER=root ; COMMAND=/usr/bin/mount -o  -t nfs 10.100.2.23:/volume1/Backups /run/xo-server/mounts/a5e54e04-d7e4-48cb-bafc-b2f306d39679
May 19 10:26:16 xo-ce sudo[77060]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=999)
May 19 10:26:16 xo-ce sudo[77060]: xo-service :  PWD=/opt/xen-orchestra/packages/xo-server ; USER=root ; COMMAND=/usr/bin/mount -o  -t nfs 10.100.2.23:/volume1/backup /run/xo-server/mounts/3ba9eed2-55f1-4760-ac08-655c252aa316
May 19 10:26:16 xo-ce sudo[77059]: pam_unix(sudo:session): session closed for user root
May 19 10:26:16 xo-ce sudo[77060]: pam_unix(sudo:session): session closed for user root
May 19 10:26:30 xo-ce xo-server[77015]: 2026-05-19T10:26:30.018Z xo:rest-api:error-handler INFO [POST] /events/2203cd6f-1023-456b-9cf0-338f35f67be9/subscriptions (401)
May 19 10:26:30 xo-ce xo-server[77015]: 2026-05-19T10:26:30.030Z xo:rest-api:error-handler INFO duplicates of the previous log were hidden { nDuplicates: 2 }
May 19 10:26:30 xo-ce xo-server[77015]: 2026-05-19T10:26:30.030Z xo:rest-api:error-handler INFO [GET] /srs (401)
May 19 10:26:30 xo-ce xo-server[77015]: 2026-05-19T10:26:30.031Z xo:rest-api:error-handler INFO [GET] /alarms (401)
May 19 10:26:31 xo-ce xo-server[77015]: 2026-05-19T10:26:31.900Z xo:rest-api:error-handler INFO [GET] /srs (401)
May 19 10:26:35 xo-ce xo-server[77015]: 2026-05-19T10:26:35.617Z xo:rest-api:error-handler INFO [GET] /tasks (401)
May 19 10:26:36 xo-ce xo-server[77015]: 2026-05-19T10:26:36.842Z xo:rest-api:error-handler INFO [GET] /backup-jobs (401)
May 19 10:26:36 xo-ce xo-server[77015]: 2026-05-19T10:26:36.845Z xo:rest-api:error-handler INFO [DELETE] /events/62644a6b-b513-42be-97a4-8fd478f995a6/subscriptions/alarm (401)
May 19 10:26:47 xo-ce xo-server[77015]: 2026-05-19T10:26:47.014Z xo:rest-api:error-handler INFO [POST] /events/126a3f5b-672e-418b-b632-28aa7f83b3fd/subscriptions (401)
May 19 10:26:52 xo-ce xo-server[77015]: 2026-05-19T10:26:52.622Z xo:rest-api:error-handler INFO [GET] /dashboard (401)
May 19 10:26:52 xo-ce xo-server[77015]: 2026-05-19T10:26:52.643Z xo:rest-api:error-handler INFO [GET] /vm-controllers (401)
May 19 10:26:54 xo-ce xo-server[77015]: 2026-05-19T10:26:54.260Z xo:rest-api:error-handler INFO [GET] /hosts (401)
May 19 10:26:54 xo-ce xo-server[77015]: 2026-05-19T10:26:54.261Z xo:rest-api:error-handler INFO [GET] /tasks (401)
May 19 10:26:56 xo-ce xo-server[77015]: 2026-05-19T10:26:56.101Z xo:rest-api:error-handler INFO [GET] /hosts (401)
May 19 10:26:57 xo-ce xo-server[77015]: 2026-05-19T10:26:57.546Z xo:rest-api:error-handler INFO [POST] /events/bb27f28f-7660-4ce5-a31c-fcb9b64fdb9f/subscriptions (401)
May 19 10:26:57 xo-ce xo-server[77015]: 2026-05-19T10:26:57.587Z xo:rest-api:error-handler INFO [GET] /vdis (401)
May 19 10:26:59 xo-ce xo-server[77015]: (node:77015) [DEP0060] DeprecationWarning: The `util._extend` API is deprecated. Please use Object.assign() instead.
May 19 10:26:59 xo-ce xo-server[77015]: (Use `node --trace-deprecation ...` to show where the warning was created)
May 19 10:26:59 xo-ce xo-server[77015]: 2026-05-19T10:26:59.509Z xo:xo-server WARN Node warning {
May 19 10:26:59 xo-ce xo-server[77015]:   error: DeprecationWarning: The `util._extend` API is deprecated. Please use Object.assign() instead.
May 19 10:26:59 xo-ce xo-server[77015]:       at ProxyServer.ws (/opt/xen-orchestra/node_modules/http-proxy/lib/http-proxy/index.js:50:26)
May 19 10:26:59 xo-ce xo-server[77015]:       at app.<anonymous> (file:///opt/xen-orchestra/packages/xo-server/src/index.mjs:697:15)
May 19 10:26:59 xo-ce xo-server[77015]:       at app.emit (node:events:509:28)
May 19 10:26:59 xo-ce xo-server[77015]:       at app.emit (/opt/xen-orchestra/@xen-orchestra/log/configure.js:52:17)
May 19 10:26:59 xo-ce xo-server[77015]:       at Server.<anonymous> (file:///opt/xen-orchestra/packages/xo-server/src/index.mjs:977:13)
May 19 10:26:59 xo-ce xo-server[77015]:       at Server.emit (node:events:521:24)
May 19 10:26:59 xo-ce xo-server[77015]:       at Server.patchedEmit [as emit] (/opt/xen-orchestra/@xen-orchestra/log/configure.js:52:17)
May 19 10:26:59 xo-ce xo-server[77015]:       at onParserExecuteCommon (node:_http_server:987:14)
May 19 10:26:59 xo-ce xo-server[77015]:       at onParserExecute (node:_http_server:891:3) {
May 19 10:26:59 xo-ce xo-server[77015]:     code: 'DEP0060'
May 19 10:26:59 xo-ce xo-server[77015]:   }
May 19 10:26:59 xo-ce xo-server[77015]: }
May 19 10:27:21 xo-ce xo-server[77015]: 2026-05-19T10:27:21.248Z xo:rest-api:error-handler INFO [GET] /tasks (401)
May 19 10:27:21 xo-ce xo-server[77015]: 2026-05-19T10:27:21.251Z xo:rest-api:error-handler INFO [GET] /srs (401)
May 19 10:29:55 xo-ce xo-server[77015]: 2026-05-19T10:29:55.798Z xo:rest-api:error-handler INFO [DELETE] /events/8c7df237-3069-4c8e-8b63-d2b7a1233799/subscriptions/SR (401)
lines 4-75/75 (END)

Back to node 22.22.3

❯ sudo journalctl -u xo-server -n 75
May 19 10:44:30 xo-ce xo-server[79847]: 2026-05-19T10:44:30.721Z xo:main INFO Setting up /robots.txt → /opt/xen-orchestra/packages/xo-server/robots.txt
May 19 10:44:30 xo-ce xo-server[79847]: 2026-05-19T10:44:30.796Z xo:plugin INFO register audit
May 19 10:44:30 xo-ce xo-server[79847]: 2026-05-19T10:44:30.796Z xo:plugin INFO register auth-github
May 19 10:44:30 xo-ce xo-server[79847]: 2026-05-19T10:44:30.796Z xo:plugin INFO register auth-google
May 19 10:44:30 xo-ce xo-server[79847]: 2026-05-19T10:44:30.797Z xo:plugin INFO register auth-ldap
May 19 10:44:30 xo-ce xo-server[79847]: 2026-05-19T10:44:30.797Z xo:plugin INFO register auth-oidc
May 19 10:44:30 xo-ce xo-server[79847]: 2026-05-19T10:44:30.797Z xo:plugin INFO register auth-saml
May 19 10:44:30 xo-ce xo-server[79847]: 2026-05-19T10:44:30.797Z xo:plugin INFO register backup-reports
May 19 10:44:30 xo-ce xo-server[79847]: 2026-05-19T10:44:30.797Z xo:plugin INFO register load-balancer
May 19 10:44:30 xo-ce xo-server[79847]: 2026-05-19T10:44:30.797Z xo:plugin INFO register netbox
May 19 10:44:30 xo-ce xo-server[79847]: 2026-05-19T10:44:30.797Z xo:plugin INFO register openmetrics
May 19 10:44:30 xo-ce xo-server[79847]: 2026-05-19T10:44:30.798Z xo:plugin INFO register perf-alert
May 19 10:44:30 xo-ce xo-server[79847]: 2026-05-19T10:44:30.798Z xo:plugin INFO register sdn-controller
May 19 10:44:30 xo-ce xo-server[79847]: 2026-05-19T10:44:30.798Z xo:plugin INFO register test-plugin
May 19 10:44:30 xo-ce xo-server[79847]: 2026-05-19T10:44:30.798Z xo:plugin INFO register transport-email
May 19 10:44:30 xo-ce xo-server[79847]: 2026-05-19T10:44:30.798Z xo:plugin INFO register transport-icinga2
May 19 10:44:30 xo-ce xo-server[79847]: 2026-05-19T10:44:30.798Z xo:plugin INFO register transport-nagios
May 19 10:44:30 xo-ce xo-server[79847]: 2026-05-19T10:44:30.799Z xo:plugin INFO register transport-slack
May 19 10:44:30 xo-ce xo-server[79847]: 2026-05-19T10:44:30.799Z xo:plugin INFO register transport-xmpp
May 19 10:44:30 xo-ce xo-server[79847]: 2026-05-19T10:44:30.799Z xo:plugin INFO register usage-report
May 19 10:44:30 xo-ce xo-server[79847]: 2026-05-19T10:44:30.799Z xo:plugin INFO register web-hooks
May 19 10:44:31 xo-ce xo-server[79847]: 2026-05-19T10:44:31.184Z xo:xo-server-openmetrics INFO Plugin initialized
May 19 10:44:31 xo-ce xo-server[79847]: 2026-05-19T10:44:31.232Z xo:plugin INFO successfully register auth-google
May 19 10:44:31 xo-ce xo-server[79847]: 2026-05-19T10:44:31.232Z xo:plugin INFO successfully register auth-github
May 19 10:44:31 xo-ce xo-server[79847]: 2026-05-19T10:44:31.232Z xo:plugin INFO successfully register auth-ldap
May 19 10:44:31 xo-ce xo-server[79847]: 2026-05-19T10:44:31.232Z xo:plugin INFO successfully register auth-oidc
May 19 10:44:31 xo-ce xo-server[79847]: 2026-05-19T10:44:31.232Z xo:plugin INFO successfully register netbox
May 19 10:44:31 xo-ce xo-server[79847]: 2026-05-19T10:44:31.232Z xo:plugin INFO successfully register test-plugin
May 19 10:44:31 xo-ce xo-server[79847]: 2026-05-19T10:44:31.232Z xo:plugin INFO successfully register transport-icinga2
May 19 10:44:31 xo-ce xo-server[79847]: 2026-05-19T10:44:31.233Z xo:plugin INFO successfully register transport-nagios
May 19 10:44:31 xo-ce xo-server[79847]: 2026-05-19T10:44:31.233Z xo:plugin INFO successfully register transport-xmpp
May 19 10:44:31 xo-ce xo-server[79847]: 2026-05-19T10:44:31.233Z xo:plugin INFO successfully register transport-slack
May 19 10:44:31 xo-ce xo-server[79847]: 2026-05-19T10:44:31.233Z xo:plugin INFO successfully register usage-report
May 19 10:44:31 xo-ce xo-server[79847]: 2026-05-19T10:44:31.233Z xo:plugin INFO successfully register web-hooks
May 19 10:44:31 xo-ce xo-server[79847]: 2026-05-19T10:44:31.233Z xo:plugin INFO successfully register auth-saml
May 19 10:44:31 xo-ce xo-server[79847]: 2026-05-19T10:44:31.233Z xo:xo-server-openmetrics INFO Starting OpenMetrics server { port: 9004, bindAddress: 'localhost' }
May 19 10:44:31 xo-ce xo-server[79847]: 2026-05-19T10:44:31.239Z xo:plugin INFO successfully register backup-reports
May 19 10:44:31 xo-ce xo-server[79847]: 2026-05-19T10:44:31.239Z xo:plugin INFO successfully register load-balancer
May 19 10:44:31 xo-ce xo-server[79847]: 2026-05-19T10:44:31.239Z xo:plugin INFO successfully register transport-email
May 19 10:44:31 xo-ce xo-server[79847]: 2026-05-19T10:44:31.239Z xo:plugin INFO successfully register perf-alert
May 19 10:44:31 xo-ce xo-server[79847]: 2026-05-19T10:44:31.321Z xo:plugin INFO successfully register audit
May 19 10:44:31 xo-ce xo-server[79847]: 2026-05-19T10:44:31.327Z xo:plugin INFO successfully register openmetrics
May 19 10:44:31 xo-ce xo-server[79847]: 2026-05-19T10:44:31.334Z xo:plugin INFO successfully register sdn-controller
May 19 10:44:31 xo-ce xo-server[79847]: 2026-05-19T10:44:31.336Z xo:main INFO Setting up /v5 → /opt/xen-orchestra/packages/xo-web/dist
May 19 10:44:31 xo-ce xo-server[79847]: 2026-05-19T10:44:31.336Z xo:main INFO Setting up /v6 → /opt/xen-orchestra/@xen-orchestra/web/dist
May 19 10:44:31 xo-ce xo-server[79847]: 2026-05-19T10:44:31.336Z xo:main INFO Setting up / → /opt/xen-orchestra/@xen-orchestra/web/dist
May 19 10:44:36 xo-ce xo-server[79847]: (node:79847) [DEP0060] DeprecationWarning: The `util._extend` API is deprecated. Please use Object.assign() instead.
May 19 10:44:36 xo-ce xo-server[79847]: (Use `node --trace-deprecation ...` to show where the warning was created)
May 19 10:44:36 xo-ce xo-server[79847]: 2026-05-19T10:44:36.542Z xo:xo-server WARN Node warning {
May 19 10:44:36 xo-ce xo-server[79847]:   error: DeprecationWarning: The `util._extend` API is deprecated. Please use Object.assign() instead.
May 19 10:44:36 xo-ce xo-server[79847]:       at ProxyServer.ws (/opt/xen-orchestra/node_modules/http-proxy/lib/http-proxy/index.js:50:26)
May 19 10:44:36 xo-ce xo-server[79847]:       at Function.<anonymous> (file:///opt/xen-orchestra/packages/xo-server/src/index.mjs:697:15)
May 19 10:44:36 xo-ce xo-server[79847]:       at Function.emit (node:events:519:28)
May 19 10:44:36 xo-ce xo-server[79847]:       at Function.emit (/opt/xen-orchestra/@xen-orchestra/log/configure.js:52:17)
May 19 10:44:36 xo-ce xo-server[79847]:       at Server.<anonymous> (file:///opt/xen-orchestra/packages/xo-server/src/index.mjs:977:13)
May 19 10:44:36 xo-ce xo-server[79847]:       at Server.emit (node:events:531:35)
May 19 10:44:36 xo-ce xo-server[79847]:       at Server.patchedEmit [as emit] (/opt/xen-orchestra/@xen-orchestra/log/configure.js:52:17)
May 19 10:44:36 xo-ce xo-server[79847]:       at onParserExecuteCommon (node:_http_server:977:14)
May 19 10:44:36 xo-ce xo-server[79847]:       at onParserExecute (node:_http_server:881:3) {
May 19 10:44:36 xo-ce xo-server[79847]:     code: 'DEP0060'
May 19 10:44:36 xo-ce xo-server[79847]:   }
May 19 10:44:36 xo-ce xo-server[79847]: }
May 19 10:44:42 xo-ce xo-server[79847]: 2026-05-19T10:44:42.247Z xo:rest-api:error-handler INFO [GET] /tasks (401)
May 19 10:44:47 xo-ce xo-server[79847]: 2026-05-19T10:44:47.602Z xo:rest-api:error-handler INFO [DELETE] /events/cd7bcc9d-15ba-4ce0-b31e-5d8798a4ff2e/subscriptions>
May 19 10:44:50 xo-ce xo-server[79847]: 2026-05-19T10:44:50.643Z xo:rest-api:error-handler INFO [GET] /vms/ff7214ce-de09-fe31-bfe9-5994af558ddb/alarms (401)
May 19 10:44:50 xo-ce sudo[79915]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=999)
May 19 10:44:50 xo-ce sudo[79915]: xo-service :  PWD=/opt/xen-orchestra/packages/xo-server ; USER=root ; COMMAND=/usr/bin/mount -o  -t nfs 10.100.2.23:/volume1/bac>
May 19 10:44:50 xo-ce sudo[79916]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=999)
May 19 10:44:50 xo-ce sudo[79916]: xo-service :  PWD=/opt/xen-orchestra/packages/xo-server ; USER=root ; COMMAND=/usr/bin/mount -o  -t nfs 10.100.2.23:/volume1/Bac>
May 19 10:44:50 xo-ce sudo[79915]: pam_unix(sudo:session): session closed for user root
May 19 10:44:50 xo-ce sudo[79916]: pam_unix(sudo:session): session closed for user root
May 19 10:45:09 xo-ce xo-server[79847]: 2026-05-19T10:45:09.413Z xo:rest-api:error-handler INFO [GET] /vms/138538a8-ef52-4d0a-4433-5ebb31d7e152/alarms (401)
May 19 10:45:10 xo-ce xo-server[79847]: 2026-05-19T10:45:10.197Z xo:rest-api:error-handler INFO [GET] /backup-repositories (401)
May 19 10:45:10 xo-ce xo-server[79847]: 2026-05-19T10:45:10.197Z xo:rest-api:error-handler INFO [POST] /events/cd7bcc9d-15ba-4ce0-b31e-5d8798a4ff2e/subscriptions (>
May 19 10:45:15 xo-ce xo-server[79847]: 2026-05-19T10:45:15.187Z xo:rest-api:error-handler INFO [GET] /schedules (401)
lines 33-75/75 (END)

@Andrew @rzr

While updating my host i see 30 updates...

=========================================================================================================================================
 Package                            Arch                  Version                                    Repository                     Size
=========================================================================================================================================
Updating:
 forkexecd                          x86_64                26.1.4-3.1.xcpng8.3                        xcp-ng-testing                2.5 M
 gpumon                             x86_64                24.1.0-84.1.xcpng8.3                       xcp-ng-testing                1.6 M
 intel-microcode                    noarch                20260416-1.xcpng8.3                        xcp-ng-testing                 14 M
 kernel                             x86_64                4.19.19-8.0.46.3.xcpng8.3                  xcp-ng-testing                 29 M
 message-switch                     x86_64                26.1.4-3.1.xcpng8.3                        xcp-ng-testing                4.6 M
 qcow-stream-tool                   x86_64                26.1.4-3.1.xcpng8.3                        xcp-ng-testing                1.4 M
 rrdd-plugins                       x86_64                26.1.4-3.1.xcpng8.3                        xcp-ng-testing                9.8 M
 sm-cli                             x86_64                26.1.4-3.1.xcpng8.3                        xcp-ng-testing                4.8 M
 squeezed                           x86_64                26.1.4-3.1.xcpng8.3                        xcp-ng-testing                1.9 M
 varstored-guard                    x86_64                26.1.4-3.1.xcpng8.3                        xcp-ng-testing                4.9 M
 vhd-tool                           x86_64                26.1.4-3.1.xcpng8.3                        xcp-ng-testing                4.9 M
 wsproxy                            x86_64                26.1.4-3.1.xcpng8.3                        xcp-ng-testing                1.1 M
 xapi-core                          x86_64                26.1.4-3.1.xcpng8.3                        xcp-ng-testing                 30 M
 xapi-nbd                           x86_64                26.1.4-3.1.xcpng8.3                        xcp-ng-testing                3.1 M
 xapi-rrd2csv                       x86_64                26.1.4-3.1.xcpng8.3                        xcp-ng-testing                3.0 M
 xapi-storage-script                x86_64                26.1.4-3.1.xcpng8.3                        xcp-ng-testing                2.5 M
 xapi-tests                         x86_64                26.1.4-3.1.xcpng8.3                        xcp-ng-testing                5.0 M
 xapi-xe                            x86_64                26.1.4-3.1.xcpng8.3                        xcp-ng-testing                1.5 M
 xcp-featured                       x86_64                1.2.1-1.xcpng8.3                           xcp-ng-testing                1.5 M
 xcp-networkd                       x86_64                26.1.4-3.1.xcpng8.3                        xcp-ng-testing                4.8 M
 xcp-rrdd                           x86_64                26.1.4-3.1.xcpng8.3                        xcp-ng-testing                3.6 M
 xen-dom0-libs                      x86_64                4.17.6-8.1.xcpng8.3                        xcp-ng-testing                703 k
 xen-dom0-tools                     x86_64                4.17.6-8.1.xcpng8.3                        xcp-ng-testing                2.0 M
 xen-hypervisor                     x86_64                4.17.6-8.1.xcpng8.3                        xcp-ng-testing                2.4 M
 xen-libs                           x86_64                4.17.6-8.1.xcpng8.3                        xcp-ng-testing                 65 k
 xen-tools                          x86_64                4.17.6-8.1.xcpng8.3                        xcp-ng-testing                 46 k
 xenopsd                            x86_64                26.1.4-3.1.xcpng8.3                        xcp-ng-testing                1.4 M
 xenopsd-cli                        x86_64                26.1.4-3.1.xcpng8.3                        xcp-ng-testing                2.0 M
 xenopsd-xc                         x86_64                26.1.4-3.1.xcpng8.3                        xcp-ng-testing                5.3 M
 xo-lite                            noarch                0.21.0-1.xcpng8.3                          xcp-ng-testing                2.6 M

Transaction Summary
=========================================================================================================================================
Upgrade  30 Packages

Total download size: 152 M

I managed to down grade to node 22.22.3 and still same issue. Its seem better on node 22.22.3 but still an issue.

@simonp

I keep asking that about Node version. And every time i was told use the latest LTS which is 24.15... Yet i see 22 being used.

I can try later today and report back.

@taghjichte From my testing you would need to passthought a device for audio. If need for professional audio work then yes a pci passthough would be the perferred option. With that said.

@dinhngtu As for sound I have never looked much into it but the only vm I heard make sound is from Fedora even while booted from install iso. Kubuntu or windows with xen drivers installed no audio. (find for me at the moment)

While audio seems to work in Fedora from iso it seems to be limited to left channel. Local system is connected to 5.1 sound.

Made some updates to this project. Any existing users please see note. I have also updated the initial post.

️ Upgrading from an earlier version of this script? Read this first.
This version bumps the config schema to v2 (adds PUBLIC_URL and ENCRYPT_REDIS_CREDENTIALS) and corrects two config.toml generation bugs. Your xo-config.cfg is migrated automatically and non-destructively, but the corrected /etc/xo-server/config.toml is only written by --reconfigure.

Run --reconfigure once before resuming normal updates:

./install-xen-orchestra.sh --reconfigure
This regenerates config.toml with the fixes (your old file is backed up first; data in /var/lib/xo-server is untouched). It is strongly recommended if you set both REDIRECT_TO_HTTPS=true and REVERSE_PROXY_TRUST — that combination previously produced a duplicate [http] section and silently dropped one of the settings.

Afterwards, run --update as normal for routine XO updates — --update does not need to be preceded by --reconfigure again.

Also added option to adjust Xen Orchestras memory allocation. Useful if you are getting out of memory errors or added more memory to XO.

Update - Previous info was incorrect. I have removed and updated.
On fresh install Debian 13 with 8gb ram node -v 24.15.0.

==============================================
  Xen Orchestra Memory Allocation
==============================================

  Setting                       Value
  ----------------------------- -----------------------------------
  Total system RAM              7943 MB
  Current xo-server heap limit  ~2240 MB (node default, no --max-old-space-size set)
  Recommended heap limit        7431 MB

@Pilow said:

@LoTus111 nice, but could be better
you're missing the additionnal step in the TIPS section here :
https://docs.xen-orchestra.com/xo5/troubleshooting#memory

upgrading XOA to 8Gb is not enough, you have to tell xo services to be able to use this additionnal RAM.

Question is if XO is built with 6gb initially does one still need to adjust memory via the command? Or only if expanding after the fact?

Edit - to answer my own question and for others. After adding this function to my script it does appear the XO will setup appropriately with deployed with 6gb ram initially.

Update - The above information is incorrect. I must have made changes when I thought i didn't. I apologize for the incorrect information.
On fresh install Debian 13 with 8gb ram node -v 24.15.0.

==============================================
  Xen Orchestra Memory Allocation
==============================================

  Setting                       Value
  ----------------------------- -----------------------------------
  Total system RAM              7943 MB
  Current xo-server heap limit  ~2240 MB (node default, no --max-old-space-size set)
  Recommended heap limit        7431 MB

Just noticed my V6 dashboard for the XO appliance does not load... Commit - d810e

Reboot xo and the dashboard may load or after a few refreshes it will load or partially load.

Pool Dashboard loads...

After some trouble shooting with my script and AI this is what we think to be the issue...

After pulling master (at 8c00ccef / d810ea0c), @xen-orchestra/web/dist is empty after a fresh build. Turbo reports all 33 tasks successful, but the browser gets text/html for every JS chunk under /assets/ because xo-server serves / from an empty directory.

Yarn warns about unmet peer deps for @xen-orchestra/web-core@0.52.0:

pinia@^3.0.1
vue@~3.5.13
vue-router@^5.0.0
vue-i18n@^11.1.2
These appear to not be resolved correctly, likely causing Vite to produce no output while still exiting 0. The old UI is accessible at /v5.

Environment: Node 24.15.0, yarn 1.22.22, turbo 2.9.12, built from fresh clone.

Another issue found

After a token flush (or after any update where session tokens are cleared), xo-server logs:


TypeError: Cannot destructure property 'client' of 'token' as it is undefined.
    at Tokens._unserialize (packages/xo-server/src/models/token.mjs:16:13)
    at packages/xo-server/src/collection/redis.mjs:194:48
Root cause: collection/redis.mjs iterates xo:token:* keys but does not filter out the xo:token::indexes key, which is a Redis HASH (not a STRING). Calling GET on a hash-type key returns a WRONGTYPE error; the code receives undefined and passes it to _unserialize, which destructures it and crashes. The fix would be to skip keys containing :: when iterating token records, since those are collection index metadata, not auth token entries.

@Chuckz

See my answer toward Nested Virtualization - https://xcp-ng.org/forum/post/105019

https://docs.xcp-ng.org/compute/#-nested-virtualization

@AlexD2006

Yes while this can be a scarry situation there have been multiple post about his. @pilow has been dealing with it the longs I believe.

Some have tried @pilow suggestion and have been good since. I would see if you can create test vm or copy one of the existing ones to try with braking a production vm.