I was looking at trying to use the SAN & NAS Free - Linux/VM version when I ran into an XCP-ng specific issue.
Apparantly, something about the virtual machine causes HTTPS setup to fail? As I can't log in to the console not having a CLI username/password I can't tell you anymore.
I do know the VM does successfully start in VirtualBox, so I changed the NIC type in XCP-ng via the XOA admin interface to E1000 to (hopefully) provide the nic type the vm is assuming it will find on first init.
I'm transferring a VM's HD I created from ovf in virtual box to the XCP-ng system now to see if an already init'ed system might boot ok.
The Latest Gartner® Magic Quadrant™Hyperconverged Infrastructure Software