CodingMicrobe

@bigbangus wondering if you've had any progress on this issue? I upgrades from 6.9.2 to 6.10-rc3 yesterday and while everything else works fine, suddenly my GTX 760 GPU which is being used for my Windows 10 VM is throwing error 43, and VM is stuck at 800x600 resolution. I tried reinstalling Nvidia drivers (v470), which now officially support virtualization, without any success. Also made a brand new Windows 10 VM, same issue.

Yeah. That’s what I had working (with monitor connected to my system with only APU graphics, no other GPU), even in a VM, until I installed AMD drivers then it broke partially. good luck with testing Parsec, just keep in mind you may not get true graphics acceleration.

Interesting because I have tried that version I posted several times and no success once drivers are installed. Can you text with a monitor? I feel like you are in the same situation we are in, but the issue is masked by the fact you’re running it headless.

Hi, could you please share your XML and what changes were required in Unraid, beyond ACS override, efifb, VFIO. Also does the VM still work with AMD drivers installed? the issues we were having was with display output, since once you connect via RDP/parsec windows may use the generic drivers and not AMD. worth testing with a monitor if possible.

I have given up for now since it really does seem like something is wrong upon installing the AMD drivers and that is beyond me on how to fix.

I have tried with Ubuntu 20.04.2 and 20.10, but couldn't get either to work, even after enabling the amdgpu.exp_hw_support=1 flag in the kernel & updating krub accordingly... Similar issue with Manjaro XFCE 20.2.1. I have not tried Linux Mint.

I have narrowed it down to AMD drivers which are automatically installed by Windows Update. I can "Pause Updates for 7 days" in W10, but that's like putting a bandage on a bleeding wound, doesn't do much long-term. I am looking into why this may be occurring, however also came across these posts on Reddit where people point out that it may be a driver version issue, since AMD may be detecting VMs and not allowing us to run the driver properly. For what it's worth, the mouse usually works fine and I can move it around and see it on my display, everything 'behind' the mouse (the entire W10 UI) is that garbled pixelated mess though.

UPDATE: got it working very well on Unraid! Very easy to setup once I knew what to look for and the little 'tricks' to be careful for. Just playing around with it a bit further to ensure it's stable, but I will be very happy to share a guide shortly! Do you think I should make a post of its own for that? EDIT: Well, it was working before this happened and persisted after a reboot. No idea what changed unless Windows tried to pull drivers in the background which messed things up?

I got iGPU passthrough (with audio over HDMI as well, did not test display port yet) working in a Proxmox Windows 10 VM! Seems to be limited to ~30hz refresh rate but I am investigating if AMD driver updates will fix the issue. I will test on Unraid in the coming days once I am happy with the Proxmox install. But briefly, what was key was passing the VBIOS file (latest version works fine, see file Renoir-017.010.000.028.000000.ROM from previous post), AND using a q35 machine (not default i440fx) with SeaBIOS (NOT OVMF). I will try to get it working on Unraid soon and make a guide, but will also make a guide for Proxmox for those who use PVE. Cheers!

Thank you for trying and reporting back. My APU arrives tomorrow so we will see how that goes!

Once my APU arrives, I'll be trying with Proxmox which also uses KVM, just like Unraid. I am hopeful I can get it to work there, and if so, I'll definitely port it over to Unraid. Might take a couple weeks though.

Hello, I had more discussion with other users from other forums and the version of VBIOS (or from which motherboard it came) shouldn't matter. These are the 3 versions I have extracted, 017.010.000.015, 017.010.000.026, 017.010.000.028. Same as I posted above just renamed properly for their versions. Renoir-017.010.000.015.000000.ROM Renoir-017.010.000.026.000000.ROM Renoir-017.010.000.028.000000.ROM

I believe once you set it for a VM, you cannot easily change it (for Windows VM at least, not sure about other distros of Linux). There is a way to change SeaBIOS to OVMF, but the opposite is much more difficult/impossible - and I think you would just need to make a new VM, at least for testing purposes now.

Might be worth trying to run these commands on the Unraid server immediately upon bootup (via SSH! or userscripts plugin), and THEN starting the VM via web UI from another computer. Very important not to use unraid GUI mode or text mode at all. echo 0 > /sys/class/vtconsole/vtcon0/bind echo 0 > /sys/class/vtconsole/vtcon1/bind echo efi-framebuffer.0 > /sys/bus/platform/drivers/efi-framebuffer/unbind Also are you running the VM with SeaBIOS or OVMF? I think SeaBIOS is preferred for this type of pass-through, since the VBIOSs provided by AMD don't support UEFI firmware (which is what OVMF is).

Good point, I will try to make a guide within a few days!