@wendell Yeah, both the 970 and the audio. I resat it a slot below my host GPU, gave the boot script the new prefixes and things are different:
Error starting domain: internal error: Process exited prior to exec: libvirt: QEMU Driver error : Unable to stat /dev/dri/by-path/pci-0000:41:00.0-render: No such file or directory
Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/asyncjob.py", line 75, in cb_wrapper
callback(asyncjob, *args, **kwargs)
File "/usr/share/virt-manager/virtManager/asyncjob.py", line 111, in tmpcb
callback(*args, **kwargs)
File "/usr/share/virt-manager/virtManager/libvirtobject.py", line 66, in newfn
ret = fn(self, *args, **kwargs)
File "/usr/share/virt-manager/virtManager/domain.py", line 1400, in startup
self._backend.create()
File "/usr/lib/python3/dist-packages/libvirt.py", line 1080, in create
if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self)
libvirt.libvirtError: internal error: Process exited prior to exec: libvirt: QEMU Driver error : Unable to stat /dev/dri/by-path/pci-0000:41:00.0-render: No such file or directory
Maybe I’m writing my bind_vfio script incorrectly? Here’s mine:
#!/bin/sh
PREREQS=""
DEVS="0000:41:00.0 0000:41:00.1"
for DEV in $DEVS;
do echo "vfio-pci" > /sys/bus/pci/devices/$DEV/driver_override
done
modprobe -i vfio-pci
Both the VGA and audio device are being used by vfio-pci too.
unfortunately there’s no further folder in the dev/dri/by-path folder but those two entries, but i can find it in the /sys/bus/pci/devices path. For context I added the GPU via the virt-manager GUI, in the config file though, would I replace
that’s a big mistake here’s my config, i’ve removed the spice display and QXL video adapter, and it’s unfortunately back to square 1 with booting and nothing happening: https://pastebin.com/raw/9LnMDzZs
still 127 error. I have a monitor plugged into the 970 via displayport but I’ve just found that my system is completely freezing when the display is turned on during boot… sheesh, i’ve got vfio, vfio_iommu_type1, vfio_virqfd, and vfio_pci in the initramfs-tools modules file and Nouveau is blacklisted but gdm still tries to load Nouveau
So since last night, I’ve followed that guide with a new vm, I’ve managed to fix the blacklisting issue, eventually I started applying a vbios in the rom which started some apparmor complaints, that’s fixed, but now I’m still at square one: The VM boots, but the GPU does nothing. Here’s my current config
On the topic of the BIOS, I did try downgrading my BIOS to 1.50 and redoing it’s settings, but that’s also done nothing, is the latest BIOS any worth it?
Greetings, I’m following your guide, and I must say that it’s very comprehensive. However, I’m having a problem: when I rebooted after configuring the bind_vfio.sh, I’m hit with a blank screen. Fortunately, switching to an earlier kernel lets me use my PC without any problem. My bind_vfio.sh looks like this:
PREREQS=""
DEVS=“0000:0b:00.0 0000:0b:00.1”
for DEV in $DEVS;
do echo “vfio-pci” > /sys/bus/pci/devices/$DEV/driver_override
done
modprobe -i vfio-pci
My pc has a ryzen 5 3600, a rx 480 (which I want to pass through to my vm) and a r7 260x. My motherboard is an asrock b450 steel legend. I’m quite sure I have followed every instruction up to that point.
@wendell I like to write comprehensive guides & tutorials. Would you have any problem with me using yours as a point of reference? I can credit you if you like.
I’m an active member over on the LTT Forums. I know >99% of their demographic won’t have a use for this but I’d like to spread the information none-the-less.
here’s my config, i’ve removed the spice display and QXL video adapter, and it’s unfortunately back to square 1 with booting and nothing happening: 
would you do that on host launch or guest launch?