8.0-3 VFIO Drivers no Longer Functional?

Windows7ge

Active Member
Sep 12, 2019
35
1
28
29
Hello, I'm helping someone setup hardware pass-thorugh on a new server but I haven't done hardware pass-through since PVE v7.

Following my old method everything seems to work...

Enabled IOMMU in BIOS & GRUB:
Code:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash intel_iommu=on"
Ran pve-boot-tool refresh and rebooted.

Added the necessary drivers to /etc/modules:
Code:
vfio
vfio_iommu_type1
vfio_pci
vfio_virqfd

Ran update-initramfs -u -k all with no errors:
Code:
update-initramfs: Generating /boot/initrd.img-6.2.16-3-pve
Running hook script 'zz-proxmox-boot'..
Re-executing '/etc/kernel/postinst.d/zz-proxmox-boot' in new private mount namespace..
Copying and configuring kernels on /dev/disk/by-uuid/7147-6DF6
        Copying kernel and creating boot-entry for 6.2.16-3-pve

Used a script created in /etc/initramfs-tools/scripts/init-top/ to block the kernel driver:
Code:
#!/bin/sh
PREREQS=""
DEVS="0000:02:00.0"
for DEV in $DEVS;
  do echo "vfio-pci" > /sys/bus/pci/devices/$DEV/driver_override
done

modprobe -i vfio-pci
Updated initranfs again and restarted the server.

This method is working flawlessly in v7.1-7 but in 8.0-3 behaves as if I never ran update-initramfs -u -k all and no matter what I try the system is behaving like the vfio drivers I added to /etc/modules were not loaded at startup for the kernel.

I'm currently at a loss and Google isn't being very helpful unless I'm just using the wrong search terms...
 
i never see any script like that.. Anyhow, at prox 7.2 they change setting and adjustment need to be made. and a on the part, different setting to be done with vm and grub base on your hrdw. Or simply, disconnect your modem, install prox 7.1 iso, set the setting and hop all work. or 7.4iso, set new setting and try out. no update, no v8 version as kernel is also a point of issues manytime.
 
i never see any script like that.. Anyhow, at prox 7.2 they change setting and adjustment need to be made. and a on the part, different setting to be done with vm and grub base on your hrdw. Or simply, disconnect your modem, install prox 7.1 iso, set the setting and hop all work. or 7.4iso, set new setting and try out. no update, no v8 version as kernel is also a point of issues manytime.
It's been so long I don't remember where I got the script but the principal of it is it forces the desired driver into a controller based on physical Device Address instead of doing it via Device ID or just blacklisting the driver server wide. Speaking of which, neither of those worked either...

I'm very confused by what you're saying. So it's still possible but the procedure is different? Any documentation on what the new process is?
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!