@stormi I've placed the tarballs here https://student.oedu.se/~peder/xcp-ng/
I changed the static min to 512M, to match the Fedora case, but it still failed.

Olivier, I'm not using Xen Storage motion but I am using two old Lenovo L430 Thinkpads as "servers" so that could be part of the problem.

I'll install a new C7 guest and see if the problem persists.

@dan2462 Don't know what's causing the error but you can export the VHD by ssh:ing to your server or selecting "Local Command shell" on the console and running the following

xe vdi-list 
xe vdi-export uuid=the-uuid-of-your-VM filename=filename.vhd format=vhd 

Make sure the location you're saving to has enough space for the file.

If you have curl installed on your VirtualBox machine you can run

curl -u root:your-xcpng-root-password -X GET "server-name-or-IP/export_raw_vdi?vdi=your-vdi-uuid&format=vhd" -o filename.vhd

on it.

To run a command in the current directory you have to prepend it with ./
So try ./recover-account-cli.mjs

I don't know if it's the case here but one not-so-obvious thing in XO(A) is that you have to enable the slider to accept unverified certificates when you try to connect to the XCP-ng server.

The error here does suggest there's something else going on but make sure to check the above.

You should also install the XOA to make sure there's nothing wrong with your self-compiled XO.

Run this in a command shell on your XCP-ng server to install the appliance

bash -c "$(curl -s http://xoa.io/deploy)"

You can also run the vm-clone command on the XCP-ng server.
Something like

xe vm-clone new-name-label="clone name" vm="original name"

Stopping xo-server before compiling shouldn't be necessary unless someone tries to use XO while it's building.

That said, I would recommend building the source under /usr/src or ~/src or something and then moving the files ( mv * ) to something like /opt/xen-orchestra-DATE (or git revision)

Then use "stow" to create symlinks in /usr/local, like this
  stow -d   /opt/   -t   /usr/local   xen-orchestra-DATE

The stow command is in the CentOS repository or can be downloaded and compiled separately from any GNU mirror.

Make sure the /etc/xo-server/ config points to the relevant symlinks in /usr/local and restart xo-server

This way you can keep a number of different XO versions available in /opt and if there's a problem with any one of them you simply run
  stow -D  -d  /opt  -t    /usr/local    xen-orchestra-BADVERSION
to delete the symlinks to the bad version and
   stow -d   /opt   -t  /usr/local   xen-orchestra-GOODVERSION
to create links to the old, good one and then restart xo-server

When it's time to update the XO build go to the, now seemingly empty, source folder and run
  git reset HEAD --hard
to repopulate the working directory and then
  git pull && yarn && yarn build

AFAIK XO can only create a new storage repository, it would be nice to being able to attach an existing one as well.