@florent I can confirm that this fixes the issue!

@CodeMercenary As far as I understand it, because its Xen based, it is Numa aware by default.

Nevermind. I forgot your previous post about: You'll need to modify two files (via SSH): /opt/dell/omc/utilities/tui/bin/ome_disk_config.sh /opt/dell/mcsi/appliance/scripts/appliance_ressource.sh In these files, replace /dev/sd with /dev/xvd. I went and made these changes, and now the Data drive is loading after doing the drive scan. I should mention that doing this BEFORE first logging into the OME web interface and completing the initialization seems to be best (no further errors appear once logged in).

Pinging @Team-OS-Platform-Release

That is a frustrating loop to be in, especially with TrueNAS. Usually, when the VM fails to start after a change, it’s because XCP-ng is trying to pass through a PCI device (like an HBA) that isn't being released properly by the host. Have you checked if the "hide" parameters in your grub config are still correct? Sometimes an update can reset those, and the host grabs the controller before the VM can. Another thing to try is toggling the BIOS/UEFI mode in the VM settings - TrueNAS can be picky about that depending on which version you’re running.

Version 0.0.6 released - it mostly fixes many small things, most notable the console is now very stable, there was a bug in VNC protocol that resulted in randomly getting just a black screen, that was fixed + many other small fixes (unable to add more than 16 disks to VM, host pool join logic, pool creation logic, etc) There is now also experimental support for override of VM transfer network, following same logic as Xen Orchestra has (it checks if xo_migration_network host otherConfig key is set and if yes it follows it). There is also additional setting for it in pool properties. https://github.com/benapetr/XenAdminQt/releases/tag/v0.0.6-alpha

Adding @Team-XO-Backend in the loop