Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Unraid not releasing GPU for vm passthough.

Featured Replies

HI all,

last few months i've been having an issue with my VM on unriad, i've used co-pilot a few times to help correct the issue, but it keeps comenig back so i thought i'd try here for help.

For several years I've been using one graphics card in my server that on boot loads into the unraid GUI, but when i launch my main VM it disconnects from the server and launches the vm using that card. I've had no problems with this all all, until the last few months, i'm not sure when it first happened or if it was related to an update. I've had a fail drive aroudn the same time i first noticed this, but no other harware changes, and i havn't tinkered with the setting on the system.

I've tried to bind the GPU to the VIFO on boot but i still get the same issues.

any one got any clues or ideas that i can try? i have a second GPU in the system but i cannot alter the placement in the PCIE slots as they will not fit.

thanks for your help in advance.

server-diagnostics-20260210-2207.zip

Solved by Belcraig

  • Community Expert

you need to chose to have it for the VM only or for unraid host access and dockers...

VFIO bind removes it form the host to never be seen or used by unraid host or dockers...
VFIO bind is correct adn prper way to pass a gcard to a VM.

to unbind a gcard this way you must unbind the GPU form VFIO and REBOOT UNRAID!
THE VM WILL NOT BE ABEL TO BE USED WITH BOTH! its one or the other...

This is wher vgpu unlock and other hackery came about... amd mxgpup and Windows NVIDIA GPUP...
This is not a support feature nor operation on unraid slackware linux.

SO first pick do you want the G Card for the VM or for the unraid Host...

  • Community Expert

Yes the VM takes control the GPU. The GPU cannot be used on the host machine until after a reboot. This is normal and expected. Not a bug.

AMD GPUs allegedly could return to the host using the AMD Vendor reset plugin but I dont have experience with passing through GPUs.

Intel GPUs and Nvidia GPUs require a full reboot.

Edit:

Apparently it can be rare some hardware can handle it but it's going to be highly dependent on the specific hardware combination and drivers.

Edited by MowMdown

  • Author

the normal operation - what has been working for the last several years is

unraid will boot into GUI,

if i then start a VM the VM takes the graphics card, Unraid never gets it back from this without a reboot of the server.

However, this has stopped working.

I dont necessarily need the GUI i can go to a different room and access if there (if the VM has an issue) -its mroe convienance.

However, I've tried to bind the GPU to VIFO at boot in the tools --> system devices but this is not working, on the screen i get the bios and the loading, then the screen stops but it dosn't pass through to the VM.

Edited by Belcraig

  • Author

ok I've moved the PCIE cards around so that the nvidea gt710 sits in the primary slot on the mother board, and moved the rx 570 to a different slot.

I've acknowledged the PCI changes in devices settings and bound the IOMMU group to VIFO at Boot (the rx570).

restarted the server and still no images on the screens from the VM.

Anyone else able to throw an idea?

I am getting this in the logs but if i bound both the GPU and the sound at boot how can i stop it picking this up.

2026-02-17T15:40:21.402594Z qemu-system-x86_64: vfio: Cannot reset device 0000:82:00.1, no available reset mechanism.

2026-02-17T15:40:21.510705Z qemu-system-x86_64: vfio: Cannot reset device 0000:82:00.1, no available reset mechanism.

2026-02-17 15:40:28.437+0000: Domain id=1 is tainted: custom-monitor

usb_generic_handle_packet: ctrl buffer too small (20480 > 4096)

thanks

Craig

Edited by Belcraig

  • Author
  • Solution

HI all,

In case anyone else finds themselves in a similar problem it seems that the ROM was incorrect...

having it now not in the primary slot means i do not need the ROM.

Not sure if an unraid update made the ROM invalid..

Regards

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...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.