Hello all,

Hope i can find any help:

 

I just set up a VM with Win 10 working properly under VNC. Today i installed a new GPU and get this error:

internal error: qemu unexpectedly closed the monitor: 2020-10-30T19:29:47.572008Z qemu-system-x86_64: -device vfio-pci,host=0000:01:00.0,id=hostdev0,bus=pci.0,addr=0x5: vfio 0000:01:00.0: group 9 is not viable Please ensure all devices within the iommu_group are bound to their vfio bus driver.

 

I followed the instructions changing settings PCIe ACS override in all modes and changed also the "VFIO allow unsafe interrupts", but i can't start the VM with a passthrough to my GPU. 

Many thanks in advance for any help.

Hi there,

 

It looks like your hardware may not be suitable for GPU pass through.  Can you please attach your system diagnostics?  These can be obtained from the Tools > Diagnostics page.

Ok, here's the file. Hope the Hardware is suitable...

unraid-diagnostics-20201103-0051.zip

... and thank you in advance.

Hello, any news for me? Best Regards

FINALLY FIGURED IT OUT!!!  Can't believe how long this took me.  So sorry for the delayed response.  I was overthinking the problem and after reviewing your logs, the issue is that your GPU has a built in USB controller.  Unraid binds the driver for that controller to the VM.  You need to bind the USB controller to the VFIO-PCI device driver to prevent it from being attached to the full driver.  You can do this from the Tools > System Devices page.  Scroll down to find device 01:00.2 and stub that device.  A reboot will be required thereafter.  Let me know if you need further assistance.

Thanks! I think, we are a step closer to the solution but i regret, i can't change anything in the System Devices page. I have no XML slider or similar. How can i change things? Regards, Uno

RE-Hello, since i still don't know how to change things, i tried to resolve with the VFIO.CFG Plugin, i think i am a step closer to the solution, since the monitor now, after binding the USB controller to the VFIO.CFG receives a signal. I regret, the screen is still dark. So, if there is a way to bind the USB Controller wothout using the plugin, it would be very helpful for me to know. Thanks

Are you booting Unraid itself in efi mode or legacy mode?

Sent from my Pixel 3 XL using Tapatalk

I wrote the ISO as UEFI down to the USB Stick, using the installer.

Can you try booting in legacy mode and see if that works better? You can toggle this boot mode from the flash device settings page.

Sent from my Pixel 3 XL using Tapatalk

It seems, that my MB does not support Legacy mode Fujitsu B-3644...

Hello agian, so now i really tried everything i could, but it still doesn't work. What i tried until now:

 

• I tried flash and start in Uefi & Lagacy, but only UEFI starts up (it's probable that my MB does support only UEFI, my research gave not a 100% clear result on this, but if it is crucial, i will try to go further and contact the seller.
• I edited the NVIDIA Rom file from techpowerup in 2 different ways, since, there are 2 different positions into the BIOS File, where the "iVideo" marker is set.
• To be comlete i dumped also the GPU ROM with GPU-Z but also this solution didn't work.
• The IOMMU Group is properly separated from the others and with the VFIO-CFG Plugin, the USB Controller is set up fine. 
• The settings into the PCI-e are set to "Downstream" unsafe interrupts are switched off.

... and here is the latest verision of the diag file. Hope we finally will bring the project on track, thanks for all your support.

 

tower-diagnostics-20201108-1720.zip

There should be a way to enable legacy booting on your motherboard. Please contact the manufacturer and see how to enable this in the bios if possible.

Sent from my Pixel 3 XL using Tapatalk

• BIOSAMI Aptio 5.x (UEFI) BIOSmodified and adapted by Fujitsu Technology Solutions; Recovery BIOS,SM-BIOS (DMI), BIOS and CPU Microcode Update, Quick Boot, Logo Boot, Quiet Boot, Plug & Play, Automatic DRAM and PCIe Configuration, BIOS Support for S.M.A.R.T., Advanced Power Management, ACPI S3/S4, Wake on time from S5.HW Watchdog support & BIOS integrated HW Diagnostic Tool.No legacy OS support, no MBR installation(UEFI only due to Intel restrictions

... at least it's clear now. Do you think, this is the reason?

 

 

 

Yes I do. I will inquire with some of our other developer contacts to see if there's workarounds for this problem. It sucks that Intel is requiring you to use UEFI for the setup.

Sent from my Pixel 3 XL using Tapatalk

Thanks, in the meantime i try to find out, if there are older BIOS versions for me, allowing Legacy boot.

Can you try adding this to your append line in syslinux? You can do this from the tools > flash device settings page.

video=efifb:off

Save and reboot and let me know if that works.



Sent from my Pixel 3 XL using Tapatalk

Hi, saw this already, tried, but no result. What do you think is it the gpu or the mb? If there is a list of compatible HW i can check , if i can change one of the items.
Regards

Sent from my Mi A3 using Tapatalk

Hi all, I FINALLY GOT IT!! Thanks for your help, the video=efifb:off solved the problem. I only had to refill it in the Syslinux config (for some reason the original input was not there). Now i can boot in UEFI and Passthrough the GPU. Next Step: Buy a Key. For me it was necessary to understend what an IOMMU Group is and how it works. Then i understood better, why all devices in a Group must be bend to th vfio driver. Finally i configured the USB controller manually and it worked.

Thanks again for your help!

PS: Wahat does the video=efifb:off command do?