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 ?
The issue seems to be synchronizing the network configurations.
The pool management is configured for bond1 (eth6+ eth7), that is set for LACP, both switch ports are already configured for LACP.
Bond0 (eth0 +1) is created, but bond 1 fails, and management interface is never assigned to Bond1.
Network 2 and 3 are active on the pool even if never used.
@florent since your early patch of my XOA (xo-server restart at the disk activity peak)
[image: 1772047222068-3e55ee10-ef90-471e-aec6-967a569c8fa1-f3d3bd6c-ef54-4f5c-9202-5aab25319db9.png]
noticing vif0 transmitting a bit on the network and different ram activity on a timespan of 2 hours
something has changed, is it for the better ? let the night decide
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.
