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 ?
@comdirect
Use this command: (replace sda in the command below with the relevant device)
cat /sys/block/sda/queue/scheduler
The active scheduler will be enclosed in brackets. e.g. noop deadline [cfq]
For multiple drives use:
grep "" /sys/block/*/queue/scheduler
I appreciate the comments and they are all welcome. Do keep note that I did say this is not Production ready and use at your own risk. If you see anything that is wrong please provide suggest feedback to correct said issue.
I just started running my home lab from this version yesterday. I imported my config from previous XO. Today i saw 4 new commits and the update function updated to the latest commit. Backups have run with no issue.
As I can only test in my home lab I can only speak of my own experiences.
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.
