@Andrew Thank you for your valuable experience and suggestions. I will personally test it and provide feedback on the results after testing.

Yes, because the CPU features are assigned on VM boot (you can't remove a CPU instruction while the VM is running, as you can imagine, if it's used anywhere in your guest OS, it will crash). A simple shutdown then start immediately after will make it boot with all the currently available CPU instructions/features

@jag5cof said in disk failure: @DustinB I have only one raid, (software) Truenas scales. What is XCP-ng installed onto? I'm not particularly familiar with the Truenas Scales platform, you may be better to reach out to their team/community for guidance. But generally speaking, two failed drives in an array, means you've already lost data. Your best bet would be to rebuild the array and then restore your data from backup.

@olivierlambert thank you

Ah I see, so if you enable it in the BIOS but without loading the module in the Dom0, then it will think the dead man switch is triggered and you are in for a reboot, I see Thanks for sharing your experience anyway!

USB passthrough is not PCI passthrough. As I said earlier, what you can try to do instead of USB passthrough, is to directly PCI passthrough the USB controller to your VM.

@amine-sahnoun There is a free version of XOA that you can use, but also the full version of XO can be built from the sources, they have pretty good documentation on how to do so.

@bigdweeb Yes.

Great news @Hightmar !! Thanks again @Andrew for your help

Try the CLI method and see if that fixes it. Those settings in XOA exist for vGPUs I believe, not for pass through.

@Andrew OK, thanks!

@iLix thks for replay, No bios and firmware are not up to date. other questions The misplacement of the RAM has an impact on the performance or otherwise, where you can see on two servers: [image: 1701959549994-empty-sockets-resized.png]

No worries, I'm used to the "You attempted an operation on a VM which lacks the feature" meaning to tools are installed. It could have been worded better. And sure, please provide screenshot if you can reproduce an issue even if the VM has tools (because if it doesn't, then it's a normal thing and not a bug)

Sometimes, I had to try 3 or 4 different sticks before one works. Those little things tend to die pretty quickly.

Thanks for the tips. All those items checked out. After a bit more troubleshooting involving a nearby switch and my VLAN routing, things are working a little more consistently, so I'm going to chalk this up to a routing issue elsewhere in my network. I'm just not used to a NIC turning off the link light if there's not a valid route.

@still_at_work Personally would say AMD, almost all XCP-ng servers I manage are AMD based and have been excellent so far. Usually a better value and better overall performance and their high core counts are great for virtualization unless you specifically need something that is faster single threaded. I have 3 hosts in my lab, all Threadripper (so baby EPYC) and they've been rock solid as well.

https://xcp-ng.org/docs/compute.html#vgpu This is what you need, Pass through. Not necessarily VGPU ($400 per seat). But! (Windows) Follow these steps: The link above. Do not connect the GPU to the VM you have. restart while holding shift so you can start with "safe mode + Networking" Before your VM gets to BIOS force Shut down. Attach RTX video Card Start "safe mode + Networking" Download and install NVIDIA drivers. Reboot You will have to do this to every VM that you need that RTX card on. Hasta la victoria siempre

I see, so you might need the UEFI info from the host or something similar I don't know if this exists, I have to admit I'm not using Windows in production myself.

You are welcome