@Danp

Hi,
I'll try this.

Thank you very much.

Best regards

Mattmurdock78

@olivierlambert

Hi,
Thanks you
It's work

@olivierlambert said in install XOA on VM Nested:

First, XOA describes only the turnkey virtual appliance you deploy with https://vates.tech/deploy , otherwise it's XO from the sources 🙂
The log output is a normal warning when you run XO on a non-Xen setup.

Double check your Node version though.

Hi,
Thank you for your feedback.

My Node.js version:
node -v
v20.19.5

Best regards

Mattmurdock78

Hi,

I created three nested VMs (on VMware ESXi). This is for a lab (to run tests, etc., without touching production ^^).

1 - An XOA VM on Debian 12 (I followed the official documentation, but I may have forgotten some things ^^) - it uses a vswitch0 interface to go out to the internet and another isolated interface (vswitch1) to communicate with the two nested VMs in XCP-NG.
2 - An XCPNG01 VM with an interface on vswitch1.
3 - An XCPNG02 VM with an interface on vswitch1.

I was able to access the XOA web console at http://X.X.X.X:8080.
But after authenticating with the default account, I get a blue circle in the middle of the page and nothing more, no action possible on the XOA web console.

When launching the commande "yarn start"

"/xen-orchestra/packages/xo-server# yarn start
yarn run v1.22.22
$ node dist/cli.mjs
2025-09-07T12:20:44.386Z xo:main INFO Starting xo-server v5.188.0 (https://github.com/vatesfr/xen-orchestra/commit/d36d64380)
2025-09-07T12:20:44.403Z xo:main INFO Configuration loaded.
2025-09-07T12:20:44.407Z xo:main INFO Web server listening on http://[::]:8080
2025-09-07T12:20:44.783Z xo:mixins:hooks WARN start failure {
  error: Error: spawn xenstore-read ENOENT
      at Process.ChildProcess._handle.onexit (node:internal/child_process:285:19)
      at onErrorNT (node:internal/child_process:483:16)
      at processTicksAndRejections (node:internal/process/task_queues:82:21) {
    errno: -2,
    code: 'ENOENT',
    syscall: 'spawn xenstore-read',
    path: 'xenstore-read',
    spawnargs: [ 'vm' ],
    cmd: 'xenstore-read vm'
  }"

Is this the "error: Error: Command failed: xenstore-read vm
xenstore-read: xs_open: No such file or directory" could be causing the problem, please?

Best regards

Mattmurdock78

0 b-Nollet committed to vatesfr/xen-orchestra

feat(lite): 0.14.1 (#8943)