Recent content by NetworkingMicrobe

Sorry I'm out of ideas then :( It seems to really be something with the driver not supporting VMs. Even on a Windows 10 VM, all I could see was my mouse moving as I moved it, but the entire rest of my screen was pixelated mess.

Saw this post on L1T as well, the last comment proposes a possible solution - https://forum.level1techs.com/t/radeon-vii-not-initialising-psp-fails/143654/2 Essentially requiring iommu=soft since there may be issues with AMD IOMMU drivers. Worth a try? Maybe with and without passing through the...

Never tried this, but it could be helpful: https://www.reddit.com/r/Proxmox/comments/l0cjve/solved_ryzen_apu_vaapi_decoding_on_proxmox/

@thex interesting output, thanks for sharing. I have no updates sadly, and as user avw wrote, it's likely that the drivers don't expect the iGPU in a VM. Also, I'm the user CodingMicrobe over on the Unraid forums ;) Having said that, the errors you are seeing are very curious. It looks like the...

I will look into those options. Thanks again for your time and help! Maybe one day a future driver will allow it to work with SeaBIOS so I could see more than jut a cursor moving around over pixelated output. Cheers!

I tried the options you suggested, and no real change. Screen still stuck on "Loading initial ramdisk" and I guess that means the VM can't "grab" control of the iGPU. Not sure if you saw my post above yours (#27), but at one point I did manage to get the VM to "grab" the iGPU I think, because...

Conversely, if I remove amdgpu from the pve-blacklist.conf file, and I remove the GPU and audio devcie from /etc/modprobe.d/vfio.conf (so it doesn't bint VFIO on boot), and I remove the video=efifb: off from /etc/default/grub -- then when I start my VM with OVMF, with or without VBIOS, the...

Looks like I was running 6.3-2 instead of latest 6.3-6, and now I see the option. Sorry about that, I just downloaded it so I thought I was latest but I guess not. Tried out OVMF (q35 5.1 and 5.2), can't even get it to initialize the iGPU, screen is still on "Loading initial ramdisk..." from...

I can't seem to find the option to switch to other q35 versions, either in the "create a VM" wizard, or the "hardware" tab once I made a VM, even with advanced enabled in the wizard... I also find it hard to believe that the VBIOS which I extracted from different BIOSes all say type 0, since...

The reason I went with SeaBIOS was because my VBIOS (which I don't pass through in the PCIe device declaration in PVE, since I found it made no difference) doesn't support UEFI. I tested using the guide in Proxmox forums here...

I've been doing a bit more digging and decided to run GPU-Z tool to get some detailed GPU info, on both W10 native and W10 guest VM on PVE. Results below, I highlighted the differences... (this was while connected to VM via RDP, not sure if that has an effect). Not sure why it says Bus is PCI...

Also I think motherboard is the deciding factor for IOMMU groups. In this case, I'm using the ASRock X300W DeskMini case/motherboard kit, there are no other PCIe slots, just a socket for the CPU and onboard audio. However, the AMD APUs shouls all look the same in terms of IOMMU groupings for...

Something else I noticed, although the screen looks very bad (again, see my previous comment above for a photo example), the mouse is still fully responsive and I see the cursor moving. Sometimes if I click enough randomly it will "crash" the driver and Code 43 will appear in Device Manager for...

I did get pass through working though, the problem arises when I install AMD drivers in the guest OS, then I see garbage output to VGA/HDMI/DP. And without drivers, very poor performance watching videos, moving windows around, etc.

My bad, I mistyped (clearly haven't had my morning coffee yet). I meant to say my IOMMU groups look the same in 5.11.7-1 as they do in the current stable kernel in PVE. Of course, if I turn ACS override ON then I see many more groups (9 total), since each device gets its own, as per my post...