Search results for query: RMRR

...0x000000f7ffc000 flags: 0x1 [ 0.740541] DMAR: dmar2: reg_base_addr f7ffc000 ver 1:0 cap 8d2078c106f0466 ecap f020df [ 0.740545] DMAR: RMRR base: 0x000000daf54000 end: 0x000000daf56fff [ 0.740548] DMAR: ATSR flags: 0x0 [ 0.740550] DMAR: ATSR flags: 0x0 [ 0.740553] DMAR-IR...

...base: 0x000000ef844000 flags: 0x1 [ 0.339231] DMAR: dmar0: reg_base_addr ef844000 ver 1:0 cap d2078c106f0462 ecap f020ff [ 0.339234] DMAR: RMRR base: 0x000000bb6c1000 end: 0x000000bb6ecfff [ 0.339236] DMAR: ATSR flags: 0x0 [ 0.339239] DMAR-IR: IOAPIC id 0 under DRHD base...

No ! It is weird why proxmox don't include this soluiton in proxmox by default. Anyway I hope to find a solution without a kernel edit.

That's what fixed it for me in Proxmox 7.4-16 and Promox 8.0 https://github.com/Aterfax/relax-intel-rmrr

This fixed it for me. https://github.com/Aterfax/relax-intel-rmrr

...now? What's the exact fix? I'm also experiencing the same issue right at the moment. https://forum.proxmox.com/threads/device-is-ineligible-for-iommu-during-pci-e-passthrough-on-hp-gen8-microserver.133443/ EDIT: I was able to fix it, try this fix. https://github.com/Aterfax/relax-intel-rmrr

...by my passthrough changes. 2- in the server console I got this message: "dmar device is ineligible for iommu domain attach due to platform rmrr requirement..." and others you can see in the attachment. Also earlier I got this message "L1TF SPU bug present and SMT on, data leak possible. ...".

...in the dmesg output, I see the following message: vfio-pci 0000:07:00.0: DMAR: Device is ineligible for IOMMU domain attach due to platform RMRR requirement. Contact your platform vendor. I came across a similar discussion on the Proxmox forum at this link...

...base: 0x000000eaffe000 flags: 0x1 [ 2.597445] DMAR: dmar1: reg_base_addr eaffe000 ver 1:0 cap d2078c106f0466 ecap f020de [ 2.597447] DMAR: RMRR base: 0x000000bdffd000 end: 0x000000bdffffff [ 2.597451] DMAR: RMRR base: 0x000000bdff6000 end: 0x000000bdffcfff [ 2.597452] DMAR: RMRR...

He don't need any "hack/patch", just use the HPE "conrep" util to enable the IOMMU on specific PCI-E slot (disabled by default on all PCI-E slot).

Sounds like the RMRR problem. I have no experience with that but maybe this can provide a work-around? Looks like you selected hardware that does not work well with passthrough.

Thank you so much Yes I did All the instructions, I just didn't do the kernel edit since I don't see that it will work in the long run and I kinda understand that it got included in proxmox kernel. As in the manual I did verfiy with (lspci -nnk) and I do get (Kernel driver in use: vfio-pci) ...

...not enabled VT-d? Do you known that Proxmox has two possible bootloaders? I don't know your particular hardware, so maybe someone else here can comment. There a some threads about DL380 and passthrough. Your system might have "the RMRR problem" and require an involved work-around or fix from HP.

...And i didn't found any solution. Does the patch mentioned here : https://github.com/Aterfax/relax-intel-rmrr/releases/tag/v6.2.16-4 is the solution for me ? actually i have these versions : proxmox-ve: 7.4-1 (running kernel: 6.2.16-4-bpo11-pve) - pve-manager: 7.4-16 (running version...

...base: 0x000000fed91000 flags: 0x1 [ 0.313326] DMAR: dmar1: reg_base_addr fed91000 ver 5:0 cap d2008c40660462 ecap f050da [ 0.313327] DMAR: RMRR base: 0x0000006c000000 end: 0x000000703fffff [ 0.313329] DMAR-IR: IOAPIC id 2 under DRHD base 0xfed91000 IOMMU 1 [ 0.313330] DMAR-IR...

...base: 0x000000fed91000 flags: 0x1 [ 0.145019] DMAR: dmar1: reg_base_addr fed91000 ver 5:0 cap d2008c40660462 ecap f050da [ 0.145022] DMAR: RMRR base: 0x0000007c000000 end: 0x000000803fffff [ 0.145025] DMAR-IR: IOAPIC id 2 under DRHD base 0xfed91000 IOMMU 1 [ 0.145028] DMAR-IR...

Do you have messages like Device is ineligible for IOMMU domain attach due to platform RMRR requirement. Contact your platform vendor. in your journalctl (you'll have to scroll or search)? Then you might first look into getting around the RMRR issue.

Hate to bring up new inquiry on older topic, but I am seeming to have same issue. It is an HPE Proliant DL380 Gen 9; I verified, even now, Every Virtual option enabled. No matter what I do, IOMMU will not enabled; But it is :( And my GRUB file looks like this that I added;

...0x000000c7ffc000 flags: 0x1 [ 2.877135] DMAR: dmar1: reg_base_addr c7ffc000 ver 1:0 cap 8d2078c106f0466 ecap f020de [ 2.877138] DMAR: RMRR base: 0x00000079174000 end: 0x00000079176fff [ 2.877142] DMAR: RMRR base: 0x000000791f4000 end: 0x000000791f7fff [ 2.877148] DMAR: RMRR base...

...the boot : ACPI: SPCR: Unexpected SPCR access Width. Defaulting to byte size DMAR: [fimware bug] : No firmware reserved region can cover this RMRR [ ..... [fimware bug] : the bios has corrupted hw-PMU ressources (MSR 38d is 330) x86/cpu: VMX (outside TXT) disabled by bios DMAR: DRHD...