Page 1 of 1

[4.2.16] PCI passthrough now fails with newer kernels

Posted: 3. Sep 2013, 17:26
by ucrasher
Hi,
since almost a year I use PCI passthrough successfully on an Ububtu 12.04 host (guest is Win7).
viewtopic.php?f=7&t=49322&p=238575&hili ... gh#p238575

The host kernel was 3.2.x. Recently I upgraded the kernel to 3.8.x. Now the PCI passthrough fails. In the syslog I find this after the VM has been started:

Code: Select all

[23563.237010] created IOMMU domain ffff88000f2c2b00
[23573.529777] dmar: DMAR:[DMA Read] Request device [00:1d.0] fault addr d4c9e000 
[23573.529777] DMAR:[fault reason 06] PTE Read access is not set
Is this a known effect? Or would you guys expect it to work fine? Does this ring a bell with somebody? Any hints are very welcome!
Windows (guest) sees the device (a USB host), but cannot start it (Error 43).

I also tried with 3.10 and 3.11 kernels - same result.
Running the old 3.2 kernel does not show the error.

Thanks!

Re: [4.2.16/5.0.16] PCI passthrough now fails with newer kernels

Posted: 12. Apr 2016, 15:16
by ucrasher
Hi,
just an update since the problem still exists.
Now using Ubuntu 14.04 with kernel 4.2 from Wily. VB is 5.016.

syslog

Code: Select all

vboxpci 0000:00:1d.0: reg=0 start=f7f17000 size=1024
DMAR: DRHD: handling fault status reg 3
DMAR: DMAR:[DMA Read] Request device [00:1d.0] fault addr 697e2000 
DMAR:[fault reason 06] PTE Read access is not set
kernel cmd line:

Code: Select all

iommu=pt intel_iommu=on intel_iommu=igfx_off
I also ensured that xhci/ehci handover is disabled in BIOS (since this is a USB controller).

With a Linux guest, I see the device with lspci, but it probably does not get interrupts.
My guess is that the above failure prevents them to get passed into the VM.

Re: [4.2.16] PCI passthrough now fails with newer kernels

Posted: 12. Apr 2016, 15:18
by ucrasher
The log file with a Linux guest.

Re: [4.2.16] PCI passthrough now fails with newer kernels

Posted: 30. Apr 2016, 17:25
by Struhio
Yes this is still issue with Ubuntu 16.04 + VirtualBox 5.0.20.
I've got devices that successfully run under QEMU-KVM, but do not want to work in VirtualBox.

This clearly VB issue, too bad they are not fixing this.