PVE 8.2 Installer Failing - Need Assistance

BlackoreanGG

New Member
Jul 20, 2024
2
1
1
Hey All,

I'm fairly familiar with Proxmox, but this is a first for me.
I'm trying to install PVE 8.2 on a Dell PowerEdge R710 that I just reset and nuked the drives to start over with a blank canvas.
I've enabled both the embedded Gig NIC and PCIe GIg NIC, Flashed the BIOS to the 6.6.0 (latest).
I've made sure that my VLANs are accessible to my DHCP server.

I'm able to boot to the USB hosting the installer and initiate the PVE Automated Installer, then I'm thrown this error:

No DHCPOFFERS received.
No working leases in persistent database - sleeping.
done
Starting chrony for opportunistic time-sync...
Starting a root shell on tty3.
[ 78.148555] DMAR: ERROR: DMA PTE for vPFN 0xcf4de already set (to cf4de003 not 1137ab003)
[ 78.149618] DMAR: ERROR: DMA PTE for vPFN 0xcf4df already set (to cf4df003 not 1137ac003)
/sbin/unconfigured.sh: line 236: 2266 Bus error /usr/bin/proxmox-low-level-installer dump-env

Where should I start looking to begin troubleshooting?

-Thanks
 
  • Like
Reactions: Karr1
You could temporarily disable Intel VT-d within the BIOS for the installation process.
 
Did you solve it? I have the same problem, I have already installed it on 3 DELL servers and this R710 is like this. Disabling, after installing, do I enable it again? Won't you have problems with VT-d disabled?
 
I had a similar error with my R710 but I was able to resolve it and am now running the latest release of PVE 8.3.
I was not able to get it to work installing the latest proxmox ISO, but I did eventually get it to work on my R710 by installing the latest PVE 7.4 and then doing an in place upgrade.

Here's how I did it (note that you may not need to follow all these steps, this is just what I did to get Proxmox to work on my system):

Systems booting off zfs ignore steps 3 and 4.

If you have already done an in place upgrade you can of course skip installing Proxmox and just do steps 3 through 7 after selecting the previous kernel in grub.


1: Enable all virtualization technologies in the BIOS including SR-IOV.
2: Install proxmox 7.4 and update all the packages once install completes.
3: Add the following parameters to the GRUB_CMDLINE_LINUX_DEFAULT string in /etc/default/grub:
Code:
intel_iommu=on iommu=pt kvm.ignore_msrs=1 allow_unsafe_interrupts=1 vfio_iommu_type1.allow_unsafe_interrupts=1
4: Update grub by executing update-grub
5: Add the same cmdline parameters to /etc/kernel/cmdline:
Code:
intel_iommu=on iommu=pt kvm.ignore_msrs=1 allow_unsafe_interrupts=1 vfio_iommu_type1.allow_unsafe_interrupts=1
Note: It is unclear based on my research whether you need to add these parameters in /etc/kernel if you are booting with grub.
6: Run the command proxmox-boot-tool refresh to ensure that the command line parameters are properly updated across all EFI system partitions (where applicable)
7: reboot the system
8: Follow this guide to do an in place upgrade to proxmox 8.

I have both a Dell T710 running root on a ZFS mirror, as well as an R710 running EXT4 with grub.
Both have these kernel command line parameters set and both are working great.

Rough explanation of the command line parameters:
iommu=on - enable intel iommu virtualization for hardware passthrough and QEMU support.
iommu=pt - enable iommu tagging for devices configured for pass through. (On my T710 I use this to pass through the GPU hardware accelleration for Jellyfin as well as passing through hard drives through my HBA.)
kvm.ignore_msrs=1 - Not entirely sure, seems to fix some bugs with Nvidia GPUs on this hardware.
allow_unsafe_interrupts=1 and vfio_iommu_type1.allow_unsafe_interrupts=1 - More flags to help with GPU passthrough.

When I started to look into this issue myself I saw a lot of conflicting information. Some people say to turn virtualization off and some say to turn it on. The thing is that in my case I already had a successfull upgrade from 7 to 8 on my T710.
Today when I attempted to intall the 8.3 ISO onto my R710, I got errors similar to the one above.
The only differences wers that I had done an in place upgrade before, and that I did not have the same command line options as my T710.

I am by no means an expert but I thought I should update this thread with my experience in case it helps somebody.
 
Last edited: