ProLiant Servers - Netservers
cancel
Showing results for 
Search instead for 
Did you mean: 

Re: Device is ineligible for IOMMU domain attach due to platform RMRR requirement

viumden
Occasional Visitor

Re: Device is ineligible for IOMMU domain attach due to platform RMRR requirement

I have a Microserver Gen8, and tries to passthrough Nvidia GPU in PCI slot 1 under linux kernel 4.1.5, applied the advisory to PCI Slot1, still got the error message:

Device is ineligible for IOMMU domain attach due
to platform RMRR requirement. Contact your platform
vendor.

I think there is still something incompatible implementation in HP firmware. And there is just no valid solution from HP for several months.

15 REPLIES
ralfE
Occasional Advisor

Re: Device is ineligible for IOMMU domain attach due to platform RMRR requirement

I get stuck with a Microserver Gen 8 with the same problem.

I applied the advisory (http://h20564.www2.hpe.com/hpsc/doc/public/display?docId=emr_na-c04781229&sp4ts.oid=5249566 ) to PCI Slot1 using the "conrep-stuff", still got the error message:

Device is ineligible for IOMMU domain attach due
to platform RMRR requirement. Contact your platform
vendor.

This happens with kernel 4.2.2.1 and a DVB-S-Card to be passed through to a vm under qemu 2.4.

... had I built a consumer-class PC for serving at home ... I think I had have no such problems.

Btw ... there are broken dependencies for the hp-scripting-tools- and hp-health-packages for debian jessie.

Please go on and give us a patched BIOS which is a bit more conform with standards (see advisory RedHat https://access.redhat.com/articles/1434873 )

Jimmy Vance
HPE Pro

Re: Device is ineligible for IOMMU domain attach due to platform RMRR requirement


ralfE wrote:

I get stuck with a Microserver Gen 8 with the same problem.

I applied the advisory (http://h20564.www2.hpe.com/hpsc/doc/public/display?docId=emr_na-c04781229&sp4ts.oid=5249566 ) to PCI Slot1 using the "conrep-stuff", still got the error message:


What is the outut of verify.dat using the command: # conrep -s -x conrep_rmrds.xml -f verify.dat

 


ralfE wrote:

Btw ... there are broken dependencies for the hp-scripting-tools- and hp-health-packages for debian jessie.


What are the broken dependencies so I can report them

 

 

 




__________________________________________________
No support by private messages. Please ask the forum!      I work for HPE

If you feel this was helpful please click the KUDOS! thumb below!   
ralfE
Occasional Advisor

Re: Device is ineligible for IOMMU domain attach due to platform RMRR requirement

<?xml version="1.0" encoding="UTF-8"?>
<!--generated by conrep version 4.4.0.0-->
<Conrep version="4.4.0.0" originating_platform="ProLiant MicroServer Gen8" originating_family="J06" originating_romdate="06/06/2014" originating_processor_manufacturer="Intel">
  <Section name="RMRDS_Slot1" helptext=".">Endpoints_Excluded</Section>
  <Section name="RMRDS_Slot2" helptext=".">Endpoints_Included</Section>
  <Section name="RMRDS_Slot3" helptext=".">Endpoints_Included</Section>
  <Section name="RMRDS_Slot4" helptext=".">Endpoints_Included</Section>
  <Section name="RMRDS_Slot5" helptext=".">Endpoints_Included</Section>
  <Section name="RMRDS_Slot6" helptext=".">Endpoints_Included</Section>
  <Section name="RMRDS_Slot7" helptext=".">Endpoints_Excluded</Section>
  <Section name="RMRDS_Slot8" helptext=".">Endpoints_Included</Section>
  <Section name="RMRDS_Slot9" helptext=".">Endpoints_Included</Section>
  <Section name="RMRDS_Slot10" helptext=".">Endpoints_Included</Section>
  <Section name="RMRDS_Slot11" helptext=".">Endpoints_Included</Section>
  <Section name="RMRDS_Slot12" helptext=".">Endpoints_Included</Section>
  <Section name="RMRDS_Slot13" helptext=".">Endpoints_Included</Section>
  <Section name="RMRDS_Slot14" helptext=".">Endpoints_Included</Section>
  <Section name="RMRDS_Slot15" helptext=".">Endpoints_Included</Section>
  <Section name="RMRDS_Slot16" helptext=".">Endpoints_Included</Section>
</Conrep>

And this for the dependencies:

The following packages have unmet dependencies:
 hp-health : Depends: libc6-i686 but it is not installable or
                      lib32gcc1 but it is not going to be installed
 hp-scripting-tools : Depends: lib32bz2-1.0 but it is not installable

Thanks for your reply so far ...

For the conrep output ...
I had tried "Slot7" as a "second" shot ... cause I wasn't shure if "Slot1" in BIOS is really Slot1. lspci reports the needed card to be on 0.07.00 ... so I tried "Slot7".

 

Jimmy Vance
HPE Pro

Re: Device is ineligible for IOMMU domain attach due to platform RMRR requirement

The output does look correct. Please open a support case with HPE and reference the HPE customer advisory along with the Red Hat paper.

I will pass the dependency issue along to the team that works with the Debian versions of the tools

 




__________________________________________________
No support by private messages. Please ask the forum!      I work for HPE

If you feel this was helpful please click the KUDOS! thumb below!   
ralfE
Occasional Advisor

Re: Device is ineligible for IOMMU domain attach due to platform RMRR requirement

Ok ... for everyone who suffers from this problem:

YOU ARE LOST ... HP will not accept this as existing problem ... WHY?

HP's answer: This configuration is unsupported. (may I add  "- as so often, when work is to be done")

Okay ... think about it and say it this way: Using an actual kernel on our HP-Server hardware is not supported and we will not consider to help you if you are running into problems. Nice standing ... and frustrating for the costumer - hopefully the next buying decision will be somewhat luckier.

In my opinion the only way to work around this effekt - else of returning the hardware to HP - will be to use an older kernelversion. Rumors are that the line of 3.16 will be a good startpoint. Have a shot at it ...

In HPs speaking this thread is ended with status "SOLVED" ........

 

Jimmy Vance
HPE Pro

Re: Device is ineligible for IOMMU domain attach due to platform RMRR requirement


ralfE wrote:

Ok ... for everyone who suffers from this problem:

YOU ARE LOST ... HP will not accept this as existing problem ... WHY?

HP's answer: This configuration is unsupported. (may I add  "- as so often, when work is to be done")

Okay ... think about it and say it this way: Using an actual kernel on our HP-Server hardware is not supported and we will not consider to help you if you are running into problems. Nice standing ... and frustrating for the costumer - hopefully the next buying decision will be somewhat luckier.

In my opinion the only way to work around this effekt - else of returning the hardware to HP - will be to use an older kernelversion. Rumors are that the line of 3.16 will be a good startpoint. Have a shot at it ...

In HPs speaking this thread is ended with status "SOLVED" ........

 


Did you open a case? If so please send me the case number here or in a private message




__________________________________________________
No support by private messages. Please ask the forum!      I work for HPE

If you feel this was helpful please click the KUDOS! thumb below!   
ralfE
Occasional Advisor

Re: Device is ineligible for IOMMU domain attach due to platform RMRR requirement

This was the case number:

CASE:4764654455

Thank you for being interested ... but I am afraid you will not be allowed to help us, due to internal restraints at HP. You know that "This configuration is unsupported"-stuff ... for example if the hardware was upgraded with a more powerfull CPU and that else ... this goes into direction "Support for maker-szene" (doing things which are not thought be the manufacturer). But what is so far away, if someone is going to use an entrylevel server as homeserver for delevering Sat-TV over IP, serving some homepages and doing private mailservices ... and to encapsulate the services to a handfull virtual machines for easier handling? 

Jimmy Vance
HPE Pro

Re: Device is ineligible for IOMMU domain attach due to platform RMRR requirement

Unfortuanely the case is mostly documented in German so I can't read it.  What I can translate and after looking at the CPU spec, the CPU in that model Microserver doesn't support VT-d

http://ark.intel.com/products/71074/Intel-Celeron-Processor-G1610T-2M-Cache-2_30-GHz




__________________________________________________
No support by private messages. Please ask the forum!      I work for HPE

If you feel this was helpful please click the KUDOS! thumb below!   
ralfE
Occasional Advisor

Re: Device is ineligible for IOMMU domain attach due to platform RMRR requirement

You are right ... but it is now a:

Intel(R) Core(TM) i5-3470T CPU @ 2.90GHz

which is fully capable of VTd ... The server was updated. In the case shall be a complete AHS-File ... which will show no issues on the hardware side. A warning maybe, due to the although upgraded memory using non-hp-branded ecc-memory from Kingston, but nothing to really worry about.

Today the server runs with VMWare 6.0.0 ... PCI-Passthrough works for the DVB-Sat-card. ... VMWare in 6.0.0. uses an older kernel than proxmox today. My design today is not very efficient ... proxmox is running as virtual machine ... a virtualization in the vitualization... nested -> not very desirable ... but the management of lxc-containers from proxmox is it worth. It was a pain getting VMWare to accept multiple VMs behind a virtual nic ... but it works for my needs. This does not mean, that I am pleased and the problem can be closed "solved":

My target is clearly to avoid VMWare and to run proxmox as virtualization native ....

 

ralfE
Occasional Advisor

Re: Device is ineligible for IOMMU domain attach due to platform RMRR requirement

Ahh ... thread moved to somewhere in "outer space" ... is this a sign that someone is working on the problem, or is it the confirmation of "closed as RESOLVED - not supported configuration" ... and so saying: "Sorry, we are not interested in your "exotic" problem and your usecase of our hardware?"

Jimmy Vance
HPE Pro

Re: Device is ineligible for IOMMU domain attach due to platform RMRR requirement


ralfE wrote:

Ahh ... thread moved to somewhere in "outer space" ...

I don't think the thread has moved anywhere


ralfE wrote:

is this a sign that someone is working on the problem, or is it the confirmation of "closed as RESOLVED - not supported configuration" 


These forums are community based and assistance is provided by other users in the community, support cases are not really worked here.  Some of us that work for HPE try to assist here when we can.  I have not used passthrough mode so I can only go by what is in the Customer Advisory. 

You state it is working as expected with VMware, so it sounds like the information in the CA is correct. Why it isn't working with proxmox is anyone's guess.  Have you tried with some other supported flavor of Linux?

 

 




__________________________________________________
No support by private messages. Please ask the forum!      I work for HPE

If you feel this was helpful please click the KUDOS! thumb below!   
ralfE
Occasional Advisor

Re: Device is ineligible for IOMMU domain attach due to platform RMRR requirement

Well, Jimmy ... I really appreciate to see a HP-Member who is interested in "this" sort of non-standard problems.
So here comes even more information ...

Some days are gone and I have tested the system in "production" ... watching and recording SAT-TV and presenting it to various clients like htpcs, tabletts, smartphones at home. And now I can say only the following: For my usecase - especially the virtualization with today VM-Ware 6.0.0 and the usage of a sat-reciever card with pci-passthrough - the GEN 8 Microserver is an absolute NO GO! Some posts earlier I was happy, that the dual-port DVB-SKY 952 was able to be passed to a virt. machine. For live-Watching everything was really fine ... but if the stream goes to storage it gets smashed - no recording was watchable, every few minutes I got pixeled videos for about 10 to 20 seconds with cuts in audio too. I checked the recording local to eleminate networking problems ... it was as scrambled as through network delivery. Something very bad must be happened with the stream when going directly from PCIe to Network II (storage is a ISCSI-Disk).
I cannot explain why PCIe to Network I (live watching) worked flawless. Are Network I and II bound to different bridges (Noth, South)? ... if so I will reconfigure the complete system and bind the ISCSI to Network I and check this.
After this I changed the SAT-reciever to my old single reciever-card (tt s2-4100) which was serving me for years in my old system with VM-Ware 5.5. This card was not able to be passed through to the virtual vdr. The logs of VM-Ware complained about not being able to reset the card on the pci-bus ... and there the by RedHat described problem is again visible.
What works today is a USB-sat-reciever passed through to the vdr ... but this a compromise with drawbacks on the WAF (the feared woman-acceptance-factor) :)
For me this is only a hobby and I am willing to spend hours of testing and frustration, but this hardware is friendly said the most thrilling one I ever had. Today I still believe that it is possible to reach my target ... but there where thoughts containing "ebay" already. Well choosen consumer-hardware in a self-build-system cannot be worse.

Btw ... the "rest" - the simple stuff; serving e-mail, hosting webpages, runing virt. desktops - works without complications and is (until today) rock solid ...
And a note back to the linux-flavour ... every distribution which uses stock-kernel 4.x will have the problems with IOMMU due to a not standard conform usage of the PCIe-Bus. The "Device is ineligible for IOMMU domain attach due to platform RMRR requirement"-Message is in my understanding a very close to hardware and very deep in kernel-check to stop a isolated PCI-card from accidently writing to memory areas outside of her isolation - which will be a serious security breach and a possible worst-case for the host if it goes into an active diskIO or something that way.

Jimmy Vance
HPE Pro

Re: Device is ineligible for IOMMU domain attach due to platform RMRR requirement

To bad it hasn't worked out for your usage model.  Have you checked over at the Home Server Show forums http://homeservershow.com/forums/index.php?/forum/96-hp-servers/ ? The users there do a lot of experimenting with the hardware.




__________________________________________________
No support by private messages. Please ask the forum!      I work for HPE

If you feel this was helpful please click the KUDOS! thumb below!   
pharidos
Visitor

Re: Device is ineligible for IOMMU domain attach due to platform RMRR requirement

I am not able to disable RMRR for slots greater than 16

pharidos@uks9:~/pt$ cat exclude.dat
<Conrep>
<Section name="RMRDS_Slot4" helptext=".">Endpoints_Excluded</Section>
<Section name="RMRDS_Slot5" helptext=".">Endpoints_Excluded</Section>
<Section name="RMRDS_Slot88" helptext=".">Endpoints_Excluded</Section>
</Conrep>
pharidos@uks9:~/pt$ sudo conrep -l -x conrep_rmrds.xml -f exclude.dat 
conrep 4.6.0.0 - HPE Scripting Toolkit Configuration Replication Program
(c) Copyright 2013,2016 Hewlett Packard Enterprise Development LP

System Type: ProLiant DL380 Gen9
ROM Date : 03/05/2015
ROM Family : P89
Processor Manufacturer : Intel(R) Corporation

XML System Configuration: conrep_rmrds.xml
Hardware Configuration: exclude.dat
Global Restriction: [3.40 ] OK

Loading configuration data from exclude.dat

ERROR: Invalid dat file entry RMRDS_Slot88

Conrep return code: 2
pharidos@uks9:~/pt$ lspci -s 88:
88:00.0 Ethernet controller: Intel Corporation Ethernet Controller 10-Gigabit X540-AT2 (rev 01)
88:00.1 Ethernet controller: Intel Corporation Ethernet Controller 10-Gigabit X540-AT2 (rev 01)
pharidos@uks9:~/pt$ 
pharidos@uks9:~/pt$ dmesg | grep -i "Setting identity map for device.*88"
[    0.908246] DMAR: Setting identity map for device 0000:88:00.0 [0x791dc000 - 0x791ebfff]
[    0.908349] DMAR: Setting identity map for device 0000:88:00.0 [0x791ec000 - 0x791effff]
[    0.908363] DMAR: Setting identity map for device 0000:88:00.1 [0x791ec000 - 0x791effff]

 

drymis
Occasional Visitor

Re: Device is ineligible for IOMMU domain attach due to platform RMRR requirement

I have the same hp-health install problems, but I am running Ubuntu Server 14.04 x64 directly on a Proliant DL360 (noVM). 

$ aptitude install hp-health
The following NEW packages will be installed:
hp-health lib32gcc1{ab} libc6-i386{ab}
0 packages upgraded, 3 newly installed, 0 to remove and 0 not upgraded.
Need to get 2,711 kB of archives. After unpacking 12.2 MB will be used.
The following packages have unmet dependencies:
lib32gcc1 : Depends: gcc-4.9-base (= 4.9-20140406-0ubuntu1) but 4.9.1-0ubuntu1 is installed.
libc6-i386 : Depends: libc6 (= 2.19-0ubuntu6) but 2.19-0ubuntu6.6 is installed.

$ apt-get install hp-tools
The following packages have unmet dependencies: hp-health : Depends: libc6-i686 but it is not installable or lib32gcc1 but it is not going to be installed $ apt-cache policy hp-health hp-health: Installed: (none) Candidate: 10.40-1815.49 Version table: 10.40-1815.49 0 500 http://downloads.linux.hpe.com/SDR/downloads/MCP/ubuntu/ trusty/current/non-free amd64 Packages

So your problem is not unique. Were you able to get hp-health installed on your system?