pearce1340

Hi All, A bit of help please. I have my RX 5700 XT GPU Passthrough to a Win11 VM (fresh install). The actual card is working fine and I have the vendor reset in place (can restart multiple times with no issues). When I try to install the AMD Drivers using the software from AMD's site, I get the following error. I don't have this issue on my other VM, so I think I've missed something simple. I keep going through my XML and can't see it. Can I ask for a bit of help/advice? Below is my XML <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm'> <name>Windows 11 - Gaming</name> <uuid>4915030b-662b-282f-044b-76d025e99aa7</uuid> <metadata> <vmtemplate xmlns="unraid" name="Windows 11" icon="windows11.png" os="windowstpm"/> </metadata> <memory unit='KiB'>16777216</memory> <currentMemory unit='KiB'>16777216</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>24</vcpu> <cputune> <vcpupin vcpu='0' cpuset='4'/> <vcpupin vcpu='1' cpuset='20'/> <vcpupin vcpu='2' cpuset='5'/> <vcpupin vcpu='3' cpuset='21'/> <vcpupin vcpu='4' cpuset='6'/> <vcpupin vcpu='5' cpuset='22'/> <vcpupin vcpu='6' cpuset='7'/> <vcpupin vcpu='7' cpuset='23'/> <vcpupin vcpu='8' cpuset='8'/> <vcpupin vcpu='9' cpuset='24'/> <vcpupin vcpu='10' cpuset='9'/> <vcpupin vcpu='11' cpuset='25'/> <vcpupin vcpu='12' cpuset='10'/> <vcpupin vcpu='13' cpuset='26'/> <vcpupin vcpu='14' cpuset='11'/> <vcpupin vcpu='15' cpuset='27'/> <vcpupin vcpu='16' cpuset='12'/> <vcpupin vcpu='17' cpuset='28'/> <vcpupin vcpu='18' cpuset='13'/> <vcpupin vcpu='19' cpuset='29'/> <vcpupin vcpu='20' cpuset='14'/> <vcpupin vcpu='21' cpuset='30'/> <vcpupin vcpu='22' cpuset='15'/> <vcpupin vcpu='23' cpuset='31'/> </cputune> <os> <type arch='x86_64' machine='pc-q35-7.2'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi-tpm.fd</loader> <nvram>/etc/libvirt/qemu/nvram/4915030b-662b-282f-044b-76d025e99aa7_VARS-pure-efi-tpm.fd</nvram> </os> <features> <acpi/> <apic/> <hyperv mode='custom'> <relaxed state='on'/> <vapic state='on'/> <spinlocks state='on' retries='8191'/> <vendor_id state='on' value='123456789123'/> </hyperv> <kvm> <hidden state='on'/> </kvm> <vmport state='off'/> <ioapic driver='kvm'/> </features> <cpu mode='host-passthrough' check='none' migratable='on'> <topology sockets='1' dies='1' cores='12' 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 11 - Gaming/vdisk1.img'/> <target dev='hdc' bus='virtio'/> <serial>vdisk1</serial> <boot order='2'/> <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 11/en-gb_windows_11_business_editions_updated_april_2022_x64_dvd_1c55c769.iso'/> <target dev='hda' bus='sata'/> <readonly/> <boot order='1'/> <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.240-1.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='0x10'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0' multifunction='on'/> </controller> <controller type='pci' index='2' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='2' port='0x11'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x1'/> </controller> <controller type='pci' index='3' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='3' port='0x12'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x2'/> </controller> <controller type='pci' index='4' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='4' port='0x13'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x3'/> </controller> <controller type='pci' index='5' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='5' port='0x14'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x4'/> </controller> <controller type='pci' index='6' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='6' port='0x15'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' 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:59:ff:b8'/> <source bridge='br0.6'/> <model type='virtio-net'/> <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='tablet' bus='usb'> <address type='usb' bus='0' port='5'/> </input> <input type='mouse' bus='ps2'/> <input type='keyboard' bus='ps2'/> <tpm model='tpm-tis'> <backend type='emulator' version='2.0' persistent_state='yes'/> </tpm> <graphics type='vnc' port='-1' autoport='yes' websocket='-1' listen='0.0.0.0' keymap='en-gb'> <listen type='address' address='0.0.0.0'/> </graphics> <audio id='1' type='none'/> <video> <model type='qxl' ram='65536' vram='65536' vgamem='16384' heads='1' primary='yes'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0'/> </video> <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/isos/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> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x046d'/> <product id='0xc52b'/> </source> <address type='usb' bus='0' port='1'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x0b05'/> <product id='0x190e'/> </source> <address type='usb' bus='0' port='2'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x0e8d'/> <product id='0x1806'/> </source> <address type='usb' bus='0' port='3'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x8087'/> <product id='0x0029'/> </source> <address type='usb' bus='0' port='4'/> </hostdev> <memballoon model='none'/> </devices> </domain>

Yes I do. It downloads it from the cloud, unlocks the array and starts the array, then deletes itself. do I need to disable the script to allow formatting?

Hi, I was following a guide in order to convert one of my drives to ZFS. It was previously XFS Encrypted. I erased the disk and changed the type to ZFS Encrypted, however now when I try to format the drive, nothing happens. I've attached a screenshot of how the drive hows in my array. When I format it, it tries to format and the "Formatting devices" appears and shows "Formatting" next to the device... however this only shows briefly and then it reverts back to "Unmountable: Volume not encrypted". Any ideas on how I can re-add this drive to my array and format it? (Disk log below and Diagnostics attached) Thanks Steve DISK LOG: text error warn system array login Aug 14 09:21:20 Unraid kernel: ata5: SATA max UDMA/133 abar m2048@0xfc000000 port 0xfc000100 irq 89 Aug 14 09:21:20 Unraid kernel: ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Aug 14 09:21:20 Unraid kernel: ata5.00: ATA-9: WDC WD60EFRX-68L0BN1, 82.00A82, max UDMA/133 Aug 14 09:21:20 Unraid kernel: ata5.00: 11721045168 sectors, multi 16: LBA48 NCQ (depth 32), AA Aug 14 09:21:20 Unraid kernel: ata5.00: configured for UDMA/133 Aug 14 09:21:20 Unraid kernel: sd 6:0:0:0: [sdb] 11721045168 512-byte logical blocks: (6.00 TB/5.46 TiB) Aug 14 09:21:20 Unraid kernel: sd 6:0:0:0: [sdb] 4096-byte physical blocks Aug 14 09:21:20 Unraid kernel: sd 6:0:0:0: [sdb] Write Protect is off Aug 14 09:21:20 Unraid kernel: sd 6:0:0:0: [sdb] Mode Sense: 00 3a 00 00 Aug 14 09:21:20 Unraid kernel: sd 6:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Aug 14 09:21:20 Unraid kernel: sd 6:0:0:0: [sdb] Preferred minimum I/O size 4096 bytes Aug 14 09:21:20 Unraid kernel: sdb: sdb1 Aug 14 09:21:20 Unraid kernel: sd 6:0:0:0: [sdb] Attached SCSI removable disk Aug 14 09:22:32 Unraid emhttpd: WDC_WD60EFRX-68L0BN1_WD-WX31D29J50AP (sdb) 512 11721045168 Aug 14 09:22:32 Unraid emhttpd: read SMART /dev/sdb Aug 14 09:27:20 Unraid emhttpd: WDC_WD60EFRX-68L0BN1_WD-WX31D29J50AP (sdb) 512 11721045168 Aug 14 09:27:20 Unraid kernel: mdcmd (2): import 1 sdb 64 5860522532 1 WDC_WD60EFRX-68L0BN1_WD-WX31D29J50AP Aug 14 09:27:20 Unraid kernel: md: import disk1: (sdb) WDC_WD60EFRX-68L0BN1_WD-WX31D29J50AP size: 5860522532 erased Aug 14 09:27:20 Unraid emhttpd: read SMART /dev/sdb Aug 14 09:27:36 Unraid emhttpd: shcmd (356): echo 128 > /sys/block/sdb/queue/nr_requests Aug 14 09:27:58 Unraid emhttpd: writing GPT on disk (sdb), with partition 1 byte offset 32KiB, erased: 0 Aug 14 09:27:58 Unraid emhttpd: shcmd (447): sgdisk -Z /dev/sdb Aug 14 09:27:59 Unraid kernel: sdb: sdb1 Aug 14 09:28:00 Unraid kernel: sdb: sdb1 Aug 14 09:28:00 Unraid emhttpd: shcmd (448): sgdisk -o -a 8 -n 1:32K:0 /dev/sdb Aug 14 09:28:01 Unraid kernel: sdb: sdb1 Aug 14 09:30:42 Unraid emhttpd: shcmd (450): /sbin/wipefs -a /dev/sdb Aug 14 09:30:43 Unraid root: /dev/sdb: 8 bytes were erased at offset 0x00000200 (gpt): 45 46 49 20 50 41 52 54 Aug 14 09:30:43 Unraid root: /dev/sdb: 8 bytes were erased at offset 0x57541e95e00 (gpt): 45 46 49 20 50 41 52 54 Aug 14 09:30:43 Unraid root: /dev/sdb: 2 bytes were erased at offset 0x000001fe (PMBR): 55 aa Aug 14 09:30:43 Unraid root: /dev/sdb: calling ioctl to re-read partition table: Success Aug 14 09:30:43 Unraid emhttpd: writing GPT on disk (sdb), with partition 1 byte offset 32KiB, erased: 0 Aug 14 09:30:43 Unraid emhttpd: shcmd (451): sgdisk -Z /dev/sdb Aug 14 09:30:44 Unraid emhttpd: shcmd (452): sgdisk -o -a 8 -n 1:32K:0 /dev/sdb Aug 14 09:30:45 Unraid kernel: sdb: sdb1 Aug 15 07:45:27 Unraid emhttpd: shcmd (603): /sbin/wipefs -a /dev/sdb Aug 15 07:45:28 Unraid root: /dev/sdb: 8 bytes were erased at offset 0x00000200 (gpt): 45 46 49 20 50 41 52 54 Aug 15 07:45:28 Unraid root: /dev/sdb: 8 bytes were erased at offset 0x57541e95e00 (gpt): 45 46 49 20 50 41 52 54 Aug 15 07:45:28 Unraid root: /dev/sdb: 2 bytes were erased at offset 0x000001fe (PMBR): 55 aa Aug 15 07:45:28 Unraid root: /dev/sdb: calling ioctl to re-read partition table: Success Aug 15 07:45:28 Unraid emhttpd: writing GPT on disk (sdb), with partition 1 byte offset 32KiB, erased: 0 Aug 15 07:45:28 Unraid emhttpd: shcmd (604): sgdisk -Z /dev/sdb Aug 15 07:45:29 Unraid emhttpd: shcmd (605): sgdisk -o -a 8 -n 1:32K:0 /dev/sdb Aug 15 07:45:30 Unraid kernel: sdb: sdb1 Aug 15 07:52:18 Unraid emhttpd: shcmd (622): /sbin/wipefs -a /dev/sdb Aug 15 07:52:18 Unraid root: /dev/sdb: 8 bytes were erased at offset 0x00000200 (gpt): 45 46 49 20 50 41 52 54 Aug 15 07:52:18 Unraid root: /dev/sdb: 8 bytes were erased at offset 0x57541e95e00 (gpt): 45 46 49 20 50 41 52 54 Aug 15 07:52:18 Unraid root: /dev/sdb: 2 bytes were erased at offset 0x000001fe (PMBR): 55 aa Aug 15 07:52:18 Unraid root: /dev/sdb: calling ioctl to re-read partition table: Success Aug 15 07:52:18 Unraid emhttpd: writing GPT on disk (sdb), with partition 1 byte offset 32KiB, erased: 0 Aug 15 07:52:18 Unraid emhttpd: shcmd (623): sgdisk -Z /dev/sdb Aug 15 07:52:19 Unraid emhttpd: shcmd (624): sgdisk -o -a 8 -n 1:32K:0 /dev/sdb Aug 15 07:52:20 Unraid kernel: sdb: sdb1 unraid-diagnostics-20230815-0755.zip

Hi, Bit of a strange problem. Sometimes when rebooting I am unable to access the webgui. I see the login page, enter the correct details and then Unraid just hangs trying to load the dashboard (or any other page). When this happens, I also find that my VM's do not auto-start and only half my dockers seem to load. The dockers that have loaded correctly, work perfectly and I can access the webgui's for them. The array itself also seems to be fine. But obviously I can only manage my system through the CLI. Weirdly if I hard reset, it can all come back up normally - so its pot luck when this happens. I have attached my syslog that I could pull from the CLI - but please let me know if I need to dump anything else. Thanks Steve syslog.txt

Thanks, I'll try that. You were right in it dropping off... it completely disappeared and took a couple of reboots for it to come back, even though it was showing in the BIOS the whole time. I'll also check out the firmware updates... not too keen on this, as I've just got my VMs working perfectly and that took a fair amount of finding the right firmware lol.

Hi All, I'm having some issues recently with my cache drives and BTRFS errors. I think (again not 100% certain) its caused by a windows update I was running on my VM 20H2 was the update. I restarted the VM... which is already a challenge as I have a RX5700 card. Then at some point into the installing updates, my dockers start failing and everything crashes! These are the errors I see in my log - and they fill it up!: Jan 9 13:54:49 Unraid kernel: BTRFS warning (device nvme0n1p1): i/o error at logical 630640209920 on dev /dev/nvme1n1p1, physical 154951610368, root 5, inode 497938, offset 79220768768, length 4096, links 1 (path: domains/Windows 10/vdisk1.img) Jan 9 13:54:52 Unraid kernel: BTRFS warning (device nvme0n1p1): lost page write due to IO error on /dev/nvme1n1p1 (-5) Jan 9 13:54:52 Unraid kernel: BTRFS error (device nvme0n1p1): error writing primary super block to device 2 Jan 9 13:54:52 Unraid kernel: BTRFS warning (device nvme0n1p1): lost page write due to IO error on /dev/nvme1n1p1 (-5) Jan 9 13:54:52 Unraid kernel: BTRFS warning (device nvme0n1p1): lost page write due to IO error on /dev/nvme1n1p1 (-5) Jan 9 13:54:52 Unraid kernel: BTRFS warning (device nvme0n1p1): lost page write due to IO error on /dev/nvme1n1p1 (-5) Jan 9 13:54:52 Unraid kernel: BTRFS error (device nvme0n1p1): error writing primary super block to device 2 Jan 9 13:54:54 Unraid kernel: btrfs_dev_stat_print_on_error: 8898923 callbacks suppressed Jan 9 13:54:54 Unraid kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme1n1p1 errs: wr 185867, rd 46640931, flush 6441, corrupt 1321, gen 0 Jan 9 13:54:54 Unraid kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme1n1p1 errs: wr 185867, rd 46640932, flush 6441, corrupt 1321, gen 0 I have performed a scrub on the cache drives and all seem fine?! Anyone got any ideas? I'm not sure windows updates should be able to cause this level of issues on what should be an image file. Full logs are attached as well. Thanks, Steve unraid-diagnostics-20210109-1406.zip

Any particular links or advice you can point me to? I want to ensure it is compatible with Unraid and not break the bank too much

Hi All, I've caught the data bug and can't bring myself to delete my precious terabytes of mostly crap I have on my Unraid array. I've ran out of space in my case and don't yet want to increase the capacity of the drives as they are all fairly new and I only have space for 6 - so its about time I increase anyways! I'm looking for a solution where I can have another unit next to my server to expand my drive capacity. I was looking at IcyBox (potentially this: https://www.raidsonic.de/products/external_cases/external_cases_35/index_en.php?we_objectID=491) but from what I can tell this operates as 1 drive through eSata or USB. I would ideally just like 1 or 2 cables running neatly from box to box... and don't want loads of mess. Any idea on what best to go for? Thanks, Steve

This is amazing, its exactly what I needed. Before you ask, not the dog... the move command lol. I've stuck it in a user script to run when the array first starts - which should do the trick! Little b&%$%d occasionally hits the reset button with a claw as well... so I'll disable that

Hi Everyone, I've done some searching already on this topic and can't find a solution that works for me, so I'm hoping I'm missing something really easy. I need to disable the 'off' command when the power button is pressed on my machine. I have a cat that likes to sleep on it and despite placing a cover etc... he still manages to turn the bloody thing off! lol I can't just unplug the button from the motherboard as I still want the ability to 'turn it on' the reason why is I have the Navi 10 reset problem and use a script to reset the card, which places my machine in standby mode. I'm hoping there is a really easy way I can just change the button's behaviour in linux - so that it does nothing when pressed if already on. I'm using the release candidate 6.9 of Unraid and my motherboard is a X570 Aurus Xtreme (may help). Thanks, Steve

I have the same issue currently. Did you manage to find a solution for this?

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

@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

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

Hey - Did anyone get a solution for this? I seem to be experiencing the exact same behaviour. I've completely remove the directory and plg files from the flash drive.