Thank you every visitors and for those who did not had the chance to visit fosdem check this report:
https://xcp-ng.org/blog/2026/02/19/fosdem-2026-follow-up/
[image: vates-xcp-ng-at-fosdem-2026-1.webp]
One question, I promised to forward to the forum, how many VM are you running on XCP-ng ?
Dozen, hundreds, thousands or more ?
@afmart_dei
I had similar issues recently. But not exacly the same. I was able to add second host to pool but was not able to work because in my case eth0 was host managment, eth4 storage, eth5 migration, eth 7 vm network. My second host at the time did not have eht7
Then i further messed myself up by using second host as its own pool attached to same storage and when down hill form there, but was an easy fix.
Just added the option for --proxy to deploy xo proxy.
https://github.com/acebmxer/install_xen_orchestra/tree/xo-proxy
Deploying a Proxy VM
The script supports deploying a Xen Orchestra Proxy VM directly to your XenServer/XCP-ng pool using the --proxy option:
./install-xen-orchestra.sh --proxy
Important Limitations and Notes
️ Network Configuration:
The --proxy option does not allow you to specify which network the VIF is attached to
It will default to "Pool wide network associated with eth0"
️ Production Use Warning:
Use at your own risk. Not advised for use in production environments.
This feature is provided for testing and development purposes. For production deployments, it is recommended to manually configure proxy VMs with proper network planning and validation.
[image: 1771890268295-screenshot_20260223_184415-resized.png]
[image: 1771890892329-screenshot_20260223_185435-resized.png]
[image: 1771891338169-screenshot_20260223_190135-1-resized.png]
While can add host and remote via proxy. Backups will fail with the following error.
backupNg.runJob
{
"id": "95ac8089-69f3-404e-b902-21d0e878eec2",
"schedule": "76989b41-8bcf-4438-833a-84ae80125367"
}
{
"code": -32000,
"data": {
"stack": "TypeError: licenses.find is not a function
at Function.<anonymous> (file:///usr/local/lib/node_modules/@xen-orchestra/proxy/app/mixins/appliance.mjs:168:23)
at processTicksAndRejections (node:internal/process/task_queues:95:5)
at file:///usr/local/lib/node_modules/@xen-orchestra/proxy/app/mixins/backups.mjs:110:25"
},
"message": "licenses.find is not a function"
}
Difficile de parler de « réalité » avec les benchmarks. Vérifiez aussi l'iodepth (qui dépend du type matériel que vous avez, sur du flash/NVMe vous pouvez monter à 128 ou 256), la latence entre en compte aussi bien sûr.
Le bottleneck principal est le monothreading de tapdisk, si vous testez sur plusieurs VMs différentes la somme va monter de manière assez régulière.
