[Update: 05-17-21] - I apologize to everyone. I shouldn't try and post late at night (or early in the morning). I have added more information as well as some recent things I found this morning at the bottom.
Hi all,
So I have had an i5-3330 with 8Gb of ram in a home lab running Proxmox with IOMMU for 6 months now and enjoyed it. But you can see my problem, I can't run too many VMs. Actually, it is just running Plex with an Nvidia GTX970. In short, I wanted to upgrade and had a chance to get a Dell R820 with 4 x E5-4640, 64Gb ram, and a Perc H310 with 4 x 300Gb SAS drives. So I did.
The first thing I did was update all the firmware that I could and then installed Proxmox. Updated Proxmox, rebooted, then added the "intel_iommu=on iommu=pt intremap=no_x2apic_optout". I found out later I needed the "intremap=no_x2apic_optout" in my search for a solution, but for brevity (and because it didn't change anything), I am including it here. Every time I boot with IOMMU on I get an error and never get into Proxmox.
If I remove the "intel_iommu=on" it boots fine, with no passthrough function of course. I Checked that virtualization and SR-IOV is on in the Bios. I'm not too familiar with server hardware, so I am sure I'm missing something simple.
I have been searching for 3 days, I have tried many different guides and forums and I can't seem to find a solution. I can get a list, but since the result was the same I figured that it wasn't needed.
I was working on it this morning and noticed this error on a fresh install without IOMMU turned on just yet. Not sure if it has anything to do with it.
This has kinda exhausted me, so if I forgot to add something, let me know and I'll get the info as soon as I can.
Thanks for the help.
---
[Update: 05-17-21] - I learned alittle more about how to read the
output properly. leading me to find out it is this:
I have tried to disable it in the vfio.conf file and the blacklist.conf outlined in the Proxmox VE Admin Passthrough section. Hilarity ensued, but I am learning how to un-screw things up. It was a different result which makes me think I am on the right track just the wrong course of action.
Hi all,
So I have had an i5-3330 with 8Gb of ram in a home lab running Proxmox with IOMMU for 6 months now and enjoyed it. But you can see my problem, I can't run too many VMs. Actually, it is just running Plex with an Nvidia GTX970. In short, I wanted to upgrade and had a chance to get a Dell R820 with 4 x E5-4640, 64Gb ram, and a Perc H310 with 4 x 300Gb SAS drives. So I did.
The first thing I did was update all the firmware that I could and then installed Proxmox. Updated Proxmox, rebooted, then added the "intel_iommu=on iommu=pt intremap=no_x2apic_optout". I found out later I needed the "intremap=no_x2apic_optout" in my search for a solution, but for brevity (and because it didn't change anything), I am including it here. Every time I boot with IOMMU on I get an error and never get into Proxmox.
If I remove the "intel_iommu=on" it boots fine, with no passthrough function of course. I Checked that virtualization and SR-IOV is on in the Bios. I'm not too familiar with server hardware, so I am sure I'm missing something simple.
I have been searching for 3 days, I have tried many different guides and forums and I can't seem to find a solution. I can get a list, but since the result was the same I figured that it wasn't needed.
I was working on it this morning and noticed this error on a fresh install without IOMMU turned on just yet. Not sure if it has anything to do with it.
This has kinda exhausted me, so if I forgot to add something, let me know and I'll get the info as soon as I can.
Thanks for the help.
---
[Update: 05-17-21] - I learned alittle more about how to read the
Code:
lspci -nn
Code:
03:00.0 RAID bus controller: LSI Logic / Symbios Logic MegaRAID SAS 2008 [Falcon] (rev 03)I have tried to disable it in the vfio.conf file and the blacklist.conf outlined in the Proxmox VE Admin Passthrough section. Hilarity ensued, but I am learning how to un-screw things up. It was a different result which makes me think I am on the right track just the wrong course of action.
Last edited: