GPU Passthough Not working. VM will not start


spotopolis

Recommended Posts

I can and have always booted my VM with just the VMC option.  I try to select the GPU (Quadro NVS 295) and hit update and that works, but then when I try to start the VM, unRAID gives me an error (not in the VM)

 

Execution error

internal error: early end of file from monitor: possible problem:
2015-09-25T17:20:19.578593Z qemu-system-x86_64: -device vfio-pci,host=0f:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on: vfio: failed to set iommu for container: Operation not permitted
2015-09-25T17:20:19.578628Z qemu-system-x86_64: -device vfio-pci,host=0f:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on: vfio: failed to setup container for group 14
2015-09-25T17:20:19.578638Z qemu-system-x86_64: -device vfio-pci,host=0f:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on: vfio: failed to get group 14
2015-09-25T17:20:19.578651Z qemu-system-x86_64: -device vfio-pci,host=0f:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on: Device initialization failed
2015-09-25T17:20:19.578663Z qemu-system-x86_64: -device vfio-pci,host=0f:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on: Device 'vfio-pci' could not be initialized

 

If I go back to just the VNC option it works fine again. Im not sure what I need to do. I havent found any other issues like this on the forum. All I see are the error 43's inside Windows once the VM boots.

Link to comment

I can and have always booted my VM with just the VMC option.  I try to select the GPU (Quadro NVS 295) and hit update and that works, but then when I try to start the VM, unRAID gives me an error (not in the VM)

 

Execution error

internal error: early end of file from monitor: possible problem:
2015-09-25T17:20:19.578593Z qemu-system-x86_64: -device vfio-pci,host=0f:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on: vfio: failed to set iommu for container: Operation not permitted
2015-09-25T17:20:19.578628Z qemu-system-x86_64: -device vfio-pci,host=0f:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on: vfio: failed to setup container for group 14
2015-09-25T17:20:19.578638Z qemu-system-x86_64: -device vfio-pci,host=0f:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on: vfio: failed to get group 14
2015-09-25T17:20:19.578651Z qemu-system-x86_64: -device vfio-pci,host=0f:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on: Device initialization failed
2015-09-25T17:20:19.578663Z qemu-system-x86_64: -device vfio-pci,host=0f:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on: Device 'vfio-pci' could not be initialized

 

If I go back to just the VMC option it works fine again. Im not sure what I need to do. I havent found any other issues like this on the forum. All I see are the error 43's inside Windows once the VM boots.

 

http://lime-technology.com/wiki/index.php/UnRAID_6/VM_Management#Help.21_Failed_to_set_iommu_for_container:_Operation_not_permitted

 

Just added that to the wiki.  Been meaning to do that anyway...

 

 

Link to comment

Now after the ACS set to YES and a reboot, I am getting a group 15 error.

 

internal error: early end of file from monitor: possible problem:
2015-09-25T17:44:03.870643Z qemu-system-x86_64: -device vfio-pci,host=0f:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on: vfio: failed to set iommu for container: Operation not permitted
2015-09-25T17:44:03.870672Z qemu-system-x86_64: -device vfio-pci,host=0f:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on: vfio: failed to setup container for group 15
2015-09-25T17:44:03.870680Z qemu-system-x86_64: -device vfio-pci,host=0f:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on: vfio: failed to get group 15
2015-09-25T17:44:03.870691Z qemu-system-x86_64: -device vfio-pci,host=0f:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on: Device initialization failed
2015-09-25T17:44:03.870701Z qemu-system-x86_64: -device vfio-pci,host=0f:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on: Device 'vfio-pci' could not be initialized

 

Here is the list of my IOMMU Groups. If I understand it correctly, group 15, the GPU, is no longer in a shared group if that was the issue before.

 

/sys/kernel/iommu_groups/0/devices/0000:00:00.0
/sys/kernel/iommu_groups/1/devices/0000:00:01.0
/sys/kernel/iommu_groups/2/devices/0000:00:03.0
/sys/kernel/iommu_groups/3/devices/0000:00:07.0
/sys/kernel/iommu_groups/4/devices/0000:00:10.0
/sys/kernel/iommu_groups/4/devices/0000:00:10.1
/sys/kernel/iommu_groups/5/devices/0000:00:11.0
/sys/kernel/iommu_groups/5/devices/0000:00:11.1
/sys/kernel/iommu_groups/6/devices/0000:00:14.0
/sys/kernel/iommu_groups/6/devices/0000:00:14.1
/sys/kernel/iommu_groups/6/devices/0000:00:14.2
/sys/kernel/iommu_groups/7/devices/0000:00:15.0
/sys/kernel/iommu_groups/8/devices/0000:00:1a.0
/sys/kernel/iommu_groups/8/devices/0000:00:1a.1
/sys/kernel/iommu_groups/8/devices/0000:00:1a.2
/sys/kernel/iommu_groups/8/devices/0000:00:1a.7
/sys/kernel/iommu_groups/9/devices/0000:00:1b.0
/sys/kernel/iommu_groups/10/devices/0000:00:1c.0
/sys/kernel/iommu_groups/11/devices/0000:00:1c.5
/sys/kernel/iommu_groups/12/devices/0000:00:1d.0
/sys/kernel/iommu_groups/12/devices/0000:00:1d.1
/sys/kernel/iommu_groups/12/devices/0000:00:1d.2
/sys/kernel/iommu_groups/12/devices/0000:00:1d.7
/sys/kernel/iommu_groups/13/devices/0000:00:1e.0
/sys/kernel/iommu_groups/13/devices/0000:37:05.0
/sys/kernel/iommu_groups/14/devices/0000:00:1f.0
/sys/kernel/iommu_groups/14/devices/0000:00:1f.2
/sys/kernel/iommu_groups/15/devices/0000:0f:00.0
/sys/kernel/iommu_groups/16/devices/0000:01:00.0
/sys/kernel/iommu_groups/17/devices/0000:3f:00.0
/sys/kernel/iommu_groups/17/devices/0000:3f:00.1
/sys/kernel/iommu_groups/18/devices/0000:3f:02.0
/sys/kernel/iommu_groups/18/devices/0000:3f:02.1
/sys/kernel/iommu_groups/19/devices/0000:3f:03.0
/sys/kernel/iommu_groups/19/devices/0000:3f:03.1
/sys/kernel/iommu_groups/19/devices/0000:3f:03.4
/sys/kernel/iommu_groups/20/devices/0000:3f:04.0
/sys/kernel/iommu_groups/20/devices/0000:3f:04.1
/sys/kernel/iommu_groups/20/devices/0000:3f:04.2
/sys/kernel/iommu_groups/20/devices/0000:3f:04.3
/sys/kernel/iommu_groups/21/devices/0000:3f:05.0
/sys/kernel/iommu_groups/21/devices/0000:3f:05.1
/sys/kernel/iommu_groups/21/devices/0000:3f:05.2
/sys/kernel/iommu_groups/21/devices/0000:3f:05.3
/sys/kernel/iommu_groups/22/devices/0000:3f:06.0
/sys/kernel/iommu_groups/22/devices/0000:3f:06.1
/sys/kernel/iommu_groups/22/devices/0000:3f:06.2
/sys/kernel/iommu_groups/22/devices/0000:3f:06.3

Link to comment

I had the same issue.

updated bios, poof, fixed.

 

The bios for my system is up to date. Not the issue unfortunately.

 

Do you get the same message if you add this after pcie_acs_override=downstream in your syslinux.cfg?

vfio_iommu_type1.allow_unsafe_interrupts=1

 

This is what my syslinux.cfg looks like. Do I add your line after "downstream" or after "bzroot"?

default /syslinux/menu.c32
menu title Lime Technology
prompt 0
timeout 50
label unRAID OS
  menu default
  kernel /bzimage
  append pcie_acs_override=downstream initrd=/bzroot
label unRAID OS Safe Mode (no plugins)
  kernel /bzimage
  append initrd=/bzroot unraidsafemode
label Memtest86+
  kernel /memtest
label Xen/unRAID OS
  kernel /syslinux/mboot.c32
  append /xen --- /bzimage --- /bzroot
label Xen/unRAID OS Safe Mode (no plugins)
  kernel /syslinux/mboot.c32
  append /xen --- /bzimage --- /bzroot unraidsafemode

Link to comment

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

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.