AMD Ryzen Issue(s) on version 8.1 and 8.2.1

[Include-sys]

Specs of my system,

AMD Ryzen 9 3900x Asus X570-F Gaming (BIOS version 4403, AMD AM4 AGESA V2 PI 1.2.0.7) G.Skill 3600Mhz CL18 DDR4 MSI GT 1030 2xNVMe Storage (500GB+2TB)

I tried 8.1 and 8.2.1 with a lot of different start combinations(changing cmdline boot option(2048M and etc.), different bios options(disabling PBO, disabling XMP, disabling C-State and etc.)) nothing worked. I kept getting the following error,(First on BIOS, second on UEFI) It wasn't booting.

Then I tried version 8.0.0 and could install it without changing anything. I wanted to have ext4 and checked official doc troubleshooting before giving it another try and saw iommu=0 option. And It worked, I was configuring the installer but It hung at some point and I decided to try again then I started to get this USB errors,

I thought It would run without a problem If I installed it once, so I started over every time It hung or showed these errors then I was able to install it. I still have to add iommu=0 option to boot xpg-ng but It's crazy slow, and not usable. It takes 5 mins to get an ssh shell.

So I'm curious If anyone has a solution for this? I really want to use the latest one.

Thanks in advance!

[Include-sys]

Here are some additional logs,

boot.log crit.log daemon.log hypervisor.log kern.log xensource.log

[olivierlambert]

Note: related to https://xcp-ng.org/forum/topic/5652/panic-on-cpu-0-xen-bug-at-iommu-init-c-1419

[geoff313]

Hi @Include-sys I had the same problem on two AM4 motherboards (the iommu_init.c error). To fix them I downgrade the BIOS to a version that was pre windows 11 support (but not sure if it was change in the bios to support windows 11 or something else). This worked for an Asus and a MSI board with 8.2.1.

[ryzen3100]

Downgrading to pre-win11 BIOS did not fix the issue for me (Asrock B550M Pro4, Ryzen 5800X)

[konsultaner]

I have the same issue on:

• AMD Ryzen Threadripper PRO 5975WX
• ASUS Pro WS WRX80E-SAGE
• NVIDIA GeForce RTX 4070 Ti 12GB

any news on this?

[olivierlambert]

"X" CPUs are having some weird quirks requiring some fixes. There's some patches not far, so we should get a solution in the next weeks or months :)

[konsultaner]

@olivierlambert Thanks for the reply. I went through the forum thread. Is there a beta or later alpha of 8.3 which seem to have worked?

[olivierlambert]

No, the patch isn't available yet, but this will come. Stay tuned!

[martinkeat]

Confirming - Ryzen 5 3600 here with latest version of xcp-ng (new install, new system) and kernel panic.

[olivierlambert]

Can you take a look at https://xcp-ng.org/forum/topic/5652/panic-on-cpu-0-xen-bug-at-iommu-init-c-1419/160?

[martinkeat]

Hi @olivierlambert

Disabled IOMMU and run the current version to no effect.

Ran the Alpha2 version with IOMMU enabled and that failed.

Ran the Alpha2 version with IOMMU disabled and it allowed me in to run the install (which is now happening). Will report back after install and whether I can re-enable IOMMU after install.

For the record, the system is 4 x Kioxia 480GB SSDs, A320M-K Motherboard just updated with the latest bios PRIME A320M-K BIOS Version 6062 2023/03/21, 32GB of Vengeance LPX DDR4 Ram, AMD Ryzen 5 3600.

[olivierlambert]

Have you enabled x2APIC?

[martinkeat]

Hi Oliver, yes it was enabled.

Installation ran all the way through with alpha 2 and was able to switch on IOMMU after installation.

[martinkeat]

So hopefully when the alpha becomes the LTS version it will all be hunky dorry! Until then, alpha it is.

[olivierlambert]

8.3 is already pretty stable, the biggest thing is to carefully check when there's updates. 8.3 won't be an LTS, but it will become an official release at some point. For consumer grade hardware, 8.3 state is probably better than most other Alpha software (there's already many users on it for NUCs and so on)

[konsultaner]

@olivierlambert is there a very recent nightly build I can try? Is it good enough for production in a small business environment?

1 Machine, 3 or 4 VMs just filled with web stuff, nothing fancy with GPU or USB or whatever?

[olivierlambert]

We don't have nightly builds (yet), latest alpha is 2, an alpha 3 will be out in next weeks, but even alpha 2 is stable. What's less is the potential upgrade path if many things changes, but as long as you have XO backups with it, you shouldn't have any problem. We have dozens of people using it already without any issue. Welcome to the testing club!

[konsultaner]

@olivierlambert I get the same error on 8.3 alpha 2. Will this issue be solved in alpha 3? Sorry for bothering

[olivierlambert]

We have patches for -X CPUs coming in the next weeks, at least in the testing repo or something.

[stormi]

@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 works around the kernel panic that was initially the topic of this bug report, if I understood things correctly.

[konsultaner]

@stormi I noticed this workarround, but my mainboard doesn't have a setting where I can disable IOMMU.

[EDIT]

I found it... it works 🥳

[stormi]

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 installer for XCP-ng 8.2.1.