Intel 520 Integrated Graphics Card Passthrough Issues on Proxmox 6.2-4

tachang

Member
Jun 29, 2020
8
0
21
43
I am having issues getting my Intel 520 integrated graphics card passing through on qemu. I am using Proxmox Virtual Environment 6.2-4.

I tried a number of different things documented here:
https://gist.github.com/tachang/66d0db979aa6d9149a5a284e15b9bd74

For the most part just getting a blank screen and fault code.

`DMAR: [DMA Write] Request device [00:02.0] PASID ffffffff fault addr 0 [fault reason 02] Present bit in context entry is clear
 
any progress?

Im having same issue.

Its an laptop dell 2 in 1 with 6200U processor and intel 520 gpu. I manage to passthrought however this error occors and I get no HW accelation
ubuntu recognizes it as llvmpipe. with mint as guest gpu gets corretly recognized, howver no HW accelaration..

I think iǘe tried every combination possible. no sucess

appreciate any help
 
root@i5b:~# dmesg | grep DMAR
[ 0.011465] ACPI: DMAR 0x00000000A8729488 0000F0 (v01 INTEL SKL 00000001 INTL 00000001)
[ 0.081138] DMAR: IOMMU enabled
[ 0.161989] DMAR: Host address width 39
[ 0.161991] DMAR: DRHD base: 0x000000fed90000 flags: 0x0
[ 0.161999] DMAR: dmar0: reg_base_addr fed90000 ver 1:0 cap 1c0000c40660462 ecap 7e3ff0505e
[ 0.162001] DMAR: DRHD base: 0x000000fed91000 flags: 0x1
[ 0.162006] DMAR: dmar1: reg_base_addr fed91000 ver 1:0 cap d2008c40660462 ecap f050da
[ 0.162008] DMAR: RMRR base: 0x000000a8497000 end: 0x000000a84b6fff
[ 0.162010] DMAR: RMRR base: 0x000000ab000000 end: 0x000000af7fffff
[ 0.162012] DMAR: ANDD device: 1 name: \_SB.PCI0.I2C0
[ 0.162013] DMAR: ANDD device: 2 name: \_SB.PCI0.I2C1
[ 0.162023] DMAR-IR: IOAPIC id 2 under DRHD base 0xfed91000 IOMMU 1
[ 0.162025] DMAR-IR: HPET id 0 under DRHD base 0xfed91000
[ 0.162029] DMAR-IR: x2apic is disabled because BIOS sets x2apic opt out bit.
[ 0.162029] DMAR-IR: Use 'intremap=no_x2apic_optout' to override the BIOS setting.
[ 0.162342] DMAR: DRHD: handling fault status reg 2
[ 0.162346] DMAR: [DMA Read] Request device [00:17.0] PASID ffffffff fault addr a8455000 [fault reason 06] PTE Read access is not set
[ 0.163591] DMAR-IR: Enabled IRQ remapping in xapic mode
[ 0.937897] DMAR: ACPI device "device:64" under DMAR at fed91000 as 00:15.0
[ 0.937902] DMAR: ACPI device "device:65" under DMAR at fed91000 as 00:15.1
[ 0.937912] DMAR: No ATSR found
[ 0.937958] DMAR: dmar0: Using Queued invalidation
[ 0.937964] DMAR: dmar1: Using Queued invalidation
[ 0.938367] DMAR: Intel(R) Virtualization Technology for Directed I/O
[ 5.747529] ath10k_pci 0000:01:00.0: DMAR: 32bit DMA uses non-identity mapping
[ 90.176190] DMAR: DRHD: handling fault status reg 2
[ 90.176198] DMAR: [DMA Write] Request device [00:02.0] PASID ffffffff fault addr 0 [fault reason 02] Present bit in context entry is clear
[ 108.764218] DMAR: DRHD: handling fault status reg 2
[ 108.764226] DMAR: [DMA Read] Request device [00:02.0] PASID ffffffff fault addr ab802000 [fault reason 05] PTE Write access is not set
[ 108.764235] DMAR: DRHD: handling fault status reg 3
[ 108.764238] DMAR: [DMA Read] Request device [00:02.0] PASID ffffffff fault addr ab802000 [fault reason 05] PTE Write access is not set
[ 108.764274] DMAR: DRHD: handling fault status reg 3
[ 108.764277] DMAR: [DMA Read] Request device [00:02.0] PASID ffffffff fault addr ab803000 [fault reason 05] PTE Write access is not set
[ 108.764310] DMAR: DRHD: handling fault status reg 3
[ 113.773275] DMAR: DRHD: handling fault status reg 3
[ 113.773283] DMAR: [DMA Read] Request device [00:02.0] PASID ffffffff fault addr ad029000 [fault reason 06] PTE Read access is not set
[ 113.773712] DMAR: DRHD: handling fault status reg 3
[ 113.773717] DMAR: [DMA Read] Request device [00:02.0] PASID ffffffff fault addr ad040000 [fault reason 06] PTE Read access is not set
[ 113.789970] DMAR: DRHD: handling fault status reg 3
[ 113.789980] DMAR: [DMA Read] Request device [00:02.0] PASID ffffffff fault addr ad029000 [fault reason 06] PTE Read access is not set
[ 113.790396] DMAR: DRHD: handling fault status reg 3
[ 172.108008] DMAR: DRHD: handling fault status reg 3
[ 172.108018] DMAR: [DMA Read] Request device [00:02.0] PASID ffffffff fault addr ab806000 [fault reason 06] PTE Read access is not set
[ 172.108649] DMAR: DRHD: handling fault status reg 3
[ 172.108655] DMAR: [DMA Read] Request device [00:02.0] PASID ffffffff fault addr ab83b000 [fault reason 06] PTE Read access is not set
[ 172.109062] DMAR: DRHD: handling fault status reg 3
[ 172.109070] DMAR: [DMA Read] Request device [00:02.0] PASID ffffffff fault addr ab83b000 [fault reason 06] PTE Read access is not set
[ 172.109491] DMAR: DRHD: handling fault status reg 3
 
I have managed to get this to work.

My string was:
-device vfio-pci,host=0000:00:02.0,id=hostpci0,bus=pci.0,addr=0x10,x-igd-opregion=on,romfile=/usr/share/kvm/i915ovmf.rom

And I used this ROM: https://github.com/HouQiming/i915ovmfPkg

You have to make sure you are on the right version of proxmox. And then you have to edit the conf file manually and put in the romfile and x-igd-opregion=on.
 
im using

PVE Manager Version
pve-manager/6.2-4/9824574a

same as you I believe. Tried your steps.. still no luck.

May you provide your confs update, please?

Ubuntu 20.04.1, gpu get llvmpipe... no hw acc at all.

what am i missing?

Code:
root@i5b:~# dmesg | grep DMAR[    0.011046] ACPI: DMAR 0x00000000A8729488 0000F0 (v01 INTEL  SKL      00000001 INTL 00000001)[    0.080685] DMAR: IOMMU enabled[    0.161559] DMAR: Host address width 39[    0.161561] DMAR: DRHD base: 0x000000fed90000 flags: 0x0[    0.161568] DMAR: dmar0: reg_base_addr fed90000 ver 1:0 cap 1c0000c40660462 ecap 7e3ff0505e[    0.161570] DMAR: DRHD base: 0x000000fed91000 flags: 0x1[    0.161575] DMAR: dmar1: reg_base_addr fed91000 ver 1:0 cap d2008c40660462 ecap f050da[    0.161577] DMAR: RMRR base: 0x000000a8497000 end: 0x000000a84b6fff[    0.161579] DMAR: RMRR base: 0x000000ab000000 end: 0x000000af7fffff
[    0.161581] DMAR: ANDD device: 1 name: \_SB.PCI0.I2C0
[    0.161582] DMAR: ANDD device: 2 name: \_SB.PCI0.I2C1
[    0.161585] DMAR-IR: IOAPIC id 2 under DRHD base  0xfed91000 IOMMU 1
[    0.161587] DMAR-IR: HPET id 0 under DRHD base 0xfed91000
[    0.161588] DMAR-IR: x2apic is disabled because BIOS sets x2apic opt out bit.
[    0.161589] DMAR-IR: Use 'intremap=no_x2apic_optout' to override the BIOS setting.
[    0.163150] DMAR-IR: Enabled IRQ remapping in xapic mode
[    0.933043] DMAR: ACPI device "device:64" under DMAR at fed91000 as 00:15.0
[    0.933047] DMAR: ACPI device "device:65" under DMAR at fed91000 as 00:15.1
[    0.933058] DMAR: No ATSR found
[    0.933088] DMAR: dmar0: Using Queued invalidation
[    0.933094] DMAR: dmar1: Using Queued invalidation
[    0.933481] DMAR: Intel(R) Virtualization Technology for Directed I/O
[    5.797622] ath10k_pci 0000:01:00.0: DMAR: 32bit DMA uses non-identity mapping
[ 2317.172048] DMAR: DRHD: handling fault status reg 2
[ 2317.172057] DMAR: [DMA Write] Request device [00:02.0] PASID ffffffff fault addr 0 [fault reason 02] Present bit in context entry is clear
[ 2317.182701] DMAR: DRHD: handling fault status reg 3
[ 2317.182710] DMAR: [DMA Read] Request device [00:02.0] PASID ffffffff fault addr ab800000 [fault reason 06] PTE Read access is not set
[ 2317.183142] DMAR: DRHD: handling fault status reg 3
[ 2317.183146] DMAR: [DMA Read] Request device [00:02.0] PASID ffffffff fault addr ab837000 [fault reason 06] PTE Read access is not set
[ 2317.183600] DMAR: DRHD: handling fault status reg 3
[ 2351.343079] DMAR: DRHD: handling fault status reg 2
[ 2351.343089] DMAR: [DMA Write] Request device [00:02.0] PASID ffffffff fault addr 0 [fault reason 02] Present bit in context entry is clear


Code:
/usr/bin/kvm -id 101 -name tst-ubuntu -chardev 'socket,id=qmp,path=/var/run/qemu-server/101.qmp,server,nowait' -mon 'chardev=qmp,mode=control' -chardev 'socket,id=qmp-event,path=/var/run/qmeventd.sock,reconnect=5' -mon 'chardev=qmp-event,mode=control' -pidfile /var/run/qemu-server/101.pid -daemonize -smbios 'type=1,uuid=2c128b4e-417a-4970-b235-e02c3997c22f' -drive 'if=pflash,unit=0,format=raw,readonly,file=/usr/share/pve-edk2-firmware//OVMF_CODE.fd' -drive 'if=pflash,unit=1,format=raw,id=drive-efidisk0,size=131072,file=/dev/pve/vm-101-disk-1' -smp '2,sockets=1,cores=2,maxcpus=2' -nodefaults -boot 'menu=on,strict=on,reboot-timeout=1000,splash=/usr/share/qemu-server/bootsplash.jpg' -vga none -nographic -cpu 'kvm64,enforce,kvm=off,+kvm_pv_eoi,+kvm_pv_unhalt,+lahf_lm,+sep' -m 4096 -device 'pci-bridge,id=pci.1,chassis_nr=1,bus=pci.0,addr=0x1e' -device 'pci-bridge,id=pci.2,chassis_nr=2,bus=pci.0,addr=0x1f' -device 'vmgenid,guid=726b8491-44c3-4b39-803e-163d658bb983' -device 'piix3-usb-uhci,id=uhci,bus=pci.0,addr=0x1.0x2' -device 'usb-tablet,id=tablet,bus=uhci.0,port=1' -device 'vfio-pci,host=0000:00:02.0,id=hostpci0,bus=pci.0,addr=0x10,x-igd-opregion=on,romfile=/usr/share/kvm/i915ovmf.rom' -iscsi 'initiator-name=iqn.1993-08.org.debian:01:dc8a8fd629e4' -drive 'file=/var/lib/vz/template/iso/ubuntu-20.04.1-desktop-amd64.iso,if=none,id=drive-ide2,media=cdrom,aio=threads' -device 'ide-cd,bus=ide.1,unit=0,drive=drive-ide2,id=ide2,bootindex=200' -device 'virtio-scsi-pci,id=scsihw0,bus=pci.0,addr=0x5' -drive 'file=/dev/pve/vm-101-disk-0,if=none,id=drive-scsi0,format=raw,cache=none,aio=native,detect-zeroes=on' -device 'scsi-hd,bus=scsihw0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0,id=scsi0,bootindex=100' -netdev 'type=tap,id=net0,ifname=tap101i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown,vhost=on' -device 'virtio-net-pci,mac=72:81:14:C5:E8:6C,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=300' -machine 'type=pc+pve0'



thank you
 
When I wrote the thread it was
Virtual Environment 6.2-4 which had a bug.

You need Virtual Environment 6.2-6
 
thanks!
Im digging in to update it.
Just curious if is this version only avaliable for enterprise subscription? Iḿ only have community.
Im trying to update, i will come here after with news.
 
still nothing...
graphics still llvmpipe (LLVM 10.0.0, 128 bits)
(im conectiong trhough xrdp, may it affects?)

I may be missing some config..

Also, i noticed that i see ubuntu screen at my laptop monitor.
 
So frustrating.. xrdp keeps falling back to llvmpipe ..

Will have to give up keep windows running
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!