New to unRAID, having VM issues, troubleshooting underway

[wabniky]

Execution error

internal error: process exited while connecting to monitor: 2017-08-13T20:48:59.231677Z qemu-system-x86_64: -device vfio-pci,host=0c:00.0,id=hostdev0,bus=pci.0,addr=0x6: vfio: failed to set iommu for container: Operation not permitted
2017-08-13T20:48:59.231709Z qemu-system-x86_64: -device vfio-pci,host=0c:00.0,id=hostdev0,bus=pci.0,addr=0x6: vfio: failed to setup container for group 22
2017-08-13T20:48:59.231714Z qemu-system-x86_64: -device vfio-pci,host=0c:00.0,id=hostdev0,bus=pci.0,addr=0x6: vfio: failed to get group 22
2017-08-13T20:48:59.231725Z qemu-system-x86_64: -device vfio-pci,host=0c:00.0,id=hostdev0,bus=pci.0,addr=0x6: Device initialization failed

I'm getting the  error above when attempting to start a VM I just made. I'm trying to pass through my GTX 1080Ti but I hit this error. I've tried the solution I see everywhere to enable PCIe ACS Override but no dice.

 

I'm going to keep working to try and find  a workaround. Please let me know if there's an easy way around this so I can keep my sanity for another day.

[Squid]

Probably a stupid question, but are you also passing through the audio portion of the card?

[wabniky]

6 minutes ago, Squid said:

Probably a stupid question, but are you also passing through the audio portion of the card?

 

I've tried with and without passing it through

[Squid]

You really should post your diagnostics though.

[wabniky]

18 minutes ago, wabniky said:

Execution error

internal error: process exited while connecting to monitor: 2017-08-13T20:48:59.231677Z qemu-system-x86_64: -device vfio-pci,host=0c:00.0,id=hostdev0,bus=pci.0,addr=0x6: vfio: failed to set iommu for container: Operation not permitted
2017-08-13T20:48:59.231709Z qemu-system-x86_64: -device vfio-pci,host=0c:00.0,id=hostdev0,bus=pci.0,addr=0x6: vfio: failed to setup container for group 22
2017-08-13T20:48:59.231714Z qemu-system-x86_64: -device vfio-pci,host=0c:00.0,id=hostdev0,bus=pci.0,addr=0x6: vfio: failed to get group 22
2017-08-13T20:48:59.231725Z qemu-system-x86_64: -device vfio-pci,host=0c:00.0,id=hostdev0,bus=pci.0,addr=0x6: Device initialization failed

Execution error

internal error: process exited while connecting to monitor: 2017-08-13T21:06:27.704062Z qemu-system-x86_64: -device vfio-pci,host=0c:00.0,id=hostdev0,bus=pci.0,addr=0x6: vfio: failed to set iommu for container: Operation not permitted
2017-08-13T21:06:27.704093Z qemu-system-x86_64: -device vfio-pci,host=0c:00.0,id=hostdev0,bus=pci.0,addr=0x6: vfio: failed to setup container for group 18
2017-08-13T21:06:27.704097Z qemu-system-x86_64: -device vfio-pci,host=0c:00.0,id=hostdev0,bus=pci.0,addr=0x6: vfio: failed to get group 18
2017-08-13T21:06:27.704108Z qemu-system-x86_64: -device vfio-pci,host=0c:00.0,id=hostdev0,bus=pci.0,addr=0x6: Device initialization failed

Here is a side-by-side of error output between having ACS Override enabled (top) and disabled (bottom) in case that's relevant.

 

[wabniky]

Diag attached

hq-diagnostics-20170813-1715.zip

[1812]

Group 22 has a sata controller and pci bridge trying to be passed to the vm. vm's don't like pci bridges.

 

group 18 has a pci bridge and the gpu with it's audio component.

 

 

Your logs also contain this message:

 

 

 vfio_iommu_type1_attach_group: No interrupt remapping support.  Use the module param "allow_unsafe_interrupts" to enable VFIO IOMMU support on this platform

 

To do this, click on the link to the hp prolaint thread in my signature, follow the directions in Step 3 of the vm problems section to allow unsafe interrupts. Then reboot, try again. if it doesn't work, post new diagnostics.

 

 

 

 

[wabniky]

Odd question; does this work if I boot to GUI or would I have to append this to that line as well?

[wabniky]

Made the change to the one line as mentioned, still receiving error;

 

Execution error

internal error: qemu unexpectedly closed the monitor: 2017-08-13T23:50:50.194275Z qemu-system-x86_64: -device vfio-pci,host=0c:00.0,id=hostdev0,bus=pci.0,addr=0x8: vfio: failed to set iommu for container: Operation not permitted
2017-08-13T23:50:50.194309Z qemu-system-x86_64: -device vfio-pci,host=0c:00.0,id=hostdev0,bus=pci.0,addr=0x8: vfio: failed to setup container for group 18
2017-08-13T23:50:50.194313Z qemu-system-x86_64: -device vfio-pci,host=0c:00.0,id=hostdev0,bus=pci.0,addr=0x8: vfio: failed to get group 18
2017-08-13T23:50:50.194324Z qemu-system-x86_64: -device vfio-pci,host=0c:00.0,id=hostdev0,bus=pci.0,addr=0x8: Device initialization failed

 

hq-diagnostics-20170813-1952.zip

[1812]

39 minutes ago, wabniky said:

Odd question; does this work if I boot to GUI or would I have to append this to that line as well?

 

Only works when added to first append/top level boot. If you want it enabled on GUI mode, it has to be there as well ( as I have understood it.)

[1812]

7 minutes ago, wabniky said:

Made the change to the one line as mentioned, still receiving error;

 

 

hq-diagnostics-20170813-1952.zip

 

 

These diagnostics are probably from your GUI boot since the unsafe interrupts line is missing from them. Please either add the line to GUI boot or boot normally and try to start the vm. If it doesn't work, then post diagnostics from that.

[wabniky]

Did a normal boot after last post and got it working. I'll get around to adding the line to the guidance boot once I get the vm up and running.

 

I can't thank you enough for your help! 

[1812]

17 minutes ago, wabniky said:

Did a normal boot after last post and got it working. I'll get around to adding the line to the guidance boot once I get the vm up and running.

 

I can't thank you enough for your help! 

 

Not a problem. I remember when I was new to all this. I couldn't have gotten up and going if it weren't for others in this great community.