Search results

Today’s update on the M11SDV-8C-LN4F from Supermicro support sounds promising:

My last contact with Supermicro indicated, they were speaking to AMD about this now. It seems, they have been able to recreate the issue, I helped with that as good as possible.

I have contacted Supermicro support, I suggest everyone with a similar board does the same. They say they do not support Proxmox, but then again, looking at the above reserved regions output, that bug has been there for earlier kernels, too. I just never caused a problem because there was not...

I have already tried that a few days ago, and it doesn’t seem to work for my AMD system.

It's this one: https://www.supermicro.com/en/products/motherboard/M11SDV-8C-LN4F

Not much to do there I think?

Thanks, here you go: oot@epyc:~# uname -a Linux epyc 6.8.4-3-pve #1 SMP PREEMPT_DYNAMIC PMX 6.8.4-3 (2024-05-02T11:55Z) x86_64 GNU/Linux root@epyc:~# grep '' /sys/kernel/iommu_groups/*/type /sys/kernel/iommu_groups/0/type:identity /sys/kernel/iommu_groups/10/type:identity...

No, sadly that is not supported either. Perhaps there's a "relax IOMMU" kernel boot option to pass? I tried almost everything that remotely related to IOMMU and RMRR, no luck.

Thanks, can you think of a fix though? I already approached Supermicro and got their latest RC BIOS, no luck. They refuse to do anything else though , because Proxmox is not on the compatibility list for their board.

I you are referring to Firmware has requested this device have a 1:1 IOMMU mapping, rejecting configuring the device without a 1:1 mapping. Contact your platform vendor. this has been happening on all 6.8 kernels for me, when trying to pass through a NIC, also the on-board ones of my...

Interesting, that is the first Intel system displaying this error. I initially thought it would be limited to AMD systems like my problematic one. I have 2 Intel servers that pass through just fine with this kernel. For my AMD system, it’s not the X710 or E810 card, also happens with the...

Already updated to the latest that seems to have been published a few days ago, no luck.

Looks like my problem is not tied to the Intel X710 adapter, seems like 1:1 mapping is completely broken on the AMD EPYC M11SDV-8C-LN4F board. Trying to map an on-board interface, same problem: 2024-05-01T15:00:02.304416+02:00 epyc kernel: [ 782.498806] igb 0000:04:00.1: removed PHC on eno2...

As this does not seem to be widespread, I guess it might be due to the fact that we are running AMD CPUs instead of Intel. Perhaps that newer kernel code is not compatible with AMD.

I have tried a lot of combinations of IOMMU kernel parameters I thought might be remotely affecting 1:1 mapping, to no avail. Still completely at loss why this happens on my Supermicro EPYC system: Firmware has requested this device have a 1:1 IOMMU mapping, rejecting configuring the device...

For my error message, this seems to be the relevant commit. But I am in the dark what that means... > + /* > + * If the driver has requested IOMMU_RESV_DIRECT then we cannot allow > + * the blocking domain to be attached as it does not contain the > + * required 1:1 mapping...

I am getting the same error with my Intel X710-DA2 card. Worked fine with 6.5 https://forum.proxmox.com/threads/opt-in-linux-6-8-kernel-for-proxmox-ve-8-available-on-test-no-subscription.144557/page-6#post-657836

When flashing newer NVM, also make sure to not have any VMs running. They usually loose network and e.g. an OPNsense VM refuses to shut down in a timely fashion afterwards. I accidentally flashed the latest one with a VM active, which I had to shut down hard afterwards.

They may have gotten a new name, see here: https://pve.proxmox.com/wiki/Roadmap#8.2-known-issues ifconfig -a should show the new name.