Hello,Hello,
I have been searching for a solution to this issue but haven’t managed to fix it yet.
I am running Proxmox VE with IOMMU enabled and using PCIe passthrough of a network card to a virtual machine where PF_RING is running for network traffic analysis. The kernel boot parameters include:
When PF_RING starts in the VM, I see repeated errors in the host logs:
These errors quickly duplicate, filling dmesg.
Using the PF_RING parameter zero_copy=0 or options pf_ring zero_copy=1 partially removes the errors, but when I try PCI passthrough, the NIC disappears from the VM after unbind, and there is no reliable way for PF_RING to write directly to DMA without triggering these faults.
So far I verified that:
Mainboard : X9DR3-F and latest bios version.
Ethernet card
VM config
I can provide additional information if needed.
I have been searching for a solution to this issue but haven’t managed to fix it yet.
I am running Proxmox VE with IOMMU enabled and using PCIe passthrough of a network card to a virtual machine where PF_RING is running for network traffic analysis. The kernel boot parameters include:
intel_iommu=on iommu=pt vfio_iommu_type1 allow_unsafe_interrupts=1When PF_RING starts in the VM, I see repeated errors in the host logs:
DMAR: DRHD: handling fault status reg XXXDMAR: [DMA Write NO_PASID] Request device [04:00.0] fault addr 0xXXXXXX [fault reason 0x05] PTE Write access is not setThese errors quickly duplicate, filling dmesg.
Using the PF_RING parameter zero_copy=0 or options pf_ring zero_copy=1 partially removes the errors, but when I try PCI passthrough, the NIC disappears from the VM after unbind, and there is no reliable way for PF_RING to write directly to DMA without triggering these faults.
So far I verified that:
- PF_RING runs normally in the VM (showing packets with pfcount)
- The issue is related to PF_RING’s DMA write attempts in the VM context
Mainboard : X9DR3-F and latest bios version.
Bash:
# pveversion -v
proxmox-ve: 8.4.0 (running kernel: 6.11.11-2-pve)
pve-manager: 8.4.14 (running version: 8.4.14/b502d23c55afcba1)
proxmox-kernel-helper: 8.1.4
proxmox-kernel-6.11.11-2-pve-signed: 6.11.11-2
proxmox-kernel-6.11: 6.11.11-2
proxmox-kernel-6.8: 6.8.12-15
proxmox-kernel-6.8.12-15-pve-signed: 6.8.12-15
proxmox-kernel-6.5.13-6-pve-signed: 6.5.13-6
proxmox-kernel-6.5: 6.5.13-6
ceph-fuse: 16.2.15+ds-0+deb12u1
corosync: 3.1.9-pve1
criu: 3.17.1-2+deb12u2
frr-pythontools: 10.2.3-1+pve1
glusterfs-client: 10.5-1
ifupdown2: 3.2.0-1+pmx11
ksm-control-daemon: 1.5-1
libjs-extjs: 7.0.0-5
libknet1: 1.30-pve2
libproxmox-acme-perl: 1.6.0
libproxmox-backup-qemu0: 1.5.2
libproxmox-rs-perl: 0.3.5
libpve-access-control: 8.2.2
libpve-apiclient-perl: 3.3.2
libpve-cluster-api-perl: 8.1.2
libpve-cluster-perl: 8.1.2
libpve-common-perl: 8.3.4
libpve-guest-common-perl: 5.2.2
libpve-http-server-perl: 5.2.2
libpve-network-perl: 0.11.2
libpve-rs-perl: 0.9.4
libpve-storage-perl: 8.3.7
libspice-server1: 0.15.1-1
lvm2: 2.03.16-2
lxc-pve: 6.0.0-1
lxcfs: 6.0.0-pve2
novnc-pve: 1.6.0-2
openvswitch-switch: 3.1.0-2+deb12u1
proxmox-backup-client: 3.4.6-1
proxmox-backup-file-restore: 3.4.6-1
proxmox-backup-restore-image: 0.7.0
proxmox-firewall: 0.7.1
proxmox-kernel-helper: 8.1.4
proxmox-mail-forward: 0.3.3
proxmox-mini-journalreader: 1.5
proxmox-offline-mirror-helper: 0.6.8
proxmox-widget-toolkit: 4.3.13
pve-cluster: 8.1.2
pve-container: 5.3.3
pve-docs: 8.4.1
pve-edk2-firmware: not correctly installed
pve-esxi-import-tools: 0.7.4
pve-firewall: 5.1.2
pve-firmware: 3.16-3
pve-ha-manager: 4.0.7
pve-i18n: 3.4.5
pve-qemu-kvm: 9.2.0-7
pve-xtermjs: 5.5.0-2
qemu-server: 8.4.3
smartmontools: 7.3-pve1
spiceterm: 3.3.1
swtpm: 0.8.0+pve1
vncterm: 1.8.1
zfsutils-linux: 2.2.8-pve1Ethernet card
Bash:
# lspci -s 0000:04:00.0 -v
04:00.0 Ethernet controller: Intel Corporation Ethernet Controller X710 for 10GbE SFP+ (rev 01)
Subsystem: Intel Corporation Ethernet Controller X710 for 10GbE SFP+
Flags: fast devsel, IRQ 28, NUMA node 0, IOMMU group 53
Memory at 380ffe000000 (64-bit, prefetchable) [size=8M]
Memory at 380fff008000 (64-bit, prefetchable) [size=32K]
Expansion ROM at df980000 [disabled] [size=512K]
Capabilities: [40] Power Management version 3
Capabilities: [50] MSI: Enable- Count=1/1 Maskable+ 64bit+
Capabilities: [70] MSI-X: Enable- Count=129 Masked-
Capabilities: [a0] Express Endpoint, MSI 00
Capabilities: [e0] Vital Product Data
Capabilities: [100] Advanced Error Reporting
Capabilities: [140] Device Serial Number 8a-f6-7b-ff-ff-ca-05-68
Capabilities: [150] Alternative Routing-ID Interpretation (ARI)
Capabilities: [160] Single Root I/O Virtualization (SR-IOV)
Capabilities: [1a0] Transaction Processing Hints
Capabilities: [1b0] Access Control Services
Capabilities: [1d0] Secondary PCI Express
Kernel driver in use: vfio-pci
Kernel modules: i40eVM config
Code:
agent: 1
boot: order=sata0;scsi0
cores: 8
cpu: host
hostpci0: 0000:04:00.0,pcie=1
machine: q35
memory: 16384
meta: creation-qemu=9.2.0,ctime=1759433901
net0: virtio=BC:24:11:C3:09:37,bridge=vmbr0,tag=10
numa: 1
ostype: l26
sata0: none,media=cdrom
scsi0: NVMe:1018/vm-1018-disk-0.qcow2,cache=writeback,discard=on,iothread=1,size=1000G,ssd=1
scsihw: virtio-scsi-single
smbios1: uuid=4b39c8ae-6036-46bb-bba8-ce7f2d8895e5
sockets: 2
vmgenid: 4d88985b-53da-44bd-b240-1863722136ff