Or just follow the official documentation… https://xen-orchestra.com/docs/from_the_sources.html

I did the manual installation via the XVA. It worked for me.

Thanks for the suggestion, but don't you think we never thought to that before? I start to think you are considering us as 2 people in a garage.

We are crunching numbers on a regular basis, and it never computes with those models. Proxmox is here since a long time, with a strong and "large" use base allowing to use this model. This is not the case for us now.

So on short term, this is not doable. But be assured we are continuously working on testing various models to see what's the best fit.

You should use GitHub and create an issue. This will be taken into account for XO 6 web UI 🙂

@rkelley You nailed it for item 2. Was driving me crazy!

Ok, that does make sense for item #1 and was kinda what I was thinking. But it does lead one to believe you can't live migrate anything with a single host even if you have shared/remote storage available unless you poke around and experiment with different buttons like i did. 🙂

That's "normal" if you are running XO (from the sources) and not XOA (the pre-built appliance)

@Danp Thanks for pointing me in the right direction. I was following an older howto where --global was not specified. That was my first problem - now fixed!
Second problem was that I had installed into the root directory of Centos7 so the paths for creating the links were different. Once I had found the correct paths and created the links all was good.
Thanks again.
Frank.

@fx991 the SR scans can and have been helpful in detecting storage issues for me. Sometimes when my ISO library goes offline but XCP-ng has not detected the failure and still shows it as connected I usually notice it from the long running SR scans that get stuck.

The "Connection to VM console..." task is when you have a console window open to a VM or Host...hence the reason why you can't cancel/end it...if you want to get rid of it then close all open console windows

I already opened one: https://github.com/vatesfr/xen-orchestra/issues/4882.

I can already confirm that I could trigger 2 Jobs manually in XO and it run successfully.
Thanks!
The scheduled ones I will see tomorrow and report if it would fail, but it is not expected.

Thanks! Found it.

It could, I don't know what XCP-ng Center can do in details. But again, this is NOT a problem.

I said it 3 times, why do you think it's still related to your coalesce problems?

It's the default parameter of your template. XCP-ng Center is probably forcing fixed memory, XO is just doing template recommendation.

You can change values at creation in "Advanced" section.

Exactly like how it's displayed in the documentation.

Try to switch to NFS and report if you have the same issue.

@Danp As soon as I read that, I thought "I think I've been down this road before." Sure enough. I gave it 2G of RAM and it wouldn't build. I gave it 4G of RAM and I watched using systat and that final step went to about 52% of RAM usage. It has completed. I routinely run Xen Orchestra on a 1G VM because it's rarely used and it runs fine that way. But building it clearly takes a lot more RAM. I'll update my internal notes. It might be worth it to update the building from source docs to mention having enough RAM.

Thanks for hitting the nail on the head with that advice!

XOA got its own numbering, unrelated to xo-server or xo-web: it'a all a matter of a coherent "whole", including dependencies etc. Thing we can't provide when built on sources.

Please test and report 🙂 You can switch to latest too, doesn't matter.

Hi Julien, i already did that. localadmin is the user i also use for the xo-server. did not elaborate that further on a test system.

@luiscamaral Let me reply to myself. If you update xoa it will show user and password as in bellow description:

Template for Alpine Linux 3.10, with 'root' username and 'xohub' password, DHCP enabled
😊