Wuping Posted September 20, 2018 Share Posted September 20, 2018 Hey guys anyone getting an vfio: Unable to power on device, stuck in D3 when starting a VM with video passthrough after the 6.6.0 update? I reverted back to 6.5.3 and my Windows 10 VM works fine. I'm running a AMD 1950X with 32 GB of Ram and a GTX 1050 Link to comment
limetech Posted September 21, 2018 Share Posted September 21, 2018 Need diagnostics.zip Link to comment
Wuping Posted September 21, 2018 Author Share Posted September 21, 2018 On 9/21/2018 at 10:40 AM, limetech said: Need diagnostics.zip attached, thanks Link to comment
eschultz Posted September 22, 2018 Share Posted September 22, 2018 Upgrade your Gigabyte BIOS to the latest and it'll fix the VM passthrough issues. Link to comment
Wuping Posted September 22, 2018 Author Share Posted September 22, 2018 1 hour ago, eschultz said: Upgrade your Gigabyte BIOS to the latest and it'll fix the VM passthrough issues. That fixed the issue thanks a lot Link to comment
Ryoko Posted September 25, 2018 Share Posted September 25, 2018 Can confirm upgrading BIOS fixed this issue for my MSI x399 SLI PLUS mother board as well. Link to comment
killeriq Posted April 15, 2019 Share Posted April 15, 2019 @limetech - Im on Version 6.7.0-rc7 2019-04-03 and just upgraded my ASUS CROSSHAIR VI HERO bios to Version 6903 - 2019/04/11 and i start to get this issue now When i Run the VM 1st time it starts but it wont start mining, to i power OFF the VM and try to start again - getting "internal error: Unknown PCI header type '127'" In Logs: 2019-04-15T12:24:56.897909Z qemu-system-x86_64: vfio: Unable to power on device, stuck in D3 2019-04-15T12:24:56.902880Z qemu-system-x86_64: vfio: Unable to power on device, stuck in D3 2019-04-15T12:28:28.784776Z qemu-system-x86_64: terminating on signal 15 from pid 14010 (/usr/sbin/libvirtd) 2019-04-15 12:28:31.422+0000: shutting down, reason=shutdown ---------- Should i roll back BIOS update or what options i've got? thanks unraidtower-diagnostics-20190415-1234.zip Link to comment
killeriq Posted April 15, 2019 Share Posted April 15, 2019 tried to go to bios 6808 and now im getting those errors in VM (no D3 anymore) 2019-04-15T15:28:06.280241Z qemu-system-x86_64: vfio_region_read(0000:0b:00.0:region1+0x9008c, 4) failed: Device or resource busy 2019-04-15T15:28:06.280260Z qemu-system-x86_64: vfio_region_write(0000:0b:00.0:region1+0xa0018, 0x40088,4) failed: Device or resource busy 2019-04-15T15:28:06.280274Z qemu-system-x86_64: vfio_region_write(0000:0b:00.0:region1+0xa001c, 0x0,4) failed: Device or resource busy 2019-04-15T15:28:06.280289Z qemu-system-x86_64: vfio_region_write(0000:0b:00.0:region1+0xa0020, 0x40084,4) failed: Device or resource busy 2019-04-15T15:28:06.280304Z qemu-system-x86_64: vfio_region_write(0000:0b:00.0:region1+0xa0024, 0x0,4) failed: Device or resource busy 2019-04-15T15:28:07.610273Z qemu-system-x86_64: vfio_region_read(0000:0b:00.0:region1+0xfdf028c, 4) failed: Device or resource busy 2019-04-15T15:28:15.802311Z qemu-system-x86_64: vfio_region_read(0000:0b:00.0:region1+0xfdf028c, 4) failed: Device or resource busy 2019-04-15T15:28:23.994328Z qemu-system-x86_64: vfio_region_read(0000:0b:00.0:region1+0xfdf028c, 4) failed: Device or resource busy 2019-04-15T15:28:32.186328Z qemu-system-x86_64: vfio_region_read(0000:0b:00.0:region1+0xfdf028c, 4) failed: Device or resource busy 2019-04-15T15:28:40.378322Z qemu-system-x86_64: vfio_region_read(0000:0b:00.0:region1+0xfdf028c, 4) failed: Device or resource busy 2019-04-15T15:28:41.703547Z qemu-system-x86_64: vfio_region_write(0000:0b:00.0:region1+0xfdf068c, 0x1,4) failed: Device or resource busy --- So tried to change Settings -> VM Manager -> PCIe ACS override: to "Downstream" before i had "Both" Last time i remember there was only YES/NO option not sure with which OS update it got extended... unraidtower-diagnostics-20190415-1536.zip Link to comment
killeriq Posted April 15, 2019 Share Posted April 15, 2019 on 6808 bios - issue fixed with "disabling UEFI boot mode" on Unraid Flash drive on 6903 bios - still D3 error Link to comment
sturmstar Posted May 30, 2019 Share Posted May 30, 2019 Hi. I actually had the same issue but with another board and bios update ... I have the "Gigabyte X470 AORUS ULTRA GAMING" Board on bios version F6. When I updated to F40 I had the same symptons and problems as you described - wrong CPU pining and the same issues with VM GPU passthrough. I wasn't able to fix them - so I downgraded again - and it is working again. I have no problems with this bios version - I'm just wondering for the future - maybe I'd like to upgrade to a 3000er Ryzen sometime - but if everything else - meaning GPU passthrough - is broken with newer bioses - that would be a problem. Maybe I'm too concerned - maybe until then there are already newer bios versions not having this issues... Best regards PS: Unraid Version is/was 6.7.0... Link to comment
Kyruss86 Posted May 31, 2019 Share Posted May 31, 2019 Same here after updating my Bios Version from 4207 to 4801 I´m on Asus PRIME B350-PLUS with Ryzen 1600 and unRaid 6.7.0 Wrong CPU Pining, "Unknown PCI header type '127'" and "vfio: Unable to power on device, stuck in D3" - but only on the first PCIE Slot/Card... But starting the same VM with the second Card (2. PCIE Slot) is no problem. I'm a bit frustrated, because simple downgrading doesn't work with my board... Should we open a "AGESA Bios Update-Warning" thread...? 😉 @killeriq : There is a new Bios version 7002 for your board, have you already tried it? greetings Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.