PCI passthrough ERROR since Kernel 5.13.19-1 (upgrade from 7.0 to 7.1)

derMischka · Jul 20, 2022

update:

Bash:

root@nas:~# qm start 110
kvm: -device vfio-pci,host=0000:00:02.0,id=hostpci0,bus=pci.0,addr=0x10: vfio 0000:00:02.0: error getting device from group 1: Invalid argument
Verify all devices in group 1 are bound to vfio-<bus> or pci-stub and not already in use
start failed: QEMU exited with code 1
root@nas:~# uname -r
5.15.39-1-pve

derMischka · Jul 20, 2022

Maybe someone have enough skills to use this information:

https://github.com/intel/gvt-linux/commit/58586680ffadc37636120d9f59955aa5f7a32b7d

bolzerrr · Oct 26, 2022

Just gave it another try with:
Linux pve 5.15.64-1-pve #1 SMP PVE 5.15.64-1 (Thu, 13 Oct 2022 10:30:34 +0200) x86_64 GNU/Linux

Still failing. Anyone got it working in the meantime?

Code:

[84549.654775] DMAR: DRHD: handling fault status reg 2
[84549.654789] DMAR: [DMA Write NO_PASID] Request device [00:02.0] fault addr 0x0 [fault reason 0x02] Present bit in context entry is clear
[84552.997855] vfio-pci 0000:00:02.0: vfio_ecap_init: hiding ecap 0x1b@0x100
[84552.997908] vfio-pci 0000:00:02.0: IGD assignment does not support opregion v2.0 with an extended VBT region
[84552.997919] vfio-pci 0000:00:02.0: Failed to setup Intel IGD regions
[84553.262672] DMAR: DRHD: handling fault status reg 2
[84553.262686] DMAR: [DMA Write NO_PASID] Request device [00:02.0] fault addr 0x0 [fault reason 0x02] Present bit in context entry is clear

kilonde · Apr 18, 2023

Also no luck for me with 5.15.102-1-pve kernel with J5005, as suggested earlier in the thread, the older one worked.

Download the old kernel:

Code:

apt install pve-kernel 5.11.22-7-pve

test by using the old kernel on next boot only

Code:

proxmox-boot-tool kernel pin 5.11.22-7-pve --next-boot

it worked for me so the below command pins it

Code:

proxmox-boot-tool kernel pin 5.11.22-7-pve

elektrinis · Dec 23, 2023

Still no fix? Have a similar issue on proxmox 8.1.

bolzerrr · Jan 9, 2024

I opened a report here: https://bugzilla.proxmox.com/show_bug.cgi?id=5168

trique · Feb 4, 2024

kilonde said:
Also no luck for me with 5.15.102-1-pve kernel with J5005, as suggested earlier in the thread, the older one worked.

Download the old kernel:

Code:

apt install pve-kernel 5.11.22-7-pve

test by using the old kernel on next boot only

Code:

proxmox-boot-tool kernel pin 5.11.22-7-pve --next-boot

it worked for me so the below command pins it

Code:

proxmox-boot-tool kernel pin 5.11.22-7-pve

I think I have the the same problem as you guys: Intel J4105, Kernel 5.15.136-1-pve. I try to passthrough the iGPU to a HAOS VM to speed up ffmpeg.
Passthrough of the Google Coral M.2 works, but not iGPU passthrough.
Have been reading and copy&pasting all about iGPU passthrough but when I start the VM I get the "QEMU exited with code 1" error log.
(My Linux skills don't go far beyond the "copy & paste" part. Seems like I wasted my youth

)

Sorry for the stupid question, but how can I download an old kernel? The

Code:

apt intall pve-kernel 5.11.22-7-pve

does not work for me:

Code:

E: Package 'pve-kernel' has no installation candidate
E: Unable to locate package 5.11.22-7-pve
E: Couldn't find any package by glob '5.11.22-7-pve'

My sources.list contain all "bullseye" links. Shouldn't this be the right version for 5.11. ?

Thanks a lot!

bolzerrr · Feb 5, 2024

I just gave the latest kernel a try and it seems the error is gone (Linux pve 6.5.11-7-pve #1 SMP PREEMPT_DYNAMIC PMX 6.5.11-7 (2023-12-05T09:44Z) x86_64 GNU/Linux)

I get this warning now:
[ 0.430482] pnp 00:03: disabling [mem 0xc0000000-0xcfffffff] because it overlaps 0000:00:02.0 BAR 9 [mem 0x00000000-0xdfffffff 64bit pref]

And the VM (Linux ALPINE-FULL 6.6.14-0-lts #1-Alpine SMP PREEMPT_DYNAMIC Fri, 26 Jan 2024 11:08:07 +0000 x86_64 GNU/Linux) complains:

Bash:

[    0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-lts root=UUID=316abd25-d40c-4008-9494-2d99f67e1d99 ro modules=sd-mod,usb-storage,ext4 quiet rootfstype=ext4 video=vesafb:off vga=normal nomodeset
[   37.246116] i915 0000:02:00.0: [drm] VT-d active for gfx access
[   37.246180] i915 0000:02:00.0: [drm] Using Transparent Hugepages
[   37.246183] i915 0000:02:00.0: [drm] *ERROR* conflict detected with stolen region: [mem 0x70800000-0x807fffff]
[   37.263156] i915 0000:02:00.0: BAR 6: can't assign [??? 0x00000000 flags 0x20000000] (bogus alignment)
[   37.263162] i915 0000:02:00.0: [drm] Failed to find VBIOS tables (VBT)
[   37.263558] i915 0000:02:00.0: vgaarb: VGA decodes changed: olddecodes=io+mem,decodes=none:owns=none
[   37.296802] i915 0000:02:00.0: [drm] Finished loading DMC firmware i915/adlp_dmc.bin (v2.20)
[   38.423184] i915 0000:02:00.0: [drm] [ENCODER:184:DDI A/PHY A] failed to retrieve link info, disabling eDP
[   38.423571] ------------[ cut here ]------------
[   38.423576] i915 0000:02:00.0: Platform does not support port C
[   38.423642] WARNING: CPU: 3 PID: 2577 at drivers/gpu/drm/i915/display/intel_display.c:7413 assert_port_valid+0x60/0x80 [i915]
[   38.424310] Modules linked in: i915(+) drm_buddy hwmon i2c_algo_bit ttm drm_display_helper cec video wmi intel_agp intel_gtt agpgart snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi snd_hda_codec snd_hda_core snd_hwdep snd_pcm snd_timer snd soundcore iTCO_wdt intel_pmc_bxt i2c_i801 iTCO_vendor_support i2c_smbus lpc_ich intel_rapl_msr input_leds intel_rapl_common kvm_intel kvm irqbypass crct10dif_pclmul ghash_clmulni_intel sha512_ssse3 sha256_ssse3 sha1_ssse3 aesni_intel crypto_simd cryptd rapl qemu_fw_cfg evdev button efivarfs hid_generic uas usbhid hid virtio_scsi virtio_net net_failover failover virtio_blk virtio_console sr_mod cdrom crc32_pclmul xhci_pci xhci_pci_renesas xhci_hcd uhci_hcd ehci_pci ehci_hcd virtio_pci virtio_pci_legacy_dev virtio_pci_modern_dev virtio_ring virtio ahci libahci libata simpledrm drm_shmem_helper drm_kms_helper drm drm_panel_orientation_quirks loop ext4 crc32c_generic crc32c_intel crc16 mbcache jbd2 usb_storage usbcore usb_common sd_mod t10_pi crc64_rocksoft crc64 scsi_mod scsi_common
[   38.424515] CPU: 3 PID: 2577 Comm: modprobe Tainted: G     U             6.6.14-0-lts #1-Alpine
[   38.424525] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 3.20230228-4 06/06/2023
[   38.424529] RIP: 0010:assert_port_valid+0x60/0x80 [i915]
[   38.425160] Code: 7f 08 8d 6e 41 4c 8b 67 50 4d 85 e4 75 03 4c 8b 27 e8 94 4e 7e d9 89 e9 4c 89 e2 48 c7 c7 70 33 1f c1 48 89 c6 e8 b0 d4 0b d9 <0f> 0b 89 d8 5b 5d 83 e0 01 41 5c 31 d2 31 c9 31 f6 31 ff c3 cc cc
[   38.425168] RSP: 0018:ffffb443008e79d0 EFLAGS: 00010246
[   38.425176] RAX: 0000000000000000 RBX: 000000000000001e RCX: 0000000000000000
[   38.425181] RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
[   38.425185] RBP: 0000000000000043 R08: 0000000000000000 R09: 0000000000000000
[   38.425189] R10: 0000000000000000 R11: 0000000000000000 R12: ffff97a180ef92b0
[   38.425194] R13: ffff97a1822e9aa8 R14: 0000000000000002 R15: ffff97a180e87000
[   38.425200] FS:  00007fd694c88b08(0000) GS:ffff97a4efd80000(0000) knlGS:0000000000000000
[   38.425207] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[   38.425212] CR2: 00007fb769834000 CR3: 00000001027e0000 CR4: 0000000000750ee0
[   38.425225] PKRU: 55555554
[   38.425229] Call Trace:
[   38.425235]  <TASK>
[   38.425240]  ? assert_port_valid+0x60/0x80 [i915]
[   38.425841]  ? __warn+0x81/0x130
[   38.425857]  ? assert_port_valid+0x60/0x80 [i915]
[   38.426383]  ? report_bug+0x182/0x1b0
[   38.426400]  ? handle_bug+0x49/0xa0
[   38.426410]  ? exc_invalid_op+0x17/0x80
[   38.426419]  ? asm_exc_invalid_op+0x1a/0x20
[   38.426432]  ? assert_port_valid+0x60/0x80 [i915]
[   38.426950]  ? __pfx_intel_ddi_init+0x10/0x10 [i915]
[   38.427492]  intel_ddi_init+0x67/0x1010 [i915]
[   38.428008]  ? __pfx_intel_ddi_init+0x10/0x10 [i915]
[   38.428537]  intel_bios_for_each_encoder+0x35/0x60 [i915]
[   38.429160]  intel_setup_outputs+0x380/0x8c0 [i915]
[   38.429743]  intel_display_driver_probe_nogem+0x164/0x220 [i915]
[   38.430288]  i915_driver_probe+0x6e3/0xb80 [i915]
[   38.430745]  local_pci_probe+0x42/0xa0
[   38.430756]  pci_device_probe+0xc1/0x220
[   38.430764]  ? sysfs_do_create_link_sd+0x6e/0xf0
[   38.430779]  really_probe+0x1a9/0x3f0
[   38.430791]  ? __pfx___driver_attach+0x10/0x10
[   38.430800]  __driver_probe_device+0x78/0x170
[   38.430810]  driver_probe_device+0x1f/0xa0
[   38.430819]  __driver_attach+0xea/0x1e0
[   38.430829]  bus_for_each_dev+0x89/0xe0
[   38.430837]  bus_add_driver+0x121/0x220
[   38.430846]  driver_register+0x5d/0x120
[   38.430857]  i915_init+0x65/0x1f0 [i915]
[   38.431300]  ? __pfx_i915_init+0x10/0x10 [i915]
[   38.431756]  do_one_initcall+0x5a/0x340
[   38.431771]  do_init_module+0x60/0x250
[   38.431781]  __do_sys_init_module+0x18f/0x1c0
[   38.431792]  do_syscall_64+0x5d/0x90
[   38.431805]  entry_SYSCALL_64_after_hwframe+0x6e/0xd8
[   38.431815] RIP: 0033:0x7fd694c07698
[   38.431824] Code: 48 83 ec 08 89 d2 b8 45 01 00 00 0f 05 48 89 c7 e8 03 e9 ff ff 48 83 c4 08 c3 e9 2d 94 01 00 48 83 ec 08 b8 af 00 00 00 0f 05 <48> 89 c7 e8 e6 e8 ff ff 48 83 c4 08 c3 48 83 ec 08 89 f6 b8 b0 00
[   38.431829] RSP: 002b:00007ffccdd62090 EFLAGS: 00000206 ORIG_RAX: 00000000000000af
[   38.431838] RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007fd694c07698
[   38.431843] RDX: 00007fd694a2fbc0 RSI: 0000000000851537 RDI: 00007fd690b87280
[   38.431848] RBP: 00007fd694b37e90 R08: 00000000d0241811 R09: 0000000000008000
[   38.431852] R10: 0000000000001349 R11: 0000000000000206 R12: 0000000000060000
[   38.431857] R13: 00007fd694a2fbc0 R14: 00007fd694a2fba0 R15: 000000000000001a
[   38.431864]  </TASK>
[   38.431867] ---[ end trace 0000000000000000 ]---
[   38.458023] i915 0000:02:00.0: [drm] GT0: GuC firmware i915/tgl_guc_70.bin version 70.13.1
[   38.458038] i915 0000:02:00.0: [drm] GT0: HuC firmware i915/tgl_huc.bin version 7.9.3
[   38.463517] i915 0000:02:00.0: [drm] GT0: HuC: authenticated for all workloads
[   38.464910] i915 0000:02:00.0: [drm] GT0: GUC: submission enabled
[   38.464914] i915 0000:02:00.0: [drm] GT0: GUC: SLPC enabled
[   38.465300] i915 0000:02:00.0: [drm] GT0: GUC: RC enabled
[   38.468068] [drm] Initialized i915 1.6.0 20201103 for 0000:02:00.0 on minor 1
[   38.472013] i915 0000:02:00.0: [drm] Cannot find any crtc or sizes
[   38.478504] i915 0000:02:00.0: [drm] Cannot find any crtc or sizes
[   38.574369] virtio_gpu virtio0: virtio: device uses modern interface but does not have VIRTIO_F_VERSION_1
[   38.574384] virtio_gpu: probe of virtio0 failed with error -22

mrjamonduro · Feb 13, 2024

kilonde said:
Also no luck for me with 5.15.102-1-pve kernel with J5005, as suggested earlier in the thread, the older one worked.

Download the old kernel:

Code:

apt install pve-kernel 5.11.22-7-pve

test by using the old kernel on next boot only

Code:

proxmox-boot-tool kernel pin 5.11.22-7-pve --next-boot

it worked for me so the below command pins it

Code:

proxmox-boot-tool kernel pin 5.11.22-7-pve

Thanks, that will do for now. Wating for the fix

mrjamonduro · May 15, 2024

Has anyone tested if it works with the latest version of proxmox?

farfarfromhome · Jun 2, 2024

Maybe not working on proxmox 8.2.2. I am trying for the first time to get GPU passthru on Dell Optiplex 7080 to no avail. I am using ubuntocinnamon-23.10-desktop-amd64 VM.
I followed:
https://3os.org/infrastructure/prox...irtual-machine-igpu-passthrough-configuration

I am a relative novice, so maybe another issue!

GPU is:
lspci -nnv | grep VGA
00:02.0 VGA compatible controller [0300]: Intel Corporation CometLake-S GT2 [UHD Graphics 630] [8086:9bc5] (rev 05) (prog-if 00 [VGA controller])

dmesg -w gives the following:
[ 0.979604] DMAR: No ATSR found
[ 0.979606] DMAR: No SATC found
[ 0.979609] DMAR: IOMMU feature fl1gp_support inconsistent
[ 0.979613] DMAR: IOMMU feature pgsel_inv inconsistent
[ 0.979616] DMAR: IOMMU feature nwfs inconsistent
[ 0.979619] DMAR: IOMMU feature pasid inconsistent
[ 0.979622] DMAR: IOMMU feature eafs inconsistent
[ 0.979624] DMAR: IOMMU feature prs inconsistent
[ 0.979626] DMAR: IOMMU feature nest inconsistent
[ 0.979629] DMAR: IOMMU feature mts inconsistent
[ 0.979631] DMAR: IOMMU feature sc_support inconsistent
[ 0.979634] DMAR: IOMMU feature dev_iotlb_support inconsistent
[ 0.979637] DMAR: dmar0: Using Queued invalidation
[ 0.979646] DMAR: dmar1: Using Queued invalidation

and the last message an invalid ROM header.
[35720.509611] vfio-pci 0000:00:02.0: Invalid PCI ROM header signature: expecting 0xaa55, got 0xffff

Can anyone point me in the right direction to solve?

farfarfromhome · Jun 3, 2024

I had some success! I noticed my Dell Optiplex 7080 BIOS was quite old v1.1.5, so updated to v1.25.0. Now I have the GPU and USB (for keyboard and mouse) pass thru working however still some strangeness in the logs. The initial boot of proxmox still shows the IOMMU feature inconsistent messages and three DRHD: handling fault status reg 3 messages :

[ 0.033808] ACPI: DMAR 0x0000000077FC1000 0000C8 (v01 INTEL EDK2 00000002 01000013)
[ 0.033951] ACPI: Reserving DMAR table memory at [mem 0x77fc1000-0x77fc10c7]
[ 0.458955] DMAR: Host address width 39
[ 0.458959] DMAR: DRHD base: 0x000000fed90000 flags: 0x0
[ 0.458988] DMAR: dmar0: reg_base_addr fed90000 ver 1:0 cap 1c0000c40660462 ecap 19e2ff0505e
[ 0.458997] DMAR: DRHD base: 0x000000fed91000 flags: 0x1
[ 0.459009] DMAR: dmar1: reg_base_addr fed91000 ver 1:0 cap d2008c40660462 ecap f050da
[ 0.459016] DMAR: RMRR base: 0x000000785e8000 end: 0x00000078831fff
[ 0.459025] DMAR: RMRR base: 0x0000007c000000 end: 0x0000007e7fffff
[ 0.459030] DMAR: RMRR base: 0x00000077edb000 end: 0x00000077f5afff
[ 0.459036] DMAR-IR: IOAPIC id 2 under DRHD base 0xfed91000 IOMMU 1
[ 0.459042] DMAR-IR: HPET id 0 under DRHD base 0xfed91000
[ 0.459046] DMAR-IR: Queued invalidation will be enabled to support x2apic and Intr-remapping.
[ 0.462847] DMAR-IR: Enabled IRQ remapping in x2apic mode
[ 1.173737] DMAR: No ATSR found
[ 1.173740] DMAR: No SATC found
[ 1.173743] DMAR: IOMMU feature fl1gp_support inconsistent
[ 1.173747] DMAR: IOMMU feature pgsel_inv inconsistent
[ 1.173751] DMAR: IOMMU feature nwfs inconsistent
[ 1.173753] DMAR: IOMMU feature pasid inconsistent
[ 1.173756] DMAR: IOMMU feature eafs inconsistent
[ 1.173758] DMAR: IOMMU feature prs inconsistent
[ 1.173761] DMAR: IOMMU feature nest inconsistent
[ 1.173763] DMAR: IOMMU feature mts inconsistent
[ 1.173765] DMAR: IOMMU feature sc_support inconsistent
[ 1.173768] DMAR: IOMMU feature dev_iotlb_support inconsistent
[ 1.173771] DMAR: dmar0: Using Queued invalidation
[ 1.173780] DMAR: dmar1: Using Queued invalidation
[ 1.179128] DMAR: Intel(R) Virtualization Technology for Directed I/O
[ 26.424045] DMAR: DRHD: handling fault status reg 3
[ 26.424048] DMAR: [DMA Read NO_PASID] Request device [00:02.0] fault addr 0xffebe000 [fault reason 0x06] PTE Read access is not set
[ 26.424562] DMAR: DRHD: handling fault status reg 3
[ 26.424565] DMAR: [DMA Read NO_PASID] Request device [00:02.0] fault addr 0xffed5000 [fault reason 0x06] PTE Read access is not set
[ 26.440716] DMAR: DRHD: handling fault status reg 3
[ 26.440719] DMAR: [DMA Read NO_PASID] Request device [00:02.0] fault addr 0xffebe000 [fault reason 0x06] PTE Read access is not set
[ 26.441233] DMAR: DRHD: handling fault status reg 3

if I then enable usb passthru for keyboard and mouse and then boot proxmox, I additionally get the following fault messages continuously:
Jun 02 19:26:12 DellProxMox kernel: DMAR: DRHD: handling fault status reg 3
Jun 02 19:26:12 DellProxMox kernel: DMAR: [DMA Read NO_PASID] Request device [00:02.0] fault addr 0x1f9147000 [fault reason 0x06] PTE Read access is not set
Jun 02 19:26:12 DellProxMox kernel: DMAR: DRHD: handling fault status reg 3
Jun 02 19:26:12 DellProxMox kernel: DMAR: [DMA Read NO_PASID] Request device [00:02.0] fault addr 0x1f9147000 [fault reason 0x06] PTE Read access is not set
Jun 02 19:26:12 DellProxMox kernel: DMAR: DRHD: handling fault status reg 3
Jun 02 19:26:12 DellProxMox kernel: DMAR: [DMA Read NO_PASID] Request device [00:02.0] fault addr 0x1f9147000 [fault reason 0x06] PTE Read access is not set
Jun 02 19:26:12 DellProxMox kernel: DMAR: DRHD: handling fault status reg 3
Jun 02 19:26:17 DellProxMox kernel: dmar_fault: 893 callbacks suppressed

However, if I stop and then restart the VM, the continuous messages do not occur suggesting there is a timing error on intial proxmox and VM boot up.

Any feedback would be welcome to eliminate the fault messages.

Blake43 · Jun 17, 2024

farfarfromhome said:
I had some success! I noticed my Dell Optiplex 7080 BIOS was quite old v1.1.5, so updated to v1.25.0. Now I have the GPU and USB (for keyboard and mouse) pass thru working however still some strangeness in the logs. The initial boot of proxmox still shows the IOMMU feature inconsistent messages and three DRHD: handling fault status reg 3 messages :

[ 0.033808] ACPI: DMAR 0x0000000077FC1000 0000C8 (v01 INTEL EDK2 00000002 01000013)
[ 0.033951] ACPI: Reserving DMAR table memory at [mem 0x77fc1000-0x77fc10c7]
[ 0.458955] DMAR: Host address width 39
[ 0.458959] DMAR: DRHD base: 0x000000fed90000 flags: 0x0
[ 0.458988] DMAR: dmar0: reg_base_addr fed90000 ver 1:0 cap 1c0000c40660462 ecap 19e2ff0505e
[ 0.458997] DMAR: DRHD base: 0x000000fed91000 flags: 0x1
[ 0.459009] DMAR: dmar1: reg_base_addr fed91000 ver 1:0 cap d2008c40660462 ecap f050da
[ 0.459016] DMAR: RMRR base: 0x000000785e8000 end: 0x00000078831fff
[ 0.459025] DMAR: RMRR base: 0x0000007c000000 end: 0x0000007e7fffff
[ 0.459030] DMAR: RMRR base: 0x00000077edb000 end: 0x00000077f5afff
[ 0.459036] DMAR-IR: IOAPIC id 2 under DRHD base 0xfed91000 IOMMU 1
[ 0.459042] DMAR-IR: HPET id 0 under DRHD base 0xfed91000
[ 0.459046] DMAR-IR: Queued invalidation will be enabled to support x2apic and Intr-remapping.
[ 0.462847] DMAR-IR: Enabled IRQ remapping in x2apic mode
[ 1.173737] DMAR: No ATSR found
[ 1.173740] DMAR: No SATC found
[ 1.173743] DMAR: IOMMU feature fl1gp_support inconsistent
[ 1.173747] DMAR: IOMMU feature pgsel_inv inconsistent
[ 1.173751] DMAR: IOMMU feature nwfs inconsistent
[ 1.173753] DMAR: IOMMU feature pasid inconsistent
[ 1.173756] DMAR: IOMMU feature eafs inconsistent
[ 1.173758] DMAR: IOMMU feature prs inconsistent
[ 1.173761] DMAR: IOMMU feature nest inconsistent
[ 1.173763] DMAR: IOMMU feature mts inconsistent
[ 1.173765] DMAR: IOMMU feature sc_support inconsistent
[ 1.173768] DMAR: IOMMU feature dev_iotlb_support inconsistent
[ 1.173771] DMAR: dmar0: Using Queued invalidation
[ 1.173780] DMAR: dmar1: Using Queued invalidation
[ 1.179128] DMAR: Intel(R) Virtualization Technology for Directed I/O
[ 26.424045] DMAR: DRHD: handling fault status reg 3
[ 26.424048] DMAR: [DMA Read NO_PASID] Request device [00:02.0] fault addr 0xffebe000 [fault reason 0x06] PTE Read access is not set
[ 26.424562] DMAR: DRHD: handling fault status reg 3
[ 26.424565] DMAR: [DMA Read NO_PASID] Request device [00:02.0] fault addr 0xffed5000 [fault reason 0x06] PTE Read access is not set
[ 26.440716] DMAR: DRHD: handling fault status reg 3
[ 26.440719] DMAR: [DMA Read NO_PASID] Request device [00:02.0] fault addr 0xffebe000 [fault reason 0x06] PTE Read access is not set
[ 26.441233] DMAR: DRHD: handling fault status reg 3

if I then enable usb passthru for keyboard and mouse and then boot proxmox, I additionally get the following fault messages continuously:
Jun 02 19:26:12 DellProxMox kernel: DMAR: DRHD: handling fault status reg 3
Jun 02 19:26:12 DellProxMox kernel: DMAR: [DMA Read NO_PASID] Request device [00:02.0] fault addr 0x1f9147000 [fault reason 0x06] PTE Read access is not set
Jun 02 19:26:12 DellProxMox kernel: DMAR: DRHD: handling fault status reg 3
Jun 02 19:26:12 DellProxMox kernel: DMAR: [DMA Read NO_PASID] Request device [00:02.0] fault addr 0x1f9147000 [fault reason 0x06] PTE Read access is not set
Jun 02 19:26:12 DellProxMox kernel: DMAR: DRHD: handling fault status reg 3
Jun 02 19:26:12 DellProxMox kernel: DMAR: [DMA Read NO_PASID] Request device [00:02.0] fault addr 0x1f9147000 [fault reason 0x06] PTE Read access is not set
Jun 02 19:26:12 DellProxMox kernel: DMAR: DRHD: handling fault status reg 3
Jun 02 19:26:17 DellProxMox kernel: dmar_fault: 893 callbacks suppressed

However, if I stop and then restart the VM, the continuous messages do not occur suggesting there is a timing error on intial proxmox and VM boot up.

Any feedback would be welcome to eliminate the fault messages.

i too am getting similar output on prox8.2. has anyone actually found a fix yet? i updated Bios on my asrock x99 board with an i7-6800k and all the virtual stuff is checked off but i keep getting the IOMMU support "inconsistent" error. i can raw map a device to a vm but i cannot use the mapped devices option.

oko · Aug 22, 2024

same problem.
"DMAR: IOMMU enabled" is there, iGPU in separate group and present in drop-down list of hardware. Assigned to VM. But no output to monitor. HW: HP EliteDesk 800 G2. CPU Intel i5-6500, iGPU: HD Graphics 530. In a VM (Win10) the GPU is displayed, I've set latest drivers, everything smooth and no errors. Windows recognizes two displays: one for VNC (works well) and the second is iGPU. Just no signal to monitor.
Proxmox v.8.2.4, kernel 6.8.12-1-pve

Code:

# pvesh get /nodes/proxmox/hardware/pci --pci-class-blacklist ""
┌──────────┬────────┬──────────────┬────────────┬────────┬──────────────────────────────────────────────────────────────────────────────┬──────┬
│ class    │ device │ id           │ iommugroup │ vendor │ device_name                                                                  │ mdev │
╞══════════╪════════╪══════════════╪════════════╪════════╪══════════════════════════════════════════════════════════════════════════════╪══════╪
│ 0x010601 │ 0xa102 │ 0000:00:17.0 │          4 │ 0x8086 │ Q170/Q150/B150/H170/H110/Z170/CM236 Chipset SATA Controller [AHCI Mode]      │      │
├──────────┼────────┼──────────────┼────────────┼────────┼──────────────────────────────────────────────────────────────────────────────┼──────┼
│ 0x020000 │ 0x15b7 │ 0000:00:1f.6 │          6 │ 0x8086 │ Ethernet Connection (2) I219-LM                                              │      │
├──────────┼────────┼──────────────┼────────────┼────────┼──────────────────────────────────────────────────────────────────────────────┼──────┼
│ 0x030000 │ 0x1912 │ 0000:00:02.0 │          0 │ 0x8086 │ HD Graphics 530                                                              │      │
├──────────┼────────┼──────────────┼────────────┼────────┼──────────────────────────────────────────────────────────────────────────────┼──────┼
│ 0x040300 │ 0xa170 │ 0000:00:1f.3 │          5 │ 0x8086 │ 100 Series/C230 Series Chipset Family HD Audio Controller                    │      │
├──────────┼────────┼──────────────┼────────────┼────────┼──────────────────────────────────────────────────────────────────────────────┼──────┼
│ 0x058000 │ 0xa121 │ 0000:00:1f.2 │          5 │ 0x8086 │ 100 Series/C230 Series Chipset Family Power Management Controller            │      │
├──────────┼────────┼──────────────┼────────────┼────────┼──────────────────────────────────────────────────────────────────────────────┼──────┼
│ 0x060000 │ 0x191f │ 0000:00:00.0 │          1 │ 0x8086 │ Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Host Bridge/DRAM Registers │      │
├──────────┼────────┼──────────────┼────────────┼────────┼──────────────────────────────────────────────────────────────────────────────┼──────┼
│ 0x060100 │ 0xa146 │ 0000:00:1f.0 │          5 │ 0x8086 │ Q170 Chipset LPC/eSPI Controller                                             │      │
├──────────┼────────┼──────────────┼────────────┼────────┼──────────────────────────────────────────────────────────────────────────────┼──────┼
│ 0x070002 │ 0xa13d │ 0000:00:16.3 │          3 │ 0x8086 │ 100 Series/C230 Series Chipset Family KT Redirection                         │      │
├──────────┼────────┼──────────────┼────────────┼────────┼──────────────────────────────────────────────────────────────────────────────┼──────┼
│ 0x078000 │ 0xa13a │ 0000:00:16.0 │          3 │ 0x8086 │ 100 Series/C230 Series Chipset Family MEI Controller #1                      │      │
├──────────┼────────┼──────────────┼────────────┼────────┼──────────────────────────────────────────────────────────────────────────────┼──────┼
│ 0x0c0330 │ 0xa12f │ 0000:00:14.0 │          2 │ 0x8086 │ 100 Series/C230 Series Chipset Family USB 3.0 xHCI Controller                │      │
├──────────┼────────┼──────────────┼────────────┼────────┼──────────────────────────────────────────────────────────────────────────────┼──────┼
│ 0x0c0500 │ 0xa123 │ 0000:00:1f.4 │          5 │ 0x8086 │ 100 Series/C230 Series Chipset Family SMBus                                  │      │
├──────────┼────────┼──────────────┼────────────┼────────┼──────────────────────────────────────────────────────────────────────────────┼──────┼
│ 0x118000 │ 0xa131 │ 0000:00:14.2 │          2 │ 0x8086 │ 100 Series/C230 Series Chipset Family Thermal Subsystem                      │      │
└──────────┴────────┴──────────────┴────────────┴────────┴──────────────────────────────────────────────────────────────────────────────┴──────┴
root@proxmox:~# dmesg | grep -e DMAR -e IOMMU -e AMD-Vi
[    0.000000] Warning: PCIe ACS overrides enabled; This may allow non-IOMMU protected peer-to-peer DMA
[    0.008694] ACPI: DMAR 0x00000000C9ECC000 0000A8 (v01 INTEL  SKL      00000001 INTL 00000001)
[    0.008719] ACPI: Reserving DMAR table memory at [mem 0xc9ecc000-0xc9ecc0a7]
[    0.030621] DMAR: IOMMU enabled
[    0.088061] DMAR: Host address width 39
[    0.088062] DMAR: DRHD base: 0x000000fed90000 flags: 0x0
[    0.088071] DMAR: dmar0: reg_base_addr fed90000 ver 1:0 cap 1c0000c40660462 ecap 7e3ff0505e
[    0.088073] DMAR: DRHD base: 0x000000fed91000 flags: 0x1
[    0.088076] DMAR: dmar1: reg_base_addr fed91000 ver 1:0 cap d2008c40660462 ecap f050da
[    0.088078] DMAR: RMRR base: 0x000000c9bd6000 end: 0x000000c9bf5fff
[    0.088079] DMAR: RMRR base: 0x000000cc000000 end: 0x000000ce7fffff
[    0.088081] DMAR-IR: IOAPIC id 2 under DRHD base  0xfed91000 IOMMU 1
[    0.088082] DMAR-IR: HPET id 0 under DRHD base 0xfed91000
[    0.088083] DMAR-IR: Queued invalidation will be enabled to support x2apic and Intr-remapping.
[    0.089672] DMAR-IR: Enabled IRQ remapping in x2apic mode
[    0.269964] DMAR: No ATSR found
[    0.269965] DMAR: No SATC found
[    0.269966] DMAR: IOMMU feature fl1gp_support inconsistent
[    0.269967] DMAR: IOMMU feature pgsel_inv inconsistent
[    0.269969] DMAR: IOMMU feature nwfs inconsistent
[    0.269969] DMAR: IOMMU feature eafs inconsistent
[    0.269970] DMAR: IOMMU feature prs inconsistent
[    0.269971] DMAR: IOMMU feature nest inconsistent
[    0.269972] DMAR: IOMMU feature mts inconsistent
[    0.269973] DMAR: IOMMU feature sc_support inconsistent
[    0.269973] DMAR: IOMMU feature dev_iotlb_support inconsistent
[    0.269974] DMAR: dmar0: Using Queued invalidation
[    0.269977] DMAR: dmar1: Using Queued invalidation
[    0.270339] DMAR: Intel(R) Virtualization Technology for Directed I/O
[   19.914393] DMAR: DRHD: handling fault status reg 2
[   19.914397] DMAR: [DMA Write NO_PASID] Request device [00:02.0] fault addr 0x0 [fault reason 0x02] Present bit in context entry is clear
root@proxmox:~#

Search

Search

PCI passthrough ERROR since Kernel 5.13.19-1 (upgrade from 7.0 to 7.1)

derMischka

Active Member

derMischka

Active Member

bolzerrr

Well-Known Member

kilonde

New Member

elektrinis

New Member

bolzerrr

Well-Known Member

trique

New Member

bolzerrr

Well-Known Member

mrjamonduro

New Member

mrjamonduro

New Member

farfarfromhome

Member

farfarfromhome

Member

Blake43

New Member

oko

New Member