Samuel Verschelde

@konsultaner Did you try to disable IOMMU, install using 8.2 alpha 2, update the system, and then re-enable IOMMU? This won't solve the known issues about -X CPUs, but already...

This issue is fixed in the refreshed XCP-ng 8.2.1 installation ISOs. You can test them from https://xcp-ng.org/forum/topic/8026/xcp-ng-8-2-1-refreshed-installation-iso-better-hardware-support and provide feedback. When the testing phase ends, they will become the default...

No promises here, but I'd be interested in hearing from users testing with the refreshed installation ISOs for XCP-ng 8.2.1 which are currently undergoing public testing: https://xcp-ng.org/forum/topic/8026/xcp-ng-8-2-1-refreshed-installation-iso-better-hardware-support.

I think it's not a problem if several tickets exist, as long as they reference each other. Individual situations may have different useful details.

It's not the first time we've had issues with this specific vendor driver. Thanks for the this data point. However I would like to avoid such comments being seen as...

This installation issue, besides being fixed in XCP-ng 8.3 beta, is now also fixed in refreshed installation ISOs for XCP-ng 8.2.1, that are currently undergoing public testing at https://xcp-ng.org/forum/topic/8026/xcp-ng-8-2-1-refreshed-installation-iso-better-hardware-support.

Yes, let's close it. Thanks for the reminder.

We will build the kernel with auditd in XCP-ng 8.3

Unfortunately, we just found out that enabling auditd changes the kernel ABI in a very large way, which breaks the compatibility with all out-of-tree kernel modules that have been built...

Or rather, will be, since XCP-ng 8.3 is not released yet :)