RX5700XT Passthrough

pearce1340

By pearce1340
in VM Engine (KVM)

Recommended Posts

pearce1340 Noob

pearce1340

Posted
Posted

Hi All,

I have previously managed to pass-through my RX5700XT with success, but weirdly after losing a VM (Long Story) I tried to recreate it and now I'm stuck!

I've followed the guides and read various articles and topics on here... but really not sure whats going on.

I have tried running without the vbios and nothing happens on the output screen. When I try to use the vbios from techpowerup I get LOTS of errors like this as soon as I start the VM... these continue to the point where the server log fills: 

2020-04-29T20:25:33.942057Z qemu-system-x86_64: vfio_region_write(0000:0f:00.0:region0+0x12488, 0x0,8) failed: Device or resource busy
2020-04-29T20:25:33.942065Z qemu-system-x86_64: vfio_region_write(0000:0f:00.0:region0+0x12480, 0x0,8) failed: Device or resource busy
2020-04-29T20:25:33.942073Z qemu-system-x86_64: vfio_region_write(0000:0f:00.0:region0+0x12478, 0x0,8) failed: Device or resource busy
2020-04-29T20:25:33.942081Z qemu-system-x86_64: vfio_region_write(0000:0f:00.0:region0+0x12470, 0x0,8) failed: Device or resource busy
2020-04-29T20:25:33.942089Z qemu-system-x86_64: vfio_region_write(0000:0f:00.0:region0+0x12468, 0x0,8) failed: Device or resource busy
2020-04-29T20:25:33.942096Z qemu-system-x86_64: vfio_region_write(0000:0f:00.0:region0+0x13188, 0x0,8) failed: Device or resource busy
2020-04-29T20:25:33.942104Z qemu-system-x86_64: vfio_region_write(0000:0f:00.0:region0+0x13180, 0x0,8) failed: Device or resource busy
2020-04-29T20:25:33.942112Z qemu-system-x86_64: vfio_region_write(0000:0f:00.0:region0+0x13178, 0x0,8) failed: Device or resource busy
2020-04-29T20:25:33.942120Z qemu-system-x86_64: vfio_region_write(0000:0f:00.0:region0+0x13170, 0x0,8) failed: Device or resource busy
2020-04-29T20:25:33.942128Z qemu-system-x86_64: vfio_region_write(0000:0f:00.0:region0+0x13168, 0x0,8) failed: Device or resource busy

I would really appreciate any help anyone can provide as it looks like something else is trying to use the device.

Here is my XML for the Win 10 VM: 

<?xml version='1.0' encoding='UTF-8'?>
<domain type='kvm'>
  <name>Windows 10</name>
  <uuid>395b20ee-6cc4-6625-7e12-28813508df56</uuid>
  <metadata>
    <vmtemplate xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10"/>
  </metadata>
  <memory unit='KiB'>16777216</memory>
  <currentMemory unit='KiB'>4194304</currentMemory>
  <memoryBacking>
    <nosharepages/>
  </memoryBacking>
  <vcpu placement='static'>16</vcpu>
  <cputune>
    <vcpupin vcpu='0' cpuset='8'/>
    <vcpupin vcpu='1' cpuset='24'/>
    <vcpupin vcpu='2' cpuset='9'/>
    <vcpupin vcpu='3' cpuset='25'/>
    <vcpupin vcpu='4' cpuset='10'/>
    <vcpupin vcpu='5' cpuset='26'/>
    <vcpupin vcpu='6' cpuset='11'/>
    <vcpupin vcpu='7' cpuset='27'/>
    <vcpupin vcpu='8' cpuset='12'/>
    <vcpupin vcpu='9' cpuset='28'/>
    <vcpupin vcpu='10' cpuset='13'/>
    <vcpupin vcpu='11' cpuset='29'/>
    <vcpupin vcpu='12' cpuset='14'/>
    <vcpupin vcpu='13' cpuset='30'/>
    <vcpupin vcpu='14' cpuset='15'/>
    <vcpupin vcpu='15' cpuset='31'/>
  </cputune>
  <os>
    <type arch='x86_64' machine='pc-q35-4.2'>hvm</type>
    <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader>
    <nvram>/etc/libvirt/qemu/nvram/395b20ee-6cc4-6625-7e12-28813508df56_VARS-pure-efi.fd</nvram>
  </os>
  <features>
    <acpi/>
    <apic/>
    <hyperv>
      <relaxed state='on'/>
      <vapic state='on'/>
      <spinlocks state='on' retries='8191'/>
      <vendor_id state='on' value='none'/>
    </hyperv>
  </features>
  <cpu mode='host-passthrough' check='none'>
    <topology sockets='1' cores='8' threads='2'/>
    <cache mode='passthrough'/>
    <feature policy='require' name='topoext'/>
  </cpu>
  <clock offset='localtime'>
    <timer name='hypervclock' present='yes'/>
    <timer name='hpet' present='no'/>
  </clock>
  <on_poweroff>destroy</on_poweroff>
  <on_reboot>restart</on_reboot>
  <on_crash>restart</on_crash>
  <devices>
    <emulator>/usr/local/sbin/qemu</emulator>
    <disk type='file' device='disk'>
      <driver name='qemu' type='raw' cache='writeback'/>
      <source file='/mnt/user/domains/Windows 10/vdisk1.img'/>
      <target dev='hdc' bus='virtio'/>
      <boot order='1'/>
      <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/>
    </disk>
    <disk type='file' device='cdrom'>
      <driver name='qemu' type='raw'/>
      <source file='/mnt/user/isos/Windows 10 Pro/en-gb_windows_10_consumer_editions_version_1903_x64_dvd_44ca01a6.iso'/>
      <target dev='hda' bus='sata'/>
      <readonly/>
      <boot order='2'/>
      <address type='drive' controller='0' bus='0' target='0' unit='0'/>
    </disk>
    <disk type='file' device='cdrom'>
      <driver name='qemu' type='raw'/>
      <source file='/mnt/user/isos/virtio-win-0.1.173-2.iso'/>
      <target dev='hdb' bus='sata'/>
      <readonly/>
      <address type='drive' controller='0' bus='0' target='0' unit='1'/>
    </disk>
    <controller type='sata' index='0'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/>
    </controller>
    <controller type='pci' index='0' model='pcie-root'/>
    <controller type='pci' index='1' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='1' port='0x8'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0' multifunction='on'/>
    </controller>
    <controller type='pci' index='2' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='2' port='0x9'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/>
    </controller>
    <controller type='pci' index='3' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='3' port='0xa'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/>
    </controller>
    <controller type='pci' index='4' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='4' port='0xb'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x3'/>
    </controller>
    <controller type='pci' index='5' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='5' port='0xc'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x4'/>
    </controller>
    <controller type='pci' index='6' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='6' port='0xd'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x5'/>
    </controller>
    <controller type='virtio-serial' index='0'>
      <address type='pci' domain='0x0000' bus='0x02' slot='0x00' function='0x0'/>
    </controller>
    <controller type='usb' index='0' model='qemu-xhci' ports='15'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/>
    </controller>
    <interface type='bridge'>
      <mac address='52:54:00:bb:0e:f1'/>
      <source bridge='br0.6'/>
      <model type='virtio'/>
      <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/>
    </interface>
    <serial type='pty'>
      <target type='isa-serial' port='0'>
        <model name='isa-serial'/>
      </target>
    </serial>
    <console type='pty'>
      <target type='serial' port='0'/>
    </console>
    <channel type='unix'>
      <target type='virtio' name='org.qemu.guest_agent.0'/>
      <address type='virtio-serial' controller='0' bus='0' port='1'/>
    </channel>
    <input type='mouse' bus='ps2'/>
    <input type='keyboard' bus='ps2'/>
    <hostdev mode='subsystem' type='pci' managed='yes'>
      <driver name='vfio'/>
      <source>
        <address domain='0x0000' bus='0x0f' slot='0x00' function='0x0'/>
      </source>
      <rom file='/mnt/user/domains/ROMS/AMD.RX5700XT.8192.190616.rom'/>
      <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0'/>
    </hostdev>
    <hostdev mode='subsystem' type='pci' managed='yes'>
      <driver name='vfio'/>
      <source>
        <address domain='0x0000' bus='0x0f' slot='0x00' function='0x1'/>
      </source>
      <address type='pci' domain='0x0000' bus='0x05' slot='0x00' function='0x0'/>
    </hostdev>
    <hostdev mode='subsystem' type='usb' managed='no'>
      <source>
        <vendor id='0x046d'/>
        <product id='0xc52b'/>
      </source>
      <address type='usb' bus='0' port='1'/>
    </hostdev>
    <memballoon model='none'/>
  </devices>
</domain>

and here is my IOMMU Groups - 35 & 36 are the 2 groups for Graphics and Audio: 

IOMMU group 0:	[1022:1482] 00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge
IOMMU group 1:	[1022:1483] 00:01.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge
IOMMU group 2:	[1022:1483] 00:01.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge
IOMMU group 3:	[1022:1482] 00:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge
IOMMU group 4:	[1022:1482] 00:03.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge
IOMMU group 5:	[1022:1483] 00:03.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge
IOMMU group 6:	[1022:1482] 00:04.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge
IOMMU group 7:	[1022:1482] 00:05.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge
IOMMU group 8:	[1022:1482] 00:07.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge
IOMMU group 9:	[1022:1484] 00:07.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B]
IOMMU group 10:	[1022:1482] 00:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge
IOMMU group 11:	[1022:1484] 00:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B]
IOMMU group 12:	[1022:1484] 00:08.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B]
IOMMU group 13:	[1022:1484] 00:08.3 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B]
IOMMU group 14:	[1022:790b] 00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev 61)
[1022:790e] 00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev 51)
IOMMU group 15:	[1022:1440] 00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 0
[1022:1441] 00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 1
[1022:1442] 00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 2
[1022:1443] 00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 3
[1022:1444] 00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 4
[1022:1445] 00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 5
[1022:1446] 00:18.6 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 6
[1022:1447] 00:18.7 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 7
IOMMU group 16:	[1987:5016] 01:00.0 Non-Volatile memory controller: Phison Electronics Corporation E16 PCIe4 NVMe Controller (rev 01)
IOMMU group 17:	[1022:57ad] 02:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse Switch Upstream
IOMMU group 18:	[1022:57a3] 03:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge
IOMMU group 19:	[1022:57a3] 03:01.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge
IOMMU group 20:	[1022:57a3] 03:02.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge
IOMMU group 21:	[1022:57a3] 03:03.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge
IOMMU group 22:	[1022:57a3] 03:04.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge
IOMMU group 23:	[1022:57a3] 03:05.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge
IOMMU group 24:	[1022:57a4] 03:08.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge
[1022:1485] 0a:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Reserved SPP
[1022:149c] 0a:00.1 USB controller: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller
[1022:149c] 0a:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller
IOMMU group 25:	[1022:57a4] 03:09.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge
[1022:7901] 0b:00.0 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 51)
IOMMU group 26:	[1022:57a4] 03:0a.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge
[1022:7901] 0c:00.0 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 51)
IOMMU group 27:	[1987:5016] 04:00.0 Non-Volatile memory controller: Phison Electronics Corporation E16 PCIe4 NVMe Controller (rev 01)
IOMMU group 28:	[1987:5016] 05:00.0 Non-Volatile memory controller: Phison Electronics Corporation E16 PCIe4 NVMe Controller (rev 01)
IOMMU group 29:	[1b4b:9215] 06:00.0 SATA controller: Marvell Technology Group Ltd. Device 9215 (rev 11)
IOMMU group 30:	[1d6a:d107] 07:00.0 Ethernet controller: Aquantia Corp. AQC107 NBase-T/IEEE 802.3bz Ethernet Controller [AQtion] (rev 02)
IOMMU group 31:	[8086:1539] 08:00.0 Ethernet controller: Intel Corporation I211 Gigabit Network Connection (rev 03)
IOMMU group 32:	[8086:2723] 09:00.0 Network controller: Intel Corporation Wi-Fi 6 AX200 (rev 1a)
IOMMU group 33:	[1002:1478] 0d:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 XL Upstream Port of PCI Express Switch (rev c1)
IOMMU group 34:	[1002:1479] 0e:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 XL Downstream Port of PCI Express Switch
IOMMU group 35:	[1002:731f] 0f:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] (rev c1)
IOMMU group 36:	[1002:ab38] 0f:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 HDMI Audio
IOMMU group 37:	[1022:148a] 10:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Function
IOMMU group 38:	[1022:1485] 11:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Reserved SPP
IOMMU group 39:	[1022:1486] 11:00.1 Encryption controller: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Cryptographic Coprocessor PSPCPP
IOMMU group 40:	[1022:149c] 11:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller
IOMMU group 41:	[1022:1487] 11:00.4 Audio device: Advanced Micro Devices, Inc. [AMD] Starship/Matisse HD Audio Controller
IOMMU group 42:	[1022:7901] 12:00.0 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 51)
IOMMU group 43:	[1022:7901] 13:00.0 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 51)

Thanks in advance!

Steve

Link to comment
Salamy Noob

Salamy

Posted
Posted

Hi, i just started with unraid so i am far off from an expert.

 

here is my setup for an Ryzen 3600 System with a Radeon VII.

 

For my windows 10 VM i set the PCIE ACS Override to Downstream in the Settingsmenue for VM.

 

 

For the VM itself

OVMF 

unpin the first core and its smt counterpart

Q35

VMC

-> install windows and all of the drivers from the virtuell driver disk

-> do config of windows

After that Shutdown.

 

No i select my radeon as GPU

and the correct Vbios (with my Radeon VII i had Problems because i used the wrong version, so might be the case for 5700 aswell)

for example AMD.RX5700XT.8192.190616.rom  = Version 616 so if thats not the Vbios on your card it wont work

add my usb Mouse and Keyboard.

-> then try 

if that works i ad my GPU Sound aswell

 

Maybe that helps. Cant post my XML at the moment.

I Can if you want later.

 

Link to comment
bastl Collaborator

bastl

Posted
Posted

@pearce1340 I think you have to manual edit the xml and put the GPU+Audio on the same bus as multifunctional device if I remember correctly.

 

Try to replace the following part in the xml: 

    <hostdev mode='subsystem' type='pci' managed='yes'>
      <driver name='vfio'/>
      <source>
        <address domain='0x0000' bus='0x0f' slot='0x00' function='0x0'/>
      </source>
      <rom file='/mnt/user/domains/ROMS/AMD.RX5700XT.8192.190616.rom'/>
      <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0'/>
    </hostdev>
    <hostdev mode='subsystem' type='pci' managed='yes'>
      <driver name='vfio'/>
      <source>
        <address domain='0x0000' bus='0x0f' slot='0x00' function='0x1'/>
      </source>
      <address type='pci' domain='0x0000' bus='0x05' slot='0x00' function='0x0'/>
    </hostdev>

with this 

    <hostdev mode='subsystem' type='pci' managed='yes'>
      <driver name='vfio'/>
      <source>
        <address domain='0x0000' bus='0x0f' slot='0x00' function='0x0'/>
      </source>
      <rom file='/mnt/user/domains/ROMS/AMD.RX5700XT.8192.190616.rom'/>
      <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0' multifunction='on'/>
    </hostdev>
    <hostdev mode='subsystem' type='pci' managed='yes'>
      <driver name='vfio'/>
      <source>
        <address domain='0x0000' bus='0x0f' slot='0x00' function='0x1'/>
      </source>
      <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x1'/>
    </hostdev>

I defined the GPU as "multifunction" and placed the audio portion of the GPU on the same bus (bus='0x04') as the GPU with the function 1 (function='0x1').

Link to comment
  • 2 weeks later...
pearce1340 Noob

pearce1340

Posted
  • Author
Posted (edited)

@bastl, Thanks for your advice... I have made the changes, but still not getting an output on the screen:

 

I do however see this in the VM logs... not sure if that helps?

  

-chardev pty,id=charserial0 \
-device isa-serial,chardev=charserial0,id=serial0 \
-chardev socket,id=charchannel0,fd=40,server,nowait \
-device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 \
-device usb-tablet,id=input0,bus=usb.0,port=2 \
-device vfio-pci,host=0000:0f:00.0,id=hostdev0,bus=pci.9,multifunction=on,addr=0x0,romfile=/mnt/user/domains/ROMS/AMD.RX5700XT.8192.190616.rom \
-device vfio-pci,host=0000:0f:00.1,id=hostdev1,bus=pci.9,addr=0x0.0x1 \
-device usb-host,hostbus=1,hostaddr=6,id=hostdev2,bus=usb.0,port=1 \
-sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny \
-msg timestamp=on
2020-05-10 21:03:35.306+0000: Domain id=8 is tainted: high-privileges
2020-05-10 21:03:35.306+0000: Domain id=8 is tainted: host-cpu
char device redirected to /dev/pts/3 (label charserial0)
2020-05-10T21:03:50.773057Z qemu-system-x86_64: -device vfio-pci,host=0000:0f:00.0,id=hostdev0,bus=pci.9,multifunction=on,addr=0x0,romfile=/mnt/cache/domains/ROMS/AMD.RX5700XT.8192.190616.rom: Failed to mmap 0000:0f:00.0 BAR 0. Performance may be slow

The last few lines in particular are highlighted yellow. 

 

Sorry just to add to this, as I've been playing more. I reset my unraid box, because I know there is the reset bug and I wanted to eliminate that, even though I didn't get the normal error. I am now getting a new problem (I think) which is the following errors filling my VM Log, to the point that it quickly (very) fills all the system logs. Does this help determine what the issue may be?

  

2020-05-10T21:12:02.205709Z qemu-system-x86_64: vfio_region_write(0000:0f:00.0:region0+0x182550, 0xff000000ff000000,8) failed: Device or resource busy
2020-05-10T21:12:02.205716Z qemu-system-x86_64: vfio_region_write(0000:0f:00.0:region0+0x182558, 0xff000000ff000000,8) failed: Device or resource busy
2020-05-10T21:12:02.205724Z qemu-system-x86_64: vfio_region_write(0000:0f:00.0:region0+0x182540, 0xff000000ff000000,8) failed: Device or resource busy
2020-05-10T21:12:02.205731Z qemu-system-x86_64: vfio_region_write(0000:0f:00.0:region0+0x182548, 0xff000000ff000000,8) failed: Device or resource busy
2020-05-10T21:12:02.205739Z qemu-system-x86_64: vfio_region_write(0000:0f:00.0:region0+0x182530, 0xff000000ff000000,8) failed: Device or resource busy
2020-05-10T21:12:02.205746Z qemu-system-x86_64: vfio_region_write(0000:0f:00.0:region0+0x182538, 0xff000000ff000000,8) failed: Device or resource busy
2020-05-10T21:12:02.205754Z qemu-system-x86_64: vfio_region_write(0000:0f:00.0:region0+0x182520, 0xff000000ff000000,8) failed: Device or resource busy
2020-05-10T21:12:02.205760Z qemu-system-x86_64: vfio_region_write(0000:0f:00.0:region0+0x182528, 0xff000000ff000000,8) failed: Device or resource busy
2020-05-10T21:12:02.205768Z qemu-system-x86_64: vfio_region_write(0000:0f:00.0:region0+0x182518, 0xff000000ff000000,8) failed: Device or resource busy
2020-05-10T21:12:02.205778Z qemu-system-x86_64: vfio_region_write(0000:0f:00.0:region0+0x18325c, 0xff000000,4) failed: Device or resource busy
2020-05-10T21:12:02.205782Z qemu-system-x86_64: vfio_region_write(0000:0f:00.0:region0+0x183260, 0xff000000,4) failed: Device or resource busy
2020-05-10T21:12:02.205788Z qemu-system-x86_64: vfio_region_write(0000:0f:00.0:region0+0x183264, 0xff000000,4) failed: Device or resource busy
2020-05-10T21:12:02.205793Z qemu-system-x86_64: vfio_region_write(0000:0f:00.0:region0+0x183268, 0xff000000,4) failed: Device or resource busy
2020-05-10T21:12:02.205800Z qemu-system-x86_64: vfio_region_write(0000:0f:00.0:region0+0x183250, 0xff000000ff000000,8) failed: Device or resource busy
2020-05-10T21:12:02.205808Z qemu-system-x86_64: vfio_region_write(0000:0f:00.0:region0+0x183258, 0xff000000ff000000,8) failed: Device or resource busy
2020-05-10T21:12:02.205819Z qemu-system-x86_64: vfio_region_write(0000:0f:00.0:region0+0x183240, 0xff000000ff000000,8) failed: Device or resource busy
2020-05-10T21:12:02.205825Z qemu-system-x86_64: vfio_region_write(0000:0f:00.0:region0+0x183248, 0xff000000ff000000,8) failed: Device or resource busy
2020-05-10T21:12:02.205834Z qemu-system-x86_64: vfio_region_write(0000:0f:00.0:region0+0x183230, 0xffafafafff7f7f7f,8) failed: Device or resource busy
2020-05-10T21:12:02.205840Z qemu-system-x86_64: vfio_region_write(0000:0f:00.0:region0+0x183238, 0xff000000ff0f0f0f,8) failed: Device or resource busy
2020-05-10T21:12:02.205848Z qemu-system-x86_64: vfio_region_write(0000:0f:00.0:region0+0x183220, 0xff000000ff000000,8) failed: Device or resource busy
2020-05-10T21:12:02.205855Z qemu-system-x86_64: vfio_region_write(0000:0f:00.0:region0+0x183228, 0xff000000ff000000,8) failed: Device or resource busy
2020-05-10T21:12:02.205863Z qemu-system-x86_64: vfio_region_write(0000:0f:00.0:region0+0x183218, 0xff000000ff000000,8) failed: Device or resource busy
2020-05-10T21:12:02.205871Z qemu-system-x86_64: vfio_region_write(0000:0f:00.0:region0+0x183f5c, 0xff000000,4) failed: Device or resource busy
2020-05-10T21:12:02.205875Z qemu-system-x86_64: vfio_region_write(0000:0f:00.0:region0+0x183f60, 0xff000000,4) failed: Device or resource busy
2020-05-10T21:12:02.205881Z qemu-system-x86_64: vfio_region_write(0000:0f:00.0:region0+0x183f64, 0xff000000,4) failed: Device or resource busy
2020-05-10T21:12:02.205886Z qemu-system-x86_64: vfio_region_write(0000:0f:00.0:region0+0x183f68, 0xff000000,4) failed: Device or resource busy
2020-05-10T21:12:02.205893Z qemu-system-x86_64: vfio_region_write(0000:0f:00.0:region0+0x183f50, 0xff000000ff000000,8) failed: Device or resource busy

 

Thanks,
Steve

Edited by pearce1340
Link to comment
  • 3 weeks later...
SpaceInvaderOne Community Regular

SpaceInvaderOne

Posted
Posted

Have you updated the motherboard bios then since doing this the vm no longer works?

This was a problem with ryzen cpus when the 3000 series came out and people updated their bios when their cpu was not a 3000 series. Then black screen on gpu.

I made a video about it here https://www.youtube.com/watch?v=l-WHCCwgyDg&feature=emb_logo

 

If that was the case you can try to downgrade the bios using this video here https://www.youtube.com/watch?v=ZzqwjVDKAnU

 

Link to comment
pearce1340 Noob

pearce1340

Posted
  • Author
Posted

Hi @SpaceInvaderOne!

 

Yes I did update the BIOS, but it was pretty unstable before. I have a Aurus X570 Xtreme with a Ryzen 3950X.

 

I have however managed to get a step further... I have booted my server in Legacy mode and now the passthrough is working. However even after a smooth shutdown and no 127 (Reset bug error) I get a black screen on reboot. 

 

I seem to have to reboot the whole server to get it to work again, even with your standby script. I have also tried removing the VBIOS from the passthrough and trying that... which caused a log issue and then corrupted my BTRFS cache.

 

Kind of regretting buying this card lol.

 

Would welcome your ideas?


Thanks,
Steve

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
Go to topic listing