ESXI 6 and intel i211 nic

patrtech

I believe I tried a factory reset yesterday in one of the iterations of using 2 drives to troubleshoot, but course I can do it again. Here's the lspci output:

[root@localhost:~] lspci
0000:00:00.0 Bridge:
0000:00:02.0 Display controller:
0000:00:03.0 Multimedia controller:
0000:00:14.0 Serial bus controller:
0000:00:16.0 Communication controller:
0000:00:19.0 Network controller: [vmnic0]
0000:00:1b.0 Multimedia controller:
0000:00:1c.0 Bridge: [PCIe RP[0000:00:1c.0]]
0000:00:1c.2 Bridge: [PCIe RP[0000:00:1c.2]]
0000:00:1c.3 Bridge: [PCIe RP[0000:00:1c.3]]
0000:00:1d.0 Serial bus controller:
0000:00:1f.0 Bridge:
0000:00:1f.2 Mass storage controller: [vmhba0]
0000:00:1f.3 Serial bus controller:
0000:02:00.0 Network controller: Intel Corporation I211 Gigabit Network Connection [vmnic1]
0000:03:00.0 Network controller:

gjaltemba

Then in esx.conf
/device/00000:000:25.0/vmkname = "vmnic0"
should be
/device/00000:000:19.0/vmkname = "vmnic0"

I wonder what is at 0000:03:00.0 Network controller:

patrtech

Should i edit esx.conf to /device/00000:000:19.0/vmkname = "vmnic0"?

0000:03:00.0 Network controller <–-----that probably is a wireless nic, which I can't disable in the bios. Maybe I should physicall just remove that?

gjaltemba

Yeah. It is the wifi card. You could try and edit esx.conf but it is not supported.

Personally, I would try re-installing with VT-d off in the bios but it is just a shot in the dark.

patrtech

So I tried again today, formatted the drive, disabled VT-d, disabled nic and exactly the same results as before. I tried editing the esx.conf file from /device/00000:000:25.0/vmkname = "vmnic0" to /device/00000:000:19.0/vmkname = "vmnic0" but after rebooting it went back to what it was before. That second nic just won't show up, I wish they hadn't put two different nics into this unit. I'm going to try installing some igb driver i found igb-5.2.7-1331820-2157967.zip, not sure if this is will do anything but it can't make it worse.

gjaltemba

If I211 nic works in passthru why not use it for the wan port in pfsense? You will still have I218 for a vswitch to assign to pfsense lan port and new VMs.

patrtech

I'm totally new to esxi and pfsense….as trivial as it might sound, are there any downsides to your suggestion? in terms of security, performance etc. Basically I was following this guide https://doc.pfsense.org/index.php/PfSense_2_on_VMware_ESXi_5 and trying to implement it that way. If nothing much is being affected, maybe this is the way to go? I'll have to reformat one last time as the vib driver I just installed didn't make a difference either.

gjaltemba

A passthru nic is bare metal to the pfsense vm and cannot be used as a vnic for other VMs. If you configure the I211 as passthru and assign it to the wan port in pfsense then it can used to provide internet for all the VMs on the lan (vmnic0).

Configure vswitch0 to use vmnic0 and add a VMKernel port group for management and Virtual Machine port group for pfsense lan port and other VMs.

https://doc.pfsense.org/index.php/PfSense_2_on_VMware_ESXi_5

patrtech

I'll give this a shot tomorrow. Thanks for all your help with this issue! It's given me some hope from where I was a couple days back.

washer

patrtech, did you get any further with this?

I just got the same board and believe I'm running into the same exact issue, all three NICs (including the wifi card, I might try to take that out. Don't think it will help but I doubt that would hurt and I don't need/want it now) show up in lspci:

0000:00:19.0 Ethernet controller Network controller: Intel Corporation Ethernet Connection (3) I218-LM [vmnic0]
	 Class 0200: 8086:15a2

0000:02:00.0 Ethernet controller Network controller: Intel Corporation I211 Gigabit Network Connection [vmnic1]
	 Class 0200: 8086:1539

0000:03:00.0 Network controller Network controller:
	 Class 0280: 10ec:8179

But only vmnic0, the I218-LM, is showing up as a Network Adapter. I also see the I211 as an option for pass-through, so I'm going to try and start setting up with that as my WAN port like gjaltemba suggested. It sure would be nice to know why it only shows up for pass-through and not as a valid network adaptor though, assuming it really is supported like we think…

preid

@patrtech:

I'm totally new to esxi and pfsense….as trivial as it might sound, are there any downsides to your suggestion? in terms of security, performance etc. Basically I was following this guide https://doc.pfsense.org/index.php/PfSense_2_on_VMware_ESXi_5 and trying to implement it that way. If nothing much is being affected, maybe this is the way to go? I'll have to reformat one last time as the vib driver I just installed didn't make a difference either.

There is one gotcha with pass-through devices - you will no longer be able to move the VM to another host via vMotion or High Availability - so if you're running a VMWare cluster, those features will not be available for that virtual machine. Aside from that, and the NIC no longer being available for other VMs, it shouldn't give you any issues.

VFrontDe

I investigated this issue and found that the igb driver is refusing to initialize lots of i211 adapters, because their NVM checksums do not match the expected value.
To work around the issue I modified the driver to ignore invalid NVM checksums. The modified driver resolved the issue in at least two cases.

More details are in this blog post:
http://www.v-front.de/2015/08/a-fix-for-intel-i211-and-i350-adapters.html

miloman

@VFrontDe:

To work around the issue I modified the driver to ignore invalid NVM checksums.

you make it sound so easy… also, the stuff on v-front.de is amazing. thank you for all your work.