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.
@john.c If a Xen Orchestra developer asks for logs / heap snapshots I will be happy to provide them.
Ideally they should tell us what is needed from us to debug this.
That being said I am not entirely sure they are currently working on this as XO team has not been very vocal here.
Looking at Github repository commits indicates that other things are currently being prioritized over this crucial backup stability issue.
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.
