Sure, let me come back to you this week!

@cyoung_mi It's a XCP Xen/Kernel code issue... So if that can be fixed then yes.

@Andrew Let's start with igc. Install git-lfs if not done already, fork and clone https://github.com/xcp-ng-rpms/igc-module/ and then create a PR against the 8.2 branch, based on the existing spec file.

@TheFrisianClause From my experiments using a GTX1080ti you'll have to follow the instructions for generic pcie-passthrough to the letter, which mostly means that the passthrough needs to be done on both sides, on the Dom0 for relinquishing device control and for the DomU to pick up the device (section 5). Perhaps now that the restrictions from Nvidia have gone, Vates will kindly include some GUI support for those operations in XOA. Note, that if your dGPU has multiple devices (e.g. my GTX 1080ti also has a USB-C controller on-board), both entries need to be added in a single 'xe vm-param-set' statement, otherwise only the latter device (USB in my case) will wind up in the VM.... (yeah, at least 30 minutes of puzzling on that one) Of course, if the dGPU is your console device, it means flying blind afterwards, but I'm getting used to that with all the recent iGPUs as well (then again, I have some DisplayLink hardware that's currently unused and EL7/8 drivers for those have popped up recently...) Thankfully the dreaded error 43 issues have gone away with the more recent Nvidia drivers, sadly Kepler support has been retired (got a lot of those still around), so you may want to preserve the latest CUDA 11.4 release as one that offers both, but for Maxwell you should still be fine. Before trying to diagnose with the Nvidia drivers, you should be able to see the device transition via lspci on both sides, Dom0 and DomU.

@rajaa-b no problem

@stormi Nope.... my mistake. Now ubuntu 20.04 and Windows 2016 boot with UEFI Secure Boot enabled. # secureboot-certs install No arguments provided to command install, default arguments will be used: - PK: default - KEK: default - db: default - dbx: latest Downloading https://www.microsoft.com/pkiops/certs/MicCorKEKCA2011_2011-06-24.crt... Downloading https://www.microsoft.com/pkiops/certs/MicCorUEFCA2011_2011-06-27.crt... Downloading https://www.microsoft.com/pkiops/certs/MicWinProPCA2011_2011-10-19.crt... Downloading https://uefi.org/sites/default/files/resources/dbxupdate_x64.bin... Successfully installed certificates to the XAPI DB for pool.

@stormi, @olivierlambert Thanks to everyone, I was able to complete it. Thank you very much!!

Solved the problem by explicitly specifying the data type $resize = 'VDI.resize'; $xcpapi->$resize($vdi, ''.(int)$hdd2.''); Doesn't work without brackets ''.(int)$hdd2.''

@andrew Yes indeed, those are known shortcomings: The installer does not wipe previous RAID setups. It does not offer to create another RAID for data storage. There's an extensive guide about this at https://xcp-ng.org/docs/guides.html#software-raid-storage-repository

Your starting point will be https://xcp-ng.org/docs/develprocess.html#local-rpm-build

Sure go ahead you should be able to do it in terms of permissions. If not, let me know

You might ask Xen project upstream directly (on appropriate mailing list), see https://xenproject.org/help/mailing-list/ However, if there's nobody interesting to do this, it means no money. If your company is interesting in it, we can try to see the amount of work needed (IMHO: not trivial at all) and get a rough price estimate.

Updated xcp-ng-pv-tools on my one XCP 8.2 server. (We have mostly (citrix)7.1 and (xcp)7.6 because of hardware RAID limitations) Found the ISO located at /opt/xensource/packages/iso. (verison 8.2.0-9) Moved this to my local workstation, and then to my ISO-repo file server. Went to my XCP 7.6 server, and then to the Rocky Linux 8.4 VM i just set up. Removed the EPEL xe-guest-utilities-latest package. (7.21.0-1) Mounted the XCP ISO from the ISO-repo and installed the guest tools from that. (7.20.0-9) Agent detected! and the service seems to run without error.

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

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

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.