Kemu GPU passthrough to W7 VM - Radeon RX 570

**ODTech** · December 3rd, 2017

I just noticed the jacob ppa also has a version of virt-manager and libvirt so i guess it's worth a try to update those two packages from the ppa too.

**KillerKelvUK** · December 3rd, 2017

Okay so I think you cracked it with your test scenario #3...

3. New VM (virt-manager, Q35, OVMF) – Finally managed to install UEFI W7. Knew about the boot manager but my images must’ve been the problem. Removed VGA and Spice display. Windows stuck at boot logo but clearly getting output from HDMI / RX 570.

Windows 7 doesn't boot as a KVM guest using Q35, OVMF and QXL gfx...were you attempting to setup the guest OS before adding in the pass through card? Switch to W10 and I'm guessing this scenario will work?

**jayz99** · December 3rd, 2017

uname -a
Code:
Linux X 4.10.0-40-generic #44-Ubuntu SMP Thu Nov 9 14:49:09 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
Thanks! I'll check it out and report back.

**jayz99** · December 6th, 2017

OK so I tried this:

1. i440fx, OVMF -> installed W7 previously but it did not work. Upgraded to W10 - GPU recognised, output on HDMI but suddenly the system froze and a few seconds the host died too. It seems this behaviour might be related to the "Windows (10?) guest freezes entire host on shutdown if using PCI passthrough" bug. See the host syslog below.

2. Q35, OVMF -> fresh install of W7 does not boot. This happens during the very first HDD boot, immediately post install.

3. Q35, OVMF -> fresh install of W10. Crashed immediately post driver installation. Upon VGA/display removal, boots up fine but stays on desktop for 10-15 seconds and BSOD stating video tdr failure as the reason. I've added a TdrDelay=8 value to W10 registry to give the GPU a grace period to respond - didn't help. Tried minimal and full Radeon driver install.

4. Kernel update to 4.14 and motherboard UEFI update (to get AGESA 1.0.0.6+). Using VM config from (3) above, I'm pleasantly surprised to report that this seems to have done the trick! I clocked 10 min in W10 and saw no problems with my RX 570 being recognized and used by the system! [Btw. I also disabled the AMD Event Service in W10 previously] I'll do some thorough testing tomorrow and report back.

I really appreciate your help - thank you!

Syslog:

Code:

Dec  5 21:50:59 BlueRidge kernel: [ 1850.863186] audit: type=1400 audit(1512510659.957:29): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-4553eac9-6699-49d6-b9e7-d520945250dc" pid=4435 comm="apparmor_parser"
Dec  5 21:50:59 BlueRidge libvirtd[1211]: Domain id=2 name='Win7VM' uuid=4553eac9-6699-49d6-b9e7-d520945250dc is tainted: host-cpu
Dec  5 21:51:00 BlueRidge libvirtd[1211]: internal error: unknown CPU feature __kvm_hv_spinlocks
Dec  5 21:51:00 BlueRidge virtlogd[3211]: End of file while reading data: Input/output error
Dec  5 21:51:00 BlueRidge virt-manager[3151]: Drawing a gadget with negative dimensions. Did you forget to allocate a size? (node box owner virtManager+autodrawer+AutoDrawer)
Dec  5 21:51:01 BlueRidge virt-manager[3151]: message repeated 5 times: [ Drawing a gadget with negative dimensions. Did you forget to allocate a size? (node box owner virtManager+autodrawer+AutoDrawer)]
Dec  5 21:51:01 BlueRidge avahi-daemon[1100]: Joining mDNS multicast group on interface vnet0.IPv6 with address fe80::fc54:ff:fe35:b34e.
Dec  5 21:51:01 BlueRidge avahi-daemon[1100]: New relevant interface vnet0.IPv6 for mDNS.
Dec  5 21:51:01 BlueRidge avahi-daemon[1100]: Registering new address record for fe80::fc54:ff:fe35:b34e on vnet0.*.
Dec  5 21:51:01 BlueRidge virt-manager[3151]: Drawing a gadget with negative dimensions. Did you forget to allocate a size? (node box owner virtManager+autodrawer+AutoDrawer)
Dec  5 21:51:01 BlueRidge kernel: [ 1852.587935] virbr0: port 2(vnet0) entered learning state
Dec  5 21:51:03 BlueRidge virt-manager[3151]: message repeated 75 times: [ Drawing a gadget with negative dimensions. Did you forget to allocate a size? (node box owner virtManager+autodrawer+AutoDrawer)]
Dec  5 21:51:03 BlueRidge NetworkManager[1097]: <info>  [1512510663.7020] device (virbr0): link connected
Dec  5 21:51:03 BlueRidge kernel: [ 1854.604070] virbr0: port 2(vnet0) entered forwarding state
Dec  5 21:51:03 BlueRidge kernel: [ 1854.604072] virbr0: topology change detected, propagating
Dec  5 21:51:04 BlueRidge virt-manager[3151]: Drawing a gadget with negative dimensions. Did you forget to allocate a size? (node box owner virtManager+autodrawer+AutoDrawer)
Dec  5 21:51:09 BlueRidge virt-manager[3151]: message repeated 51 times: [ Drawing a gadget with negative dimensions. Did you forget to allocate a size? (node box owner virtManager+autodrawer+AutoDrawer)]
Dec  5 21:51:09 BlueRidge systemd[1]: Reloading.
Dec  5 21:51:10 BlueRidge virt-manager[3151]: Drawing a gadget with negative dimensions. Did you forget to allocate a size? (node box owner virtManager+autodrawer+AutoDrawer)
Dec  5 21:51:13 BlueRidge virt-manager[3151]: message repeated 35 times: [ Drawing a gadget with negative dimensions. Did you forget to allocate a size? (node box owner virtManager+autodrawer+AutoDrawer)]
Dec  5 21:51:13 BlueRidge dnsmasq-dhcp[1858]: DHCPDISCOVER(virbr0) 52:54:00:35:b3:4e
Dec  5 21:51:13 BlueRidge dnsmasq-dhcp[1858]: DHCPOFFER(virbr0) 192.168.122.91 52:54:00:35:b3:4e
Dec  5 21:51:13 BlueRidge dnsmasq-dhcp[1858]: DHCPREQUEST(virbr0) 192.168.122.91 52:54:00:35:b3:4e
Dec  5 21:51:13 BlueRidge dnsmasq-dhcp[1858]: DHCPACK(virbr0) 192.168.122.91 52:54:00:35:b3:4e Win7VM
Dec  5 21:51:14 BlueRidge virt-manager[3151]: Drawing a gadget with negative dimensions. Did you forget to allocate a size? (node box owner virtManager+autodrawer+AutoDrawer)
Dec  5 21:51:16 BlueRidge virt-manager[3151]: message repeated 8 times: [ Drawing a gadget with negative dimensions. Did you forget to allocate a size? (node box owner virtManager+autodrawer+AutoDrawer)]
Dec  5 21:51:16 BlueRidge dnsmasq-dhcp[1858]: DHCPINFORM(virbr0) 192.168.122.91 52:54:00:35:b3:4e
Dec  5 21:51:16 BlueRidge dnsmasq-dhcp[1858]: DHCPACK(virbr0) 192.168.122.91 52:54:00:35:b3:4e Win7VM
Dec  5 21:51:16 BlueRidge virt-manager[3151]: Drawing a gadget with negative dimensions. Did you forget to allocate a size? (node box owner virtManager+autodrawer+AutoDrawer)
Dec  5 21:51:32 BlueRidge virt-manager[3151]: message repeated 378 times: [ Drawing a gadget with negative dimensions. Did you forget to allocate a size? (node box owner virtManager+autodrawer+AutoDrawer)]

**jayz99** · December 7th, 2017

Confirmed. The above solution worked. Passthrough fully functional. Recap of what is needed and why for others reading through the thread:

1. IOMMU / AMD-Vi enabled in order to pass through physical devices.
2. Driver blacklisting and VFIO-PCI used to capture and segregate the GPU at boot.
3. Q35 chipset for VM - better for modern systems.
4. OVMF (UEFI) - better than BIOS/SeaBIOS due to VGA arbitration at boot.
5. Motherboard software - must support AGESA 1.0.0.6 or higher. This means your UEFI/BIOS must have been updated post May 2017.
6. Linux kernel - use 4.12 or higher.
7. Windows 10 used as guest OS due to better support of the above technologies.

ODTech and KillerKelvUK - thank you again for your help!

Thanks & pozdrowienia,
Janusz