PassthroughXeon E3-1200 v2/3rd Gen Core processor Graphics Controller

[peter_sm]

Hi!

I'm trying tp pass trough my iGPU, FYI ! this have been OK without any error in the past when starting the VM. I'm going to see if my OSX VM can handle this better than my HD 5450 GPU

 

i have tested this with iGPU in earlier beta for Windows without no success to install drivers for the iGPU, something must have been changes. never have got this error when starting VM.

 

All other PCI devices work fine to passtrough ! its only 00:02.0 that gives error.

 

this is the error I got

 

rror: internal error: early end of file from monitor: possible problem:
2014-12-08T20:06:24.904673Z qemu-system-x86_64: -device vfio-pci,host=00:02.0,bus=pcie.0,multifunction=on: vfio: failed to set iommu for container: Operation not permitted
2014-12-08T20:06:24.904697Z qemu-system-x86_64: -device vfio-pci,host=00:02.0,bus=pcie.0,multifunction=on: vfio: failed to setup container for group 2
2014-12-08T20:06:24.904703Z qemu-system-x86_64: -device vfio-pci,host=00:02.0,bus=pcie.0,multifunction=on: vfio: failed to get group 2
2014-12-08T20:06:24.904711Z qemu-system-x86_64: -device vfio-pci,host=00:02.0,bus=pcie.0,multifunction=on: Device initialization failed.
2014-12-08T20:06:24.904719Z qemu-system-x86_64: -device vfio-pci,host=00:02.0,bus=pcie.0,multifunction=on: Device 'vfio-pci' could not be initialized

 

This is the iGPU, its already vfio-pci

00:02.0 Display controller [0380]: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0162] (rev 09)
Subsystem: ASRock Incorporation Device [1849:0162]
Kernel driver in use: vfio-pci

 

My xml code

 

<qemu:commandline>
    <qemu:arg value='-device'/>
    <qemu:arg value='vfio-pci,host=00:02.0,bus=pcie.0,multifunction=on'/>
  </qemu:commandline>

[archedraft]

Here is what I get if I try and pass through my iGPU

error: Failed to start domain OSX-Mavericks-10.9-test2
error: internal error: early end of file from monitor: possible problem:
2014-12-08T22:54:03.029230Z qemu-system-x86_64: -device vfio-pci,host=00:02.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on: vfio: failed to set iommu for container: Operation not permitted
2014-12-08T22:54:03.029266Z qemu-system-x86_64: -device vfio-pci,host=00:02.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on: vfio: failed to setup container for group 2
2014-12-08T22:54:03.029276Z qemu-system-x86_64: -device vfio-pci,host=00:02.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on: vfio: failed to get group 2
2014-12-08T22:54:03.029290Z qemu-system-x86_64: -device vfio-pci,host=00:02.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on: Device initialization failed.
2014-12-08T22:54:03.029302Z qemu-system-x86_64: -device vfio-pci,host=00:02.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on: Device 'vfio-pci' could not be initialized

[peter_sm]

Thanks for confirmation this, then there is defiantly something that have been changes, LT can you please take a look what's is causing this?

[peter_sm]

I have this line in my syslog

 

vfio-pci 0000:00:02.0: Device is ineligible for IOMMU domain attach due to platform RMRR requirement.  Contact your platform vendor.

 

Are LimeTech my plaftorm vendor ;-)

 

//Peter

[peter_sm]

I found this discussion with Alex williamson at redhat  and Daniel Vetter at Intel

 

http://www.gossamer-threads.com/lists/linux/kernel/1944482

 

//Peter

[peter_sm]

iommu/intel: Exclude devices using RMRRs from IOMMU API domains

 

https://lkml.org/lkml/2014/6/13/394

 

Looks like we are stuck with this issue?

//P

 

[jonp]

Hey guys, igpu passthrough is still not supported (on either Xen or KVM).  There are some folks that have been able to get it to work with very specific kernel versions in very specific situations (or so have claimed) but not very many and there are numerous bugs with this at this time.

 

We are not performing any further testing on iGPU pass through until after the release of 6.0.  There are things potentially coming from the upstream in terms of iGPU passthrough (Xen 4.5, Linux 3.18 kernel, etc.) that may help with this, but those are still just a bit out from hitting unRAID yet (3.18.0 was just recently released and Xen 4.5 hasn't hit yet).

 

- Jon