We have been quietly suffering without the time to try and resolve it for the past couple of months.
I have now spent the day trying to resolve it in our environment, as we have one SR having this problem with some hundreds! of vdi.
I am having the same problem whether running the docker container version of XO CE or the local install on a VM we've been using for ages.
It seems that the api call from the VDIs tab in v6 (Disks in v5) may be triggering a call to the wrong url, without the /rest/v0 prefix:
sudo journalctl -u xo-server -n 300 --no-pager
2026-02-26T06:01:57.169Z xo:rest-api:error-handler INFO [GET] /vms/[[UUID]]/vdis (404)
I had the same experience as some others for a while, a couple of months ago, where it would not show up in the v5 UI but was showing in v6, but very quickly after that it stopped working in either.
I know that these are VDIs with a snapshot in the chain, for example a parent VDI that may have two snapshots from it.
I had thought the issue may have been had something to do with https://github.com/vatesfr/xen-orchestra/pull/9381 as it was around this time that I saw the problem in v5 before it also trickled through to v6 - but now I see that this topic was started just before Christmas so there must have been something else too.
If I run curl with the /rest/v0 prefix to the url I don't get the 404.
I hope this helps to track it down!
MathieuRA opened this pull request in vatesfr/xen-orchestra
closed
fix(rest-api): fix getVmVdis and enhance the type
#9381
