You can boot a VM on PXE by selecting the right boot order (enabling "Network" in boot order in XO for example)
Then you need to setup a PXE server, you can fine various guides by googling "PXE server setup", eg this one)
@schories It should be noted here that the emulated BIOS in XCPNG7.6 seemingly doesn't care about the bootflags. If the first one (per device id) isn't bootable it will fail, even if xvdb is bootable! So if you e.g. have swap on xvda, move it to another device id at the end (and temporarily disable it in fstab or so)
I did try that, but it still did not want to recognize and load the PV drivers properly. The VM is still limping with the realtek divers and. It is performing noticeably slow. Oddly others upgraded without a hitch.
If you don't want to take the risky route, just add the test repository by downloading the .repo file, then edit it to disable xcp-ng-centos_testing by default, and then use it only for installing the updated smartmontools with:
Yes I gave a look but Rancher is so much more different than a regular distribution, even CoreOS. The problem is everything on system is container, I can't install something by default even manually (using the tar.gz) because when you are login, you are in a BusyBox container in some way...
IMHO, I don't think the Citrix tools has been design to run in a container (even privileged) and to retrieve information for the entire system that is also in a container... What a mess right ? 😂
But in the end, these kind of Docker-ready OSes start giving me headache, even CoreOS now is not working like it was in the past, the fault of a very fast-paced developement from the CoreOS devs, the outdated documentation since they has been buyed by Red Hat (they move to Fedora CoreOS with lot of changes), and Citrix who seems to not giving much interest in CoreOS support.