@beshleman So, after yum --enablerepo=base install python-requests on each of my hosts, secureboot-certs install default default default latest works perfectly. (Cool that it installs certs to each host in the pool with one invocation from any pool host.) Interesting that it doesn't install the three files to /var/lib/uefistored until you secure boot a vm on each host. I went looking for them and was initially confused because they were only written to the pool db. Serves me right for looking under the hood! 🕵 Looks like XCP-ng secure boot is ready for prime time. Great job!
The FreeRDP project has a worked on shadow worker that may be utilized as the reason for a RDP worker and the OGON project as a comparable, however further developed, type worker that likewise considers plugable modules in that it very well may be utilized for RDP and even SPICE later on, on the off chance that I recollect effectively while I feel that they have VNC previously coded up.
My musings are to discover where XCP-ng at present handles the entirety of the VNC stuff for the hypervisor which I imagine that @olivierlambert just sent the connection in order to check whether it very well may be feasible to work out likely the OGON worker from that point to permit supporting the VNC, RDP, and SPICE numerous conventions.
I will take some time, yet on the off chance that all works out in a good way, the client ought to have the option to associate with any of the VM consoles (Linux, Windows, and so on) with any of these conventions and not need to do it from inside the Guest VM.
Actually what I think that I am looking to patch into XCP-ng is a way to have a "console" Passthrough which I think would do the job perfectly.
I am developing a PoC project using XCP-ng just for a heads up so some questions may sound non-standard but in my mind I have a rationale for looking in that direction so any help that you could provide would be greatly appreciated.
XOA is meant to be disposable. Config is pretty thin, all Xen objects are in memory only.
In case of problem, just deploy a new one and import the config. Works well for people who even lost their physical hypervisors (thanks for backup being entirely self-contained, even a fresh XOA is able to restore backups made by an old lost XOA)