So trying to make VM with GPU pass threw. Get this error.

 

internal error: qemu unexpectedly closed the monitor: 2017-04-13T04:36:33.553980Z qemu-system-x86_64: -device vfio-pci,host=05:00.0,id=hostdev0,bus=pci.0,addr=0x5: vfio: failed to set iommu for container: Operation not permitted
2017-04-13T04:36:33.554025Z qemu-system-x86_64: -device vfio-pci,host=05:00.0,id=hostdev0,bus=pci.0,addr=0x5: vfio: failed to setup container for group 18
2017-04-13T04:36:33.554031Z qemu-system-x86_64: -device vfio-pci,host=05:00.0,id=hostdev0,bus=pci.0,addr=0x5: vfio: failed to get group 18
2017-04-13T04:36:33.554047Z qemu-system-x86_64: -device vfio-pci,host=05:00.0,id=hostdev0,bus=pci.0,addr=0x5: Device initialization failed

 

CPUs have VT-d /VT-x / Hyper V and they are all on in the bios 100% sure about this.

(also had pass threw working in ESXi , so i know it works ) 

 

I have tried with A GT 710 and GT 730 so its not the cards.

Also, in other PCI Devices my HBA dont show up ... wanted to use that for A VM later on ... 

 

Thank you for any help you can give.

 

Neko

 

unneko-diagnostics-20170412-2145.zip

Edited April 13, 20179 yr by Neko77025

This is your problem:

 

pci 0000:05:00.1: Device is ineligible for IOMMU domain attach due to platform RMRR requirement.  

This is the audio portion of your gpu.

 

you will need to read this thread: 

 

 

You can then try 1 of 2 things. The first is going into the server bios and switching the server to the backup bios. Earlier versions sometimes remove this error. The second option is follow the workaround in the thread above which discusses isolating the 2 components of the GPU from each other, then only passing through the video component. 

 

Either way, you will need to modify your syslinux.cfg to contain the following to get either one of the above fixes to work:

 

append vfio_iommu_type1.allow_unsafe_interrupts=1 initrd=/bzroot

 

 

for the hba, you'll need to stub it (isolate it from unRaid) to pass it through to a vm.

30 minutes ago, 1812 said:

This is your problem:

 

pci 0000:05:00.1: Device is ineligible for IOMMU domain attach due to platform RMRR requirement.  

This is the audio portion of your gpu.

 

you will need to read this thread: 

 

 

You can then try 1 of 2 things. The first is going into the server bios and switching the server to the backup bios. Earlier versions sometimes remove this error. The second option is follow the workaround in the thread above which discusses isolating the 2 components of the GPU from each other, then only passing through the video component. 

 

Either way, you will need to modify your syslinux.cfg to contain the following to get either one of the above fixes to work:

 

append vfio_iommu_type1.allow_unsafe_interrupts=1 initrd=/bzroot

 

 

for the hba, you'll need to stub it (isolate it from unRaid) to pass it through to a vm.

Thank you, 

 

Will read and look into.  

 

Just wondering, if I disable the Audio from the GPU , is their another way to get audio back to the VM, other then adding A soundcard ?..

 

These VMs are for streaming too TVs so I can have computers at any TV and they will need sound. (not games, just for general PC/web stuff ) 

Just now, Neko77025 said:

Thank you, 

 

Will read and look into.  

 

Just wondering, if I disable the Audio from the GPU , is their another way to get audio back to the VM, other then adding A soundcard ?..

 

These VMs are for streaming too TVs so I can have computers at any TV and they will need sound. (not games, just for general PC/web stuff ) 

 

Try using the older bios first. On my servers, the newer bios makes the audio portion of gpu's ineligible. But I rolled them back to the factory backup bios and it's all fine using HDMI audio from gpus.

 

The last post in that thread has links to HP's workarounds and explanations of why it happens . There is one other user on here who has done the workaround, or come close. I have not attempted it as it looked time consuming.

 

The only other way I know to get audio back to a physical vm w/out hdmi audio is via usb audio dongle or sound card.

 

You say the vm's are for streaming to tv's... streaming how? Or did you mean to say that they will be hooked up to tv's? 

I just checked the bios , The back up and bios in use are both the same from 2011 .. .Assume that is stock bios .. wonder if should update it and see if that helps.

 

Steaming via Steamlink or nzxt doko.  

 The plan is to project [Stream] VM pc's to the TVs so I can get rid of these old one and save alot of room.  Will just be for general use no gaming.  I think I like Steamlink better , more control over the stream and resolution ... the Doko does some weird cropping.  I have got both the work in Virtual BOX, however with out their own GPU it can get A bit laggy.  Thats where unRAID / GPU passthrew and some cheap GT 710s come in.

 

....

 

another thought .. 

I was reading something about black listing  ( trying to find the post ) ..

Could I black list that HDMI audio from the VM and make it never see it ?

updating won't help the problem.

 

If you're using windows as an os, you might be able to use a "virtual" sound card program in windows and use that to stream audio.....

when edit the syslinux.cfg does it matter where I put the lines ?

 

is the syslinux.cfg- A backup if I mess something up ?

 

Edited April 13, 20179 yr by Neko77025

6 hours ago, Neko77025 said:

when edit the syslinux.cfg does it matter where I put the lines ?

 

is the syslinux.cfg- A backup if I mess something up ?

 

 

 

matters and should look like this:

 

default /syslinux/menu.c32
menu title Lime Technology, Inc.
prompt 0
timeout 50
label unRAID OS
  menu default
  kernel /bzimage
  append vfio_iommu_type1.allow_unsafe_interrupts=1 initrd=/bzroot
label unRAID OS GUI Mode
  kernel /bzimage
  append initrd=/bzroot,/bzroot-gui
label unRAID OS Safe Mode (no plugins, no GUI)
  kernel /bzimage
  append initrd=/bzroot unraidsafemode
label Memtest86+
  kernel /memtest

 

no backups!

 

 

Thank you for all the help 1812.  However I am giving up on unRAID. have other issues now ... not even sure where to begin with them .. Going back to ESXi / VMware.  Was fun but it hates my hardware and I need too move on.

 

Thanks again, Sorry I wasted your time.