Blacklisting Driver...Permanently?

Nollimox

Member
Mar 9, 2023
270
21
18
So, had problems enabling IOMMU for two devices that I wanted to passthrough. In an effort to encourage
a solution, I ended up blacklisted the driver name - igb.

Now, whenever I launch the VM, immediately I see on the monitor...even after a clean install of Proxmox...
Sorry had not enable ssh so I could print it exactly.

vmbr1device tap100io entered promiscuous mode, followed by entering blocking state, then entered disable state, then, entered blocking state,
then, entered forwarding state, then link up, then, entered disable state.

Is this permanently etched on bios? The reason is the first NIC was i350xt4, then, I tried an i350xt2 after the clean install...both use the same exact driver...
 
This is a weird issue...clean install of Proxmox and then configured...got IOMMU passed-through...see below:
root@nollipve:~# dmesg | grep -e DMAR -e IOMMU
[ 0.010680] ACPI: DMAR 0x0000000079C217C8 0000C8 (v01 INTEL EDK2 00000002 01000013)
[ 0.010720] ACPI: Reserving DMAR table memory at [mem 0x79c217c8-0x79c2188f]
[ 0.090547] DMAR: IOMMU enabled
[ 0.224973] DMAR: Host address width 39
[ 0.224975] DMAR: DRHD base: 0x000000fed90000 flags: 0x0
[ 0.224982] DMAR: dmar0: reg_base_addr fed90000 ver 1:0 cap 1c0000c40660462 ecap 19e2ff0505e
[ 0.224987] DMAR: DRHD base: 0x000000fed91000 flags: 0x1
[ 0.224991] DMAR: dmar1: reg_base_addr fed91000 ver 1:0 cap d2008c40660462 ecap f050da
[ 0.224995] DMAR: RMRR base: 0x00000079a87000 end: 0x00000079aa6fff
[ 0.224997] DMAR: RMRR base: 0x0000007d000000 end: 0x0000007f7fffff
[ 0.225000] DMAR: RMRR base: 0x00000079b39000 end: 0x00000079bb8fff
[ 0.225003] DMAR-IR: IOAPIC id 2 under DRHD base 0xfed91000 IOMMU 1
[ 0.225006] DMAR-IR: HPET id 0 under DRHD base 0xfed91000
[ 0.225008] DMAR-IR: Queued invalidation will be enabled to support x2apic and Intr-remapping.
[ 0.228173] DMAR-IR: Enabled IRQ remapping in x2apic mode
[ 0.549604] DMAR: No ATSR found
[ 0.549606] DMAR: No SATC found
[ 0.549608] DMAR: IOMMU feature fl1gp_support inconsistent
[ 0.549609] DMAR: IOMMU feature pgsel_inv inconsistent
[ 0.549612] DMAR: IOMMU feature nwfs inconsistent
[ 0.549614] DMAR: IOMMU feature pasid inconsistent
[ 0.549617] DMAR: IOMMU feature eafs inconsistent
[ 0.549619] DMAR: IOMMU feature prs inconsistent
[ 0.549621] DMAR: IOMMU feature nest inconsistent
[ 0.549623] DMAR: IOMMU feature mts inconsistent
[ 0.549626] DMAR: IOMMU feature sc_support inconsistent
[ 0.549628] DMAR: IOMMU feature dev_iotlb_support inconsistent
[ 0.549630] DMAR: dmar0: Using Queued invalidation
[ 0.549636] DMAR: dmar1: Using Queued invalidation
[ 0.550273] DMAR: Intel(R) Virtualization Technology for Directed I/O
root@nollipve:~#

Then, apply a clean Install of pfSense and, as soon as, it reboots and asked for WAN interface, I get:

[58:2511981] - vmbr1device tap100io entered promiscuous mode, followed by entering blocking state, then entered disable state, then, entered blocking state, then, entered forwarding state, then link up, then, entered disable state.

HOW TO FLUSH OR CLEAR, whatever is doing this and where?
 

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!