From my XOA [image: 1771944043824-screenshot-2026-02-24-094020.png] One of my pools have been offline for 24hrs due to power outage. Standard XOA can open support tunnel if needed.

Starting with the documentation is a good thing: https://docs.xcp-ng.org/troubleshooting/ This will give you (and us) hints on what's going on

@florent So If my Mikrotik router is sitting between XO and the HITRON and the HITRON is power cycled, because the Mikrotik is the gateway as far as XO is concerned and the gateway is not down, will the 10 minute timeout apply or might it timeout faster than that?

Aha! I will move to prometheus in the future, but at the moment it is more basic. Thank you!

Update 2: Renaming eth2 to eth6 and eth7 worked like a charm. Had to do a fresh install because the emergency network restart didn't work. it's hard to tell which PIF belong to each bond on XO (at least on source-compiled version), needed to use old xcp-center to figure it out. This thread can be closed. still having some network issues :S

@Cyrille

Hello, since this never had a clear resolution, here is explanation of the bug and why it happens: There is a bug in disk iteration in that XO vmware plugin (somewhere in that esxi.mjs I don't remember exact location) - it basically expects that all disks of VM exist in same datastore and if they don't it crashes as the next disk in unexpectedly missing (undefined) Workaround is rather simple - select the VM in vmware, migrate -> storage, disable DRS (important) and then select any DS that no disks current exist on. If you select and DS that is already used by same VM it will sometimes not get fixed! It also may happen even if VM is "apparently" looking like it's on single DS, even if it reports as such, still try to migrate it to another DS, and disable DRS so that really all files, even meta files are in same directory. Then run XO import again, it will magically work.

@pilow As I am completly new to this scripting and such I did reach out to Ai for assistance and believe the license check should be bypassed now. Again not suggested to use in production. Use at your own risk. still has its own branch for more testing before merging to main branch.