VDI not showing in XO 5 from Source.

andrewperry

@florent Thanks, if there is something I need to do to coalesce the vdis to avoid disaster, that would be good to understand. I had been thinking it was just an XO issue that would not affect running vms and their vdis.

bogikornel

@florent The following error occurred:

Mar 16 18:38:10 XOA xo-server[4001]: 2026-03-16T17:38:10. 246Z xo:rest-api:error-handler INFO [GET] /vms/0691be81-7ce9-7dba-9387-5620f8e0c52f/vdis (404)

XO version: Master, commit 15917
xcp-ng version: 8.3 with the latest updates.

What’s interesting is that there are two xcp-ng servers, and the problem only occurs on one of them.

anthoineb

@andrewperry Hi, we are working on 2 things:

a proper fix under development to avoid new issue where snapshot-of field is garbage.
a script to fix the wrongly set snapshot-of already present on affected pools.
Both are necessary and we hope we can release the script soon to at least workaround if the issue happen again before we release the fix.

Pilow

@anthoineb wow great news ! still impacted by this issue

andrewperry

@anthoineb thanks very much! Definitely has us sharpening our cli skills in the meantime….

wgomes

Just ran the update on Xen today and still have the same problem. "no itens found" when I go to see the disks tab.

Pilow

@wgomes yup thanks for bumping this topic, still having the problem too

bogikornel

@anthoinebThe problem still persists; when can we expect it to be resolved?

ashinobi

@Team-Storage

I am also having the same issue. Here is link on my forum post:

https://xcp-ng.org/forum/topic/12093/lost-connection-to-iso-repository/9

acomav

I have just started having this issue on one Pool yet 5 other pools are fine.
Running XOA 6.2.2.

andrewperry

@acomav it’s disappointing that there seems to be internal knowledge of:

(A) the issue with xcp-ng that triggers this problem but no one has shared the workaround in development to help us to fix it in xcp-ng

(B) the issue with XO failing to deal with this edge(?) case that was introduced in December still hasn’t been reverted.

I would have thought that if we were given the instructions for (A), someone could help with a patch for (B) or we’d just do it manually and (B) wouldn’t be needed.

If we have the information then we can help with the solution rather than feel like we’re living with a festering wound! Seems like a pretty important issue for enterprise software, and I haven’t heard that ‘if you pay money it will be quickly fixed’ - that’s both good and bad. I’d like to think it would be, but don’t want to feel like this community is a sales funnel either!

Anyway, xcp-ng and xo are a gift that I am very thankful for in my small business.

If the people on this thread can help in any way please let us know!