In case someone ran into the same problem here is how I solved it.
I had a feeling this was http mounts issue. I checked and looks like during update process the .xo-server.toml got deleted. I copied the sample one from the /opt/xen-orchestra/packages/xo-server/sample.config.toml , edited the http.mount and bob's your uncle.

I have a feeling this has something to do with the format of that file change. When I originally built from source the file has a slightly different syntax and it was called .xo-server.yaml. At least according tot he directions I used to build. In any case its all back to normal now.
Thanks you everyone for your help.

Thanks, this way we'll have a way to understand what's wrong with this OVA, if it's something really specific or a VMWare way to make something we didn't expected 🙂

Yes, I know this is not exclusive to C, but there are some facilities to handle this, that are, as far as I know, not available in Node.

@MajorTom I saw it on my XenOrchestra's and wondered also 🚰

@hitechhillbilly yes it does 🙂 you can do it live or with a shutdown VM

that's relatively easy to explain, only the naming is doubled:

the backup-hdd are local disks raid1 in xcp-ng and there brought to xcp-ng as a local "vmbackup" volume, called vmbackup on xcp-ng-volume a disk is created with the name "backup_raid1_1tb" and connected as 2nd disk (xvdb) to XO

ab68fa1c-49a8-4d15-afcf-ecdc8bcd9d04-grafik.png

to make the disk available for backup-usage the disk xvdb is mounted via "remote" as a local now usage for backup-ng is possible, but the usage is not xo_disks

Yes, you can safely remove them.

I've replied on github. For sure the VMs should not boot. Of course the source vm has autopower on parameter becouse it's needed.

The problem is big: DR copy of Second Active Directory server is up.... for sure I can expect AD problems in a while...

724808f6-fc82-4487-9f87-4d0291fc3e92-image.png

Autopower on is set up:

e4b71a2e-17cd-4e5f-a863-77f693249847-image.png

That's why I thought. NEVER enable base repo. If you want a package from their, just enable it during the yum install command line.

Okay thanks. Note that with XCP-ng 8.0, it will be even easier to deploy XOA, directly from the host HTTP URL "mini website".

@pdonias Thanks for confirming that this issue wasn't caused by the use of a 3rd party script.

Hi,

Before reporting on issues when you use XO from the sources, you must always fetch the latest code available on GitHub. Because it's likely some issues are fixed since then. Please upgrade, and come back if the problem persists 🙂

We're deploying support for the incoming release channels and there was an issue with that.

Hi Brad,

From the whole team: thanks a LOT. It's really cool to hear your feedback 🙂

Enjoy XOA/XCP-ng!

Will do. Done.

Likely orphaned VDIs. Removing them should fix coalesce.

Okay so maybe there is a race condition somewhere with zstd (gut feeling, about premature EOF and using ZSTD). @johnelse what do you think? Do you need better logs?

Thanks for your feedback. We also took in consideration what people asked for the next UI 🙂