Also note - when run a rebuild i get the following... [WARNING] XO 6 web UI (@xen-orchestra/web/dist) was not built — browser will use XO 5 UI at /v5. [WARNING] This may be caused by unmet peer dependencies (pinia 3.x, vue-router 5.x). [WARNING] Access your XO instance at: https://<host>/v5 until the upstream issue is resolved. The rebuild completed successfully. A few things to note from the output: Build successful: All 35 packages built in ~48 seconds XO 6 UI warning: @xen-orchestra/web was not built due to unmet peer dependencies (pinia ^3.0.1, vue@~3.5.13, vue-router ^5.0.0, vue-i18n ^11.1.2). The browser will use XO 5 at /v5 until upstream resolves this. Service running: HTTPS on port 443, tokens preserved, settings unchanged. The XO 6 UI issue is an upstream dependency mismatch in the master branch — nothing broken on your end. If you need XO 6, you'd need to wait for the upstream repo to update those peer deps or pin to a commit where they were satisfied.

@Rod-G These have 9.4.2-xxxx and I need to go through and update everything now that I see how far behind I am. the second VM completed fine after its reboot, something was just stuck in a dirty state and got in the way of the import or health check.

@tonyp90 great, thanks !

I'm not positive, but this may be available RSN in xo-lite.

@Danp I was going to do the upgrade over the December / January Christmas break in Australia but that is when this issue became apparent so we didn't want to be making major changes until it was resolved. I note @anthoineb noted the first report was late August / September 2025 which was just before 8.2.1 reached EOL, so it would be a shame not to have a fix for it tested on 8.2.1 as it seems an upgrade to 8.3 would be unwise while we still have this issue?

Hey, @Forza I found this step and this guide useful in preventing driver issues due to errors had today: https://techdirectarchive.com/2026/05/21/prevent-automatic-driver-updates-in-windows-and-xen-orchestra/

@AtaxyaNetwork no error but also no xe-linux-distribution service installed or available...

@florent said: where does this disk comes from From my Redhat 10 @florent said: if you have access to your SR from the outside, you can also put the qcow2 file directly I create a VM to be a NFS to access the 3 HDs, the qcow disks are on the Redhat 10 that I was trying to import from. Do you mean I put the qcow disks on one of the HDs and access them when I create a VM?