Trying to set up GPU passthrough for my RX 580

• Single-GPU-Passthrough

  207 1,396 3.4 Shell

First, I tried following this guide by u/Lellow_Yedbetter, as I was linked to it in one of Mutahar's videos. I installed the libvirt hook helper. Then I mkdir -p'd the directories /etc/libvirt/hooks/qemu.d/win10/prepare/begin and /etc/libvirt/hooks/qemu.d/{VM Name}/release/end. However, I was unsure about the start/stop scripts, as the guide said not to copy them. I was unsure about what to do, but I tried seeing what happened if I went ahead and copied them. I did this by using nano to create the script files(with the same names), copy/pasted the code into them, place the scripts at the aforementioned directories and chmod +x them. Lastly, I removed "Display Spice" and "Video Virtio" as it said how if you still have them you will get a black screen.

• single-gpu-passthrough

  175 - -

Second, I tried this guide, as the Archwiki linked me to it. I downloaded and unzipped the repo, cd'd into it, and ran sudo ./install_hooks.sh. I removed "Display Spice" and "Video Virtio" too. It worked exactly the same as with the other guide; it would show a black screen, and force-shutting off would blackscreen, before showing the display manager, which would black-screen upon logging in. I tried again but with Display Spice and Video(tried with both QXL and Virtio). This time, it would boot Windows and work, but it would not be using the GPU(GPU would not show up in Task Manager), and once again the host's graphics were still working. And shutting it off by clicking the Windows Shut Down button would make the entire screen black, before showing the display manager, which would black-screen upon logging in.

• WorkOS

  workos.com sponsored

  The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.

  

• vendor-reset

  143 701 0.0 C

  Linux kernel vendor specific hardware reset module for sequences that are too complex/complicated to land in pci_quirks.c

I used to have an RX580-based single GPU passthrough setup. You likely need the vendor reset module, since hot-plugging Polaris 10 GPUs is a bit buggy and can cause GPU lockups. It might also be worth dumping your GPU bios and configuring libvirt to use it so you get a visible boot screen (tool). I think I mostly followed this guide, however it hasn't been updated in quite a while it seems.

• amdvbflash

  8 45 0.0

I used to have an RX580-based single GPU passthrough setup. You likely need the vendor reset module, since hot-plugging Polaris 10 GPUs is a bit buggy and can cause GPU lockups. It might also be worth dumping your GPU bios and configuring libvirt to use it so you get a visible boot screen (tool). I think I mostly followed this guide, however it hasn't been updated in quite a while it seems.

• vfio

  76 - -

I used to have an RX580-based single GPU passthrough setup. You likely need the vendor reset module, since hot-plugging Polaris 10 GPUs is a bit buggy and can cause GPU lockups. It might also be worth dumping your GPU bios and configuring libvirt to use it so you get a visible boot screen (tool). I think I mostly followed this guide, however it hasn't been updated in quite a while it seems.

• InfluxDB

  www.influxdata.com sponsored

  Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.

  

Suggest a related project