@AtaxyaNetwork Hi yes, Sorry I'm not super experienced in this area at all. I'm SSHd into the host and just ran dmesg -T in the root. [image: 1771509732474-0583e493-4d70-40b7-afc0-a88b0d9fd1a4-image.png]

Hi @Bastien-Nollet, oh okay, thanks for clarifying!

@olivierlambert Je corrige le test FIO qui ne reflète pas la réalité. Le débit est d'environ 5.5Gbps/s throughput-test-job: (groupid=0, jobs=4): err= 0: pid=2452: Fri Feb 20 10:02:44 2026 read: IOPS=10.3k, BW=646MiB/s (677MB/s)(75.7GiB/120002msec) slat (nsec): min=0, max=230384k, avg=183401.87, stdev=705796.53 clat (usec): min=1227, max=252507, avg=11943.41, stdev=5670.46 lat (usec): min=1357, max=252514, avg=12126.82, stdev=5722.82 clat percentiles (msec): | 1.00th=[ 8], 5.00th=[ 9], 10.00th=[ 10], 20.00th=[ 11], | 30.00th=[ 11], 40.00th=[ 12], 50.00th=[ 12], 60.00th=[ 12], | 70.00th=[ 13], 80.00th=[ 14], 90.00th=[ 15], 95.00th=[ 16], | 99.00th=[ 19], 99.50th=[ 20], 99.90th=[ 23], 99.95th=[ 241], | 99.99th=[ 247] bw ( KiB/s): min=347392, max=848640, per=100.00%, avg=661471.87, stdev=15968.62, samples=956 iops : min= 5428, max=13260, avg=10335.50, stdev=249.51, samples=956 write: IOPS=10.3k, BW=646MiB/s (677MB/s)(75.7GiB/120002msec); 0 zone resets slat (nsec): min=0, max=230979k, avg=199173.27, stdev=642430.39 clat (usec): min=1057, max=257260, avg=12446.58, stdev=5587.92 lat (usec): min=1349, max=257596, avg=12645.76, stdev=5633.93 clat percentiles (msec): | 1.00th=[ 9], 5.00th=[ 10], 10.00th=[ 11], 20.00th=[ 11], | 30.00th=[ 12], 40.00th=[ 12], 50.00th=[ 12], 60.00th=[ 13], | 70.00th=[ 13], 80.00th=[ 14], 90.00th=[ 16], 95.00th=[ 17], | 99.00th=[ 20], 99.50th=[ 21], 99.90th=[ 24], 99.95th=[ 40], | 99.99th=[ 247] bw ( KiB/s): min=339968, max=829184, per=100.00%, avg=661765.89, stdev=15966.89, samples=956 iops : min= 5312, max=12956, avg=10340.09, stdev=249.48, samples=956 lat (msec) : 2=0.01%, 4=0.01%, 10=10.97%, 20=88.57%, 50=0.40% lat (msec) : 250=0.05%, 500=0.01% cpu : usr=1.26%, sys=13.37%, ctx=2934238, majf=0, minf=51 IO depths : 1=0.1%, 2=0.1%, 4=0.1%, 8=0.1%, 16=0.1%, 32=0.1%, >=64=100.0% submit : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.0%, >=64=0.0% complete : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.1%, >=64=0.0% issued rwts: total=1239575,1240247,0,0 short=0,0,0,0 dropped=0,0,0,0 latency : target=0, window=0, percentile=100.00%, depth=64 Run status group 0 (all jobs): READ: bw=646MiB/s (677MB/s), 646MiB/s-646MiB/s (677MB/s-677MB/s), io=75.7GiB (81.2GB), run=120002-120002msec WRITE: bw=646MiB/s (677MB/s), 646MiB/s-646MiB/s (677MB/s-677MB/s), io=75.7GiB (81.3GB), run=120002-120002msec Disk stats (read/write): dm-3: ios=1238448/1239080, merge=0/0, ticks=1874753/2464217, in_queue=4338970, util=99.99%, aggrios=2479429/2480865, aggrmerge=0/48, aggrticks=3199165/4352700, aggrin_queue=7551881, aggrutil=81.90% xvda: ios=2479429/2480865, merge=0/48, ticks=3199165/4352700, in_queue=7551881, util=81.90%

Check the disk scheduler on the Dom0 for this drive.

@jmara Thank you for the input. All pods are running with caveats. Prior to executing the installation, I updated the image name to ghcr.io/vatesfr/xenorchestra-csi:edge in the manifests. After executing the install, I had to manually edit the image name in the DaemonSet, from ghcr.io/vatesfr/xenorchestra-csi-driver:edge to ghcr.io/vatesfr/xenorchestra-csi:edge. After editing the DaemonSet, the node pods restarted and transitioned to running. However, the controller pod was still attempting to pull this image: ghcr.io/vatesfr/xenorchestra-csi-driver:edge and never transitioned to running. To correct that, I edited the image name in the Deployment, from ghcr.io/vatesfr/xenorchestra-csi-driver:edge to ghcr.io/vatesfr/xenorchestra-csi:edge. Thus after editing the DaemonSet and Deployment, the pods transitioned to running. kgp -nkube-system | grep csi* csi-xenorchestra-controller-b5b695fb-ts4b9 3/3 Running 0 4m8s csi-xenorchestra-node-27qzg 3/3 Running 0 6m21s csi-xenorchestra-node-4bflf 3/3 Running 0 6m20s csi-xenorchestra-node-8tb5m 3/3 Running 0 6m20s csi-xenorchestra-node-t9m78 3/3 Running 0 6m20s

I wonder to which extend we could lower dom0 memory, eventually reduce the set of features for this kind of usecases. I can definitely see a pool of machines (x86 or ARM) for industrial purpose where that could make sense, and that could be managed and update through XOA.

@stormi Thank you so much. Only now getting around to setting up another set of R660s, will let you know how this works. Edit: worked beautifully on a new set of R660s. Using the old 20250606 ISO, the BCM57414 were not detected. The new ISO works as expected (BIOS install, did not attempt UEFI) and the NICs are all enumerated properly.

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 ?

I had same problem, about last 2 weeks, but is is about Xen update, after apply last update, Backup of Windows VMs works again.

Hello everyone ! I rebuild a new OME appliance with the latest version (4.6) Dell decided to give this appliance Proxmox, Nutanix and OpenShift compatibility, but no XCP-ng yet... If someone from Dell want to reach out about this, please contact me ! [image: 1771504614561-7f4cc1c1-90c4-4f30-94f8-cf109711cfd6-image-resized.png] What i did on the rebuild: Via live CD add xen-blkfront and xen-netfront driver, and rebuild the initrd change root password activate SSH. Via SSH sed -i -e 's/sda/xvda/g' /opt/dell/omc/utilities/tui/bin/ome_disk_config.sh sed -i -e 's/sda/xvda/g' /opt/dell/mcsi/appliance/scripts/appliance_resources.sh bash /mnt/Linux/install.sh # To install XCP-ng tools As usual, please send a DM if you want the link to the VHD Feedback is welcome ! (Disclamer: This build is something I create on my free time and to help people who have difficulty running Dell appliances on XCP-ng. I do not guarantee a fully functional appliance, but I do my best to make it work. If you have a support contract with Dell and require official support for OME, please contact Dell and request compatibility with XCP-ng.)