Using this command to install from the old guest tools ISO worked fine

./install.sh -d rhel -m 8

the file version is xe-guest-utilities-latest-7.16.0-2.el8.x86_64, the distro logo is not showing though.

@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!

That's correct: NASA asked for a solution and Rackspace worked with them to create it 🙂 See https://www.rackspace.com/library/what-is-openstack

See https://xcp-ng.org/forum/topic/4378/new-guest-tools-iso-for-linux-and-freebsd-can-you-help-with-the-tests

@stormi Sorry for the delay in testing. This looks to be fixed now. Thanks!

For the exertion start, I have run over sensible RDP stuff from the FreeRDP project just as OGON.

bestrdp (https://www.freerdp.com/)

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.

At any rate that is objective

I see movement in the github repo again. Good sign!

Hi,

No, at least not yet, due to the lack of demand for that.

I'm happy to hear you are working on VirtIO since both FreeBSD and Linux guests supports it well these days.

Obviously this is a big commitment, but I thought I'd post about it anyway in the hopes that it could one day become possible 🙂

One more thing that would be needed for virtio is spice support. This would actually be pretty cool as it allows piping USB, Audio and VGA to users connecting to the VM's console 🙂

Packer is an option (better than Ansible in this case).

Otherwise, use xo CLI to do that.

We should probably talk in private for some details @throk 😉
Also ping @ch_s

The documentation is now in a much better shape than when I started this thread, has been available for months at https://xcp-ng.org/docs/.

You can still contribute to it. Each page footer has a "help us improve this page" link that allows to create a pull request with your changes.

Many thanks to everyone who contributed to the documentation and to those who will.

@olivierlambert

THX Olivier

looks like it Working
I hope i can build a Coreboot with a Supermicroboard 🙂

@stormi Actually you are correct and it is call "xen"

https://wiki.xenproject.org/wiki/Compiling_Xen_From_Source

I see that on the XCP-ng 8.2 ISO that you are using a variant of the 4.13 Xen hypervisor. I think that is where I will start my reading up on things.

Thanks again and I appreciate your help

@olivierlambert I also just did not see the actual Hypervisor repo on the XCP-ng Github (https://github.com/xcp-ng)

Thanks my friend. You are so very helpful to me as I endeavor to get deeper ingrained into XCP-ng.

Hi All,

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.

Thanks again

If you need virtual desktop infrastructure, also take a look to UDS Enterprise 🙂

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)