Search results for query: vendor-reset

...will test if this is actually working. Edit for quick update: without doing any troubleshooting at all, all I can say is that the vendor-reset kernel module does not work on my AMD Ryzen 5. lsmod shows the module being loaded, but after a shutdown of my Win11 VM, it doesn't claim the monitor...

vendor-reset has indeed not been updated for recent kernels, but you can fix the source code yourself: https://github.com/gnif/vendor-reset/pull/103 EDIT: A simpler manual fix is also possible as shown in one of the issues/PRs but maybe switching to the branch mentioned above is the easiest?

@jaminmc what kernel / pve are you using? The repo you mentioned fails to compile on most kernel 6.17.2. Is this method of running the vendor reset module the "official" one?

I’m using https://github.com/gnif/vendor-reset/ to achieve perfect resets on my Vega64 and APU in my Ryzen 7 9700x. However, I’m hoping to create a hook script that will return a GPU to amdgpu after the VM is stopped, so I’ll give a similar script a shot.

I don't think setting vendor-reset will have any effect on Navi33 (RDNA3). That generation will likely use a bus reset. * I think it's probably a bus reset for RDNA2 and later. cat "/sys/bus/pci/devices/0000:03:00.0/reset_method" https://github.com/gnif/vendor-reset We'll need to...

...to the GPU gets stuck in a bad PCIe state. From what I see above Proxmox itself is fine, the issue can be with Linux’s amdgpu driver. You can try to enable BIOS options like Above 4G Decoding/Resizable BAR and loading the vendor-reset kernel module on the host to improve GPU reset handling.

I see! Thank you both for the additional advice!! I'll remove the parameters you pointed out.

Is vendor-reset active? Do you see messages in the System logs about reset and NAVI10? Nevermid, your last post mentions that it's working. BTW: amd_iommu=on does nothing and video=efifb:off does nothing on Proxmox. EDIT: amd_iommu=on does not exist and is actually invalid...

...pcie_aspm=off pci=noaer" to remove outdated parameters and apply settings that improve PCIe stability on newer kernels. 2. Moved `vendor-reset` to the top of `/etc/modules`, then ran: update-grub && update-initramfs -k all -u and restart the host. 3. Changed BIOS IOMMU from Auto to...

Unfortunately, I don't have an environment that requires a vendor reset, so I'm afraid I can't help. *At least RDNA2 or later is not required. The following seem to cover similar issues, so I suggest trying them one by one...

Thank you for your advice. I installed vendor-reset, but it still hasn't fixed the issue. I also tried applying it after rebooting using commands like `echo vendor-reset >> /etc/modules-load.d/vendor-reset.conf`, but it didn't work. I would greatly appreciate it if you could tell me how to fix...

Runing latest Proxmox 9.1, no-subscription Dmesg Log: [Thu Nov 27 14:18:42 2025] vfio-pci 0000:03:00.0: vgaarb: VGA decodes changed: olddecodes=io+mem,decodes=io+mem:owns=io [Thu Nov 27 14:18:42 2025] xe 0000:03:00.0: [drm] Running in SR-IOV PF mode [Thu Nov 27 14:18:42 2025] xe 0000:03:00.0...

Did you install and enable vendor-reset: https://github.com/gnif/vendor-reset ? If not, you might wan to look into it (lots of threads on this forum and the internet) for properly resetting Radeon 5700 GPUs. x-vga=1 (Primary GPU) is for NVidia and should usually not be enabled for AMD GPUs.

Hi, I can't get my CX-6 LX to work with SR_IOV and Proxmox 9.1.1. SR_IOV is enabled in the motherboard BIOS and in the card's firmware, and I'm using this UDEV rule. ACTION=="add", SUBSYSTEM=="net", ATTRS{vendor}=="0x15b3", ATTRS{device}=="0x101f", ATTR{device/sriov_drivers_autoprobe}="0"...

I understand, that the Setup on the host side is not optimal. My goal is to fix the Windows driver side first. I can move the VM onto other disk later. But the speed is far away from what it should be . Even with ZFS slowing us down. root@pve:~# smartctl -a /dev/nvme0n1 smartctl 7.4...

...reboots of the VM, the monitor shows the loading bar of the UEFI boot screen and nothing else I suspect the second issue is due to the vendor-reset bug, but looking for support on resolving both. Below are my settings / process. 1. I followed...

I've installed Windows 11 25H2 onto a fresh ProxMox 9 installation, installed the latest VirtIO drivers and successfully passed through my Nvidia RTX 4070 Super GPU into the VM and installed the latest GPU drivers from Nvidia. Everything appears as expected while accessing through the Proxmox...

...|| true sleep 1 # Kurze Pause # GPU auf dem Host initialisieren (genau wie in Ihrem manuellen Script) nvidia-smi || true log "GPU erfolgreich an Host zurückgegeben." ;; esac exit 0 There is no vendor-reset like for AMD GPUs for NVIDIA is it?

istgt.conf Issue This issue is best shown by a diff after creating one single vm using zfs over iscsi. This only affects the section "[LogicalUnit1]", which is my last section and all sections above remain unchanged in the file: ➜ diff istgt.conf istgt.conf.before.delete 111,118c111,168 <...

This is from backup log: NFO: Starting Backup of VM 102 (qemu) INFO: Backup started at 2025-10-27 03:27:26 INFO: status = stopped INFO: backup mode: stop INFO: ionice priority: 7 INFO: VM Name: ************ INFO: include disk 'virtio0' 'vmdisk:102/vm-102-disk-2.raw' 104G INFO: include disk...