Another mystery - Intel i350 quad NIC driver igb failed with error -16

[mike the newb]

I'm literally on...probably, my 35th install/reinstall of Proxmox. No problem really, because I'm just learning, but frustrating, nonetheless.

This card was picked up on each installation, up to this last one, where I was trying to complete the install with UEFI and a ZFS root pool.
Now it doesn't show, and

dmesg | egrep -i --color 'igb'

shows the following:

root@PVE:/# dmesg | egrep -i --color 'igb'
[    2.068624] igb: Intel(R) Gigabit Ethernet Network Driver
[    2.068899] igb: Copyright (c) 2007-2014 Intel Corporation.
[    2.144732] igb 0000:04:00.0: DCA enabled
[    2.149795] igb 0000:04:00.0: added PHC on eth0
[    2.150062] igb 0000:04:00.0: Intel(R) Gigabit Ethernet Network Connection
[    2.150542] igb 0000:04:00.0: eth0: (PCIe:5.0Gb/s:Width x4) 00:25:90:7c:2e:ea
[    2.150861] igb 0000:04:00.0: eth0: PBA No: 104900-000
[    2.151103] igb 0000:04:00.0: Using MSI-X interrupts. 4 rx queue(s), 4 tx queue(s)
[    2.205202] igb 0000:04:00.1: DCA enabled
[    2.207140] igb 0000:04:00.1: added PHC on eth1
[    2.207405] igb 0000:04:00.1: Intel(R) Gigabit Ethernet Network Connection
[    2.207648] igb 0000:04:00.1: eth1: (PCIe:5.0Gb/s:Width x4) 00:25:90:7c:2e:eb
[    2.207963] igb 0000:04:00.1: eth1: PBA No: 104900-000
[    2.208200] igb 0000:04:00.1: Using MSI-X interrupts. 4 rx queue(s), 4 tx queue(s)
[    2.209226] igb 0000:07:00.0: BAR 0: can't reserve [mem 0x80000000-0x800fffff]
[    2.209555] igb 0000:07:00.0: probe with driver igb failed with error -16
[    2.209868] igb 0000:07:00.1: BAR 0: can't reserve [mem 0x80100000-0x801fffff]
[    2.210162] igb 0000:07:00.1: probe with driver igb failed with error -16
[    2.210479] igb 0000:07:00.2: BAR 0: can't reserve [mem 0x80200000-0x802fffff]
[    2.210778] igb 0000:07:00.2: probe with driver igb failed with error -16
[    2.211096] igb 0000:07:00.3: BAR 0: can't reserve [mem 0x80300000-0x803fffff]
[    2.211415] igb 0000:07:00.3: probe with driver igb failed with error -16
[    4.389442] igb 0000:04:00.1 eno2: renamed from eth1
[    4.393593] igb 0000:04:00.0 eno1: renamed from eth0
[    9.378341] igb 0000:04:00.0 eno1: entered allmulticast mode
[    9.378767] igb 0000:04:00.0 eno1: entered promiscuous mode
[   13.311780] igb 0000:04:00.0 eno1: igb: eno1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX

Any thoughts/ideas?

 

[mike the newb]

As an addendum, I am not trying to pass through. I haven't even learned about that yet.

 

[mike the newb]

After some additional work on this issue I found that if I set the base allocation address, the failures follow.
For instance, when I started out, the base address in BIOS was 0x80000000, and you see the failure to reserve 0x80000000-0x800fffff above.

I changed the base address to 0x50000000, 0x40000000, and 0x30000000, and got "BAR 0: can't reserve [mem 0x50000000-0x500fffff], BAR 0: can't reserve [mem 0x40000000-0x400fffff], and BAR 0: can't reserve [mem 0x30000000-0x300fffff]" respectively.

Whatever is trying to make these reservations seems to be the problem, and it's looking more and more like it is the kernel.