@JamesG said: When I ask the system what it thinks the capabilities are, again I get Gen1x1: cat /sys/bus/pci/devices/0000:00:08.0/current_link_speed 2.5 GT/s PCIe cat /sys/bus/pci/devices/0000:00:08.0/current_link_width 1 cat /sys/bus/pci/devices/0000:00:08.0/max_link_speed 2.5 GT/s PCIe cat /sys/bus/pci/devices/0000:00:08.0/max_link_width 1 This information is actually crafted by QEMU, it doesn't represent the actual real device PCI state; you should check this from Dom0 which should be closer to reality.

I made 2 PRs upstream, let me ping @Team-XAPI-Network about it. https://github.com/xapi-project/xen-api/pull/7145 https://github.com/xapi-project/xen-api/pull/7146 olivierlambert opened this pull request in xapi-project/xen-api open xapi: report a clear error when host evacuation is blocked by unprotected VMs #7145 olivierlambert opened this pull request in xapi-project/xen-api draft xapi: evacuate non-HA-protected VMs when no host failures are tolerated #7146

For your storage question, it's fully explained in the doc: https://docs.xcp-ng.org/storage/#-how-to-modify-an-existing-sr-connection And yes, it's planned to get the complete error visible in XO, sadly, it's not "obvious" since the error message isn't returned by XAPI when you try to start but by another method we need to call after it fails ("assert can be started here" from the top of my head). Let me ping @julienXOvates