Proxmox 8 AMD GPU Passthrough

DarkJackal87

New Member
Apr 20, 2025
5
0
1
Hello everyone,

i've been following the guide for the GPU Passthrough at this link:

https://forum.proxmox.com/threads/p...x-ve-8-installation-and-configuration.130218/

So far i've reached the part where i need to install the vendor-reset service, and i've installed it and configured the service which looks like it's running

○ vreset.service - AMD GPU reset method to 'device_specific'
Loaded: loaded (/etc/systemd/system/vreset.service; enabled; preset: enabled)
Active: inactive (dead) since Sun 2025-04-20 11:57:39 CEST; 3min 16s ago
Duration: 3ms
Process: 1520 ExecStart=/usr/bin/bash -c echo device_specific > /sys/bus/pci/devices/0000:0a:00.0/reset_method (code=exited, status=0/SUCCESS)
Main PID: 1520 (code=exited, status=0/SUCCESS)
CPU: 3ms
However, running the command dmesg | grep vendor_reset yeld no output and also running modprobe vendor-reset gives back:

modprobe: ERROR: could not insert 'vendor_reset': Key was rejected by service
I'm running latest Proxmox version 8.4.1, i can correctly passthrough my 2400GE iGPU to the Windows VM with error 43 currently

Does anyone ahve any leads on this? Also secure boot it's enabled on the host

Thanks in advance and have an happy easter!
 
modprobe: ERROR: could not insert 'vendor_reset': Key was rejected by service

Also secure boot it's enabled on the host
The error is typically because of secure boot, and the module is not signed maybe? I don't know how to fix this without disabling secure boot but maybe someone else knows. It's not specific to Proxmox so other Linux secure boot and dkms guides on the internet might help you.

EDIT: vendor-reset does not support the Vega 11 from your 2400GE, so it probably won't help in resetting the iGPU (which is always more problematic than a discrete GPU passthrough).
 
Last edited:
The error is typically because of secure boot, and the module is not signed maybe? I don't know how to fix this without disabling secure boot but maybe someone else knows. It's not specific to Proxmox so other Linux secure boot and dkms guides on the internet might help you.

Hello! Thanks for the reply

I can disable secure boot because this is for a home lab, i can disable secure boot after proxmox install? Will it boot?
 
If this was built with DKMS, your key should be in /var/lib/dkms/mok.pub - do mokutil import on that key, follow the instructions on reboot and your secure boot will work. Not a good idea to disable secure boot these days.
 
  • Like
Reactions: leesteken
If this was built with DKMS, your key should be in /var/lib/dkms/mok.pub - do mokutil import on that key, follow the instructions on reboot and your secure boot will work. Not a good idea to disable secure boot these days.

Hello!

Thanks for the heads up, i did the import but i guess i need to connect an external Monitor and do that on boot time, cannot do that from the shell

Now the system it's already rebooted, is there any way to force the MokAdmin to show at the next reboot?

Thanks!
 
You get about 20s to do it at the next boot, simply re-import before your next reboot and watch on console or IPMI.

THANKS! it worked! Finally the module it's loaded

However, i've passed the GPU to the Win11 Host and it worked.... the first time, as soon i've sutdown the VM the entire host crashed.... and the next time i've booted it i've got error 43 again

i really don't understand, for one time it worked....! Any ideas?