I ended up getting one of these cards anyway and I am pleased to find that I'm not having any issues with my Linux VM when shutting down or rebooting.

I'm on Unraid 7.1.2 which is on the newer 6.12 kernel compared to 7.0.1 which I believe was still on 6.6 and I have the GPU and audio device unbound in VFIO

Unfortunately I cannot confirm anything with Windows because I don't have a windows VM set up, but this thread on Reddit has a script that seems to prevent this issue if run before starting the VM. Note that they use the custom 6.14 kernel, which may or may not still be necessary for Windows to work.

Running the Linux VM, I am still seeing the following errors repeated in the logs
qemu-system-x86_64: vfio: Cannot reset device 0000:00:1f.5, no available reset mechanism.

qemu-system-x86_64: vfio: Cannot reset device 0000:00:14.0, no available reset mechanism.

qemu-system-x86_64: vfio: Cannot reset device 0000:00:1f.3, no available reset mechanism.

and

qemu-system-x86_64: VFIO_MAP_DMA failed: Invalid argument

qemu-system-x86_64: vfio_container_dma_map(0x55c154e14fe0, 0x383000000000, 0x400000000, 0x144bc0000000) = -22 (Invalid argument)

But since there haven't been any issues I can see I haven't looked into them too much yet

Edited June 18, 20251 yr by sixkittens
Misstated version number

Hi, got the same issue here. Updated to latest kernel version 6.14.6. Run the unbind, bind script and added tried multiple combinations in syslinux.cfg with e.g. "video=efifb:off" to block the unraid usage.

On a fresh unraid boot the device is on D0 mode:

cat /sys/bus/pci/devices/0000\:03\:00.0/power_state

D0

The virtual machine with GPU 9070 XT passed through boots without issues the first time.

But once I shut it down the graphic card goes into "D3cold" and the unraid system is instantly frozen. It can only be shutdowned by a hard reset.

I wonder why it works for some people and for some don't. Anybody has an idea?

Regards

Update on my last comment. I'm getting issues sometimes when playing games where the VM locks up completely and has to be force stopped and restarted. It may be the power state change issue that has been mentioned earlier, but I am unsure how to check. Hoping that someone at Lime Tech is looking into this issue, I would hate to have to go back to my 1080ti after buying a new card.

Edit: Adding the following to my XML under the cpu section fixed the crashes and the VFIO_MAP_DMA error:

<domain...>
  <cpu...>
    ...
    <maxphysaddr mode='passthrough' limit='39'/>
  </cpu>
  ...
</domain>

I'm not sure what the 'limit' section does, since I saw people suggesting both with and without it, but it works with and I haven't tested without.

Edited July 2, 20251 yr by sixkittens
Added possible fix

Please can we have an update on who has this working and what version of unraid you are running and what kennel?

Along with what VirtIO driver you are running?

Let's get this working this month!

Thank you

Edited July 19, 20251 yr by Rick Sanchez

Unfortunately I haven't been able to set up a Windows VM to test the issue, for some reason the installation hangs for both Windows 10 and 11. That said I have had no issues with my Linux VM since updating my previous post.

Edit: managed to install Win 11, but it's no go. "vfio: Unable to power on device, stuck in D3" showing up in the logs and a hard reset is still needed to stop the VM if the OS shuts down even after adding the line from my earlier message to the XML.

Edited July 27, 2025Jul 27 by sixkittens
Update

@limetech @SpaceInvaderOne

Do you have any information on when UnRAID will update its kernel to the required version to support this card?

Thank you

My RTX 5060 has a similar issue—the log shows it getting stuck in D3 state, and the VM also fails to pass through properly. When I start the VM, it reports an error: "Unknown PCI header type '127'". My Unraid is already on the latest version, and the BIOS is up to date as well. I borrowed my friend's RTX 4060 to test, and without making any changes to the configuration, everything worked perfectly with no errors. I've already posted about this issue elsewhere, but haven't received any replies, so I'm sharing it here since it seems more active.

On 7/29/2025 at 1:37 PM, Rick Sanchez said:

@limetech @SpaceInvaderOne

Do you have any information on when UnRAID will update its kernel to the required version to support this card?

Thank you

Refer to this:

On 8/19/2025 at 8:37 PM, PUNGGOKERS said:

Refer to this:

for me this is working

Unraid Kernel: "6.16.0-rc7-thor-Unraid+"

linux bazzite vm kernel: 6.16.4

Q35-9.2

Multifunction: On

Sound Card: AMD Navi 48 HDMI (this renamed from RX9070XT with the 6.16 kernel so I think it's working because of the new Kernel)

Windows is still giving strange issues even with syslinux.cfg changes, leaving sound card unmounted, unbind gpu script on startup...

On 9/6/2025 at 1:59 AM, Ojun said:

for me this is working

...

linux bazzite vm kernel: 6.16.4

...

The issue does not occur with Linux-based VM's only Windows ones.

On 9/10/2025 at 1:32 AM, sixkittens said:

The issue does not occur with Linux-based VM's only Windows ones.

Good to know

On 9/9/2025 at 7:32 PM, sixkittens said:

The issue does not occur with Linux-based VM's only Windows ones.

Did you solve your issue or ???

Coz putting vfio-pci.disable_idle_d3=1 in the append line usually solves it when it comes to the power management of the GPU.

In the qemu command line?

Doesn't seem to help with the D3 power issue for me in my test just now when binding my GPU for the Linux VM. I can run the VM unbound but when the VM is off the displays don't power down so eventually I'd like to be able to bind the GPU again. Haven't tested windows yet

Edit: nevermind, when unbound it does actually seem to fix the monitors staying on. How strange. I still get no video out when bound, which is indicative of some problem still existing, but that seems to do something at least. I'll try test windows tomorrow.

Edit 2: Scratch that, it doesn't get saved if entered into the qemu args section. Guess the change I noticed was from binding and unbinding the GPU.

Edited October 15, 2025Oct 15 by sixkittens
update

I have tried all the troubleshooting steps here myself.
I've tried a 9060XT and a 7900GRE.

Seeing a D0 code at almost every step.
But, once I stop the VM and try to start again I receive the 127 PCI header error.

On 10/3/2025 at 9:50 AM, PUNGGOKERS said:

Did you solve your issue or ???

Coz putting vfio-pci.disable_idle_d3=1 in the append line usually solves it when it comes to the power management of the GPU.

Adding this line in the syslinux command line does not seem to prevent the GPU from binding to D3 when the GPU is bound to VFIO at boot (as mentioned before, it does not do it for me when it's unbound), nor do spaceinvaderone's suggestions of disabling the framebuffer and resizeable BAR. I decided to revisit this because despite not having the shutdown issue with my Linux VM, I am on rare occasion seeing the server freeze when I try to start the VM instead. I have not had much luck so far though.

Edit: The weird thing is that the VM log says the GPU is stuck in D3 and won't restart if I shut it down, like I would expect if it was stuck in D3, but cat /sys/bus/pci/devices/0000:03:00.0/power_state always reports D0

Edited November 6, 2025Nov 6 by sixkittens

1 hour ago, alexandru360 said:

In your post you mention the AMD vendor-reset module/plugin which is only compatible with cards up to the Navi 14 architecture, i.e 5000 series cards, newer cards that experience the vendor reset bug when passing through are not supported by the module and, as far as I am aware, require fixes from the in-kernel drivers. Additionally, the issue being discussed in this thread isn't to do with being able to pass the card through as such, it's preventing the hard freeze that occurs once a VM using the card is shut down and a new VM session starts.

If you are interested in reading up on what other people have written who have managed to prevent the reset bug on newer cards, I'll link some resources here:

https://forum.level1techs.com/t/vfio-pass-through-working-on-9070xt/227194
https://forum.proxmox.com/threads/working-win11-vm-wont-boot-after-passthrough-of-gpu-vendor-reset-not-able-to-set-reset_method-solution-update-kernel-unbind-via-hook-script.166362/
https://forum.proxmox.com/threads/working-amd-rx-9070xt-support.163370/

https://www.reddit.com/r/unRAID/comments/1j52fkc/unable_to_pass_through_amd_rx_9070_xt/

So far I have not had much success following the steps in the threads linked above, but for whatever reason my server doesn't freeze every time, possibly because I am running a Linux VM rather than Windows. Since having a newer host kernel seems to play a role in other users' success, I am hoping for a stable custom kernel for Unraid 7.2 to be released (linked in the reddit thread) before I try anything further, as the unstable one caused my VM to repeatedly kernel panic.

In all cases where people have it working, it appears to be necessary to manually unbind and rebind the GPU before starting a new VM session.

Unfortunately these issues with 7000 and 9000 series cards don't seem to be well known outside of the hobby virtualization communities, and Limetech don't seem to have any ideas, so a definite fix might not be forthcoming any time soon.

On 11/27/2025 at 12:45 AM, sixkittens said:

In your post you mention the AMD vendor-reset module/plugin which is only compatible with cards up to the Navi 14 architecture, i.e 5000 series cards, newer cards that experience the vendor reset bug when passing through are not supported by the module and, as far as I am aware, require fixes from the in-kernel drivers. Additionally, the issue being discussed in this thread isn't to do with being able to pass the card through as such, it's preventing the hard freeze that occurs once a VM using the card is shut down and a new VM session starts.

If you are interested in reading up on what other people have written who have managed to prevent the reset bug on newer cards, I'll link some resources here:

https://forum.level1techs.com/t/vfio-pass-through-working-on-9070xt/227194
https://forum.proxmox.com/threads/working-win11-vm-wont-boot-after-passthrough-of-gpu-vendor-reset-not-able-to-set-reset_method-solution-update-kernel-unbind-via-hook-script.166362/
https://forum.proxmox.com/threads/working-amd-rx-9070xt-support.163370/

https://www.reddit.com/r/unRAID/comments/1j52fkc/unable_to_pass_through_amd_rx_9070_xt/

So far I have not had much success following the steps in the threads linked above, but for whatever reason my server doesn't freeze every time, possibly because I am running a Linux VM rather than Windows. Since having a newer host kernel seems to play a role in other users' success, I am hoping for a stable custom kernel for Unraid 7.2 to be released (linked in the reddit thread) before I try anything further, as the unstable one caused my VM to repeatedly kernel panic.

In all cases where people have it working, it appears to be necessary to manually unbind and rebind the GPU before starting a new VM session.

Unfortunately these issues with 7000 and 9000 series cards don't seem to be well known outside of the hobby virtualization communities, and Limetech don't seem to have any ideas, so a definite fix might not be forthcoming any time soon.

You are totally right about that unraid plugin I wanted to say that ... even thow I installed the plugin it does not help my case with my vedeo card ... it came out unclear... whatI said it still works but I'm not satisfied if I do not get a kernel patch soon is going to be very not cool.

Is there any "offical" solution yet? Currently whiched to Ubuntu when running UnRAID VMs but it limits what I can do

Nothing definitive that I've been able to find. There's a few recommendations out there that work for some people, but I haven't found anything that makes an actual difference in my testing. I'm hopeful that the 7.3 update might have a positive effect, moving to the 6.18 kernel. In my case, there's about a 20% (guessing) chance of the GPU locking up after VM stop and crashing the server if the VM starts again, but none of the suggested fixes have made an improvement on that for me.

Hi, Has anyone been able to solve this issue since then?

I also have recently upgraded to a 9070xt and am running into all the issues dicussed in this thread.

I really need a Windows 11VM working with the GPU passed throug.

Thank you for the help.

On 5/5/2026 at 10:22 PM, ashle said:

Hi, Has anyone been able to solve this issue since then?

I also have recently upgraded to a 9070xt and am running into all the issues dicussed in this thread.

I really need a Windows 11VM working with the GPU passed throug.

Thank you for the help.

Im on 7.2.0 with a gigabyte 9070 xt oc and its running flawlessly in a win 11 pro (gaming) VM. It goes to sleep, and can reboot without any server instability issues. I replaced my 7800xt that did have all the reboot issues, changed the romfile for a generic navi48 i found online, and it just worked.

6 hours ago, Arie said:

Im on 7.2.0 with a gigabyte 9070 xt oc and its running flawlessly in a win 11 pro (gaming) VM. It goes to sleep, and can reboot without any server instability issues. I replaced my 7800xt that did have all the reboot issues, changed the romfile for a generic navi48 i found online, and it just worked.

Hi Arie,

Are you referring to a vbios? Any more information you can provide would be helpful as we have been struggling with this for months now (I had mostly given up and just never shut down my VM). I have a vbios file that I dumped directly from my card but it did not fix anything. So if you can confirm what the romfile is and where you got it, as well as any other steps you took to get things working that would be much appreciated.

11 hours ago, sixkittens said:

Hi Arie,

Are you referring to a vbios? Any more information you can provide would be helpful as we have been struggling with this for months now (I had mostly given up and just never shut down my VM). I have a vbios file that I dumped directly from my card but it did not fix anything. So if you can confirm what the romfile is and where you got it, as well as any other steps you took to get things working that would be much appreciated.

To be honest, I was having the very same issues as everyone on my 7800XT, and just figured I might as well try to upgrade and make it work with a 9070 XT. I had heard rumors that people had gotten it to work, so wanted to give it a shot, and if it failed I would return the card and just concede and get an Nvidia card. But to my surprise, it just worked. All of it. I leave the VM running (as it seems to lower my idle power consumption, I think windows activates some power saving modes that Unraid doesnt), and it auto updates, reboots without any issues. I can get it out of hibernate mode by clicking the restart option in Unraid VM manager, and it comes back alive. And all I did was swap out the card and the rom file.

See below some screenshots of my VM and passthrough screens which show my settings and version numbers, and Ive attached the Navi48 rom file I found on a random website which seems to work.

Unraid Win 11 Pro VM details.pdfUnraid GPU Passthrough.pdfNavi 48.rom

My hardware:

Intel 12600K on an Asrock Z790 Pro RS with an Gigabyte RX 9070 XT Gaming OC and I use a 10 euro OEM key on a Windows 11 Pro installation (see screenshot for details). I have the AMD vendor reset plugin installed since my attempts to get the 7800XT tp play nice, but never tested if it does anything for the 9070 XT.

Let me know if you want to know anything else!

PS. Updating to 7.2.6 broke the VM btw. It boots, outputs scrambled image, then stops outputting image altogether. Doesnt seem to cause a server reboot or anything like that. Dont you just love Unraid? Ugh

Edited May 12May 12 by Arie

On 5/9/2026 at 10:52 PM, Arie said:

To be honest, I was having the very same issues as everyone on my 7800XT, and just figured I might as well try to upgrade and make it work with a 9070 XT. I had heard rumors that people had gotten it to work, so wanted to give it a shot, and if it failed I would return the card and just concede and get an Nvidia card. But to my surprise, it just worked. All of it. I leave the VM running (as it seems to lower my idle power consumption, I think windows activates some power saving modes that Unraid doesnt), and it auto updates, reboots without any issues. I can get it out of hibernate mode by clicking the restart option in Unraid VM manager, and it comes back alive. And all I did was swap out the card and the rom file.

See below some screenshots of my VM and passthrough screens which show my settings and version numbers, and Ive attached the Navi48 rom file I found on a random website which seems to work.

Unraid Win 11 Pro VM details.pdfUnraid GPU Passthrough.pdfNavi 48.rom

My hardware:

Intel 12600K on an Asrock Z790 Pro RS with an Gigabyte RX 9070 XT Gaming OC and I use a 10 euro OEM key on a Windows 11 Pro installation (see screenshot for details). I have the AMD vendor reset plugin installed since my attempts to get the 7800XT tp play nice, but never tested if it does anything for the 9070 XT.

Let me know if you want to know anything else!

PS. Updating to 7.2.6 broke the VM btw. It boots, outputs scrambled image, then stops outputting image altogether. Doesnt seem to cause a server reboot or anything like that. Dont you just love Unraid? Ugh

I recommend unbinding the GPU from VFIO, and testing again. Not sure how you got it to work before, but binding to VFIO (for me anyway) causes the GPU to get stuck in the wrong power state and there's no video output as a result.

I intend to look further into what might be causing the lockup when bound, but I don't know enough about how these things work to have a good starting point.

I have added a ROM that I dumped myself from GPU-Z, and updated to 7.3.0, which has a newer kernel, so it may yet prevent the lockups when restarting the vm.