I have an Intel Ethernet Server Adapter I340-T4 that was recognized in ESXi 4.1 and just recently upgraded to ESXi 5.0.
In the new version of ESXi, the same NICs (it's a quad port card) were not present, so I tried installing the driver update "igb version 3.2.10". Still no dice, the vmnics are not present in the ESXi client or when I do a "esxclient network nic list".
The system does have knowledge of the NICs (82580 below) existence though:
~ # lspci | grep 825
000:000:25.0 Network controller: Intel Corporation 82579LM Gigabit Network Connection
000:001:00.0 Network controller: Intel Corporation 82580 Gigabit Network Connection [vmnic0]
000:001:00.1 Network controller: Intel Corporation 82580 Gigabit Network Connection [vmnic2]
000:001:00.2 Network controller: Intel Corporation 82580 Gigabit Network Connection [vmnic3]
000:001:00.3 Network controller: Intel Corporation 82580 Gigabit Network Connection [vmnic4]
000:004:00.0 Network controller: Intel Corporation 82574L Gigabit Network Connection [vmnic1]
And the vib was installed:
~ # esxcli software vib list
Name Version Vendor Acceptance Level Install Date
-------------------- ---------------------------------- ------ ---------------- ------------
net-igb 3.2.10-1OEM.500.0.0.472560 Intel VMwareCertified 2011-11-04
ata-pata-amd 0.3.10-3vmw.500.0.0.469512 VMware VMwareCertified 2011-10-31
And the module appears to be loaded:
~ # vmkload_mod -l | grep igb
igb 0 136
But for some reason, the igb driver is not claiming any devices:
/var/log # less vmkernel.log | grep igb
2011-11-04T22:29:17.517Z cpu0:2048)VisorFSTar: 2405: net-igb.v00 for 0x3ec08 bytes
2011-11-04T22:29:26.564Z cpu2:2626)Loading module igb ...
2011-11-04T22:29:26.567Z cpu2:2626)Elf: 1862: module igb has license GPL
2011-11-04T22:29:26.568Z cpu2:2626)skb_mem_info mempool for module igb created - max size 23068672
2011-11-04T22:29:26.568Z cpu2:2626)module heap vmklnx_igb: creation succeeded. id = 0x41000b600000
2011-11-04T22:29:26.568Z cpu2:2626)PCI: driver igb is looking for devices
2011-11-04T22:29:26.568Z cpu2:2626)PCI: driver igb claimed 0 device
2011-11-04T22:29:26.568Z cpu2:2626)Mod: 4015: Initialization of igb succeeded with module ID 26.
2011-11-04T22:29:26.568Z cpu2:2626)igb loaded successfully.
2011-11-05T00:18:14.517Z cpu0:2048)VisorFSTar: 2405: net-igb.v00 for 0x3ec08 bytes
2011-11-05T00:18:23.614Z cpu1:2626)Loading module igb ...
2011-11-05T00:18:23.617Z cpu1:2626)Elf: 1862: module igb has license GPL
2011-11-05T00:18:23.618Z cpu1:2626)skb_mem_info mempool for module igb created - max size 23068672
2011-11-05T00:18:23.618Z cpu1:2626)module heap vmklnx_igb: creation succeeded. id = 0x410015620000
2011-11-05T00:18:23.618Z cpu1:2626)PCI: driver igb is looking for devices
2011-11-05T00:18:23.618Z cpu1:2626)PCI: driver igb claimed 0 device
2011-11-05T00:18:23.618Z cpu1:2626)Mod: 4015: Initialization of igb succeeded with module ID 26.
2011-11-05T00:18:23.618Z cpu1:2626)igb loaded successfully.
Is there something I missed?
Thanks,
Antonio
Yes from the log, it says that the driver is not detecting the hardware.
Did you try version igb version 3.1.17, if not try and let see if there is a luck,
Here's what I've tried so far:
I noticed that when the driver isn't installed (say after I removed the vib), the lspci output does change a bit:
/var/log # lspci -v | grep 000:001:00 000:001:00.0 Ethernet controller Network controller: Intel Corporation Ethernet Server Adapter I340-T4 000:001:00.1 Ethernet controller Network controller: Intel Corporation Ethernet Server Adapter I340-T4 000:001:00.2 Ethernet controller Network controller: Intel Corporation Ethernet Server Adapter I340-T4 000:001:00.3 Ethernet controller Network controller: Intel Corporation Ethernet Server Adapter I340-T4
Aside from the device name being different (no longer contains string "82580"), the string "[vmnicX]" is no longer appended to the end of the line. What gives? When I had the VIB installed, the new Intel module was loaded but the NICs weren't being recognized by the driver.
I will also note that I found these warnings for my missing NICs:
/etc/vmware # less /var/log/vmkwarning.log | grep 000:000:01 ING: PCI: 2567: No mem resources: Mem (0xff88c000 - 0xff88ffff) out of range on parent: 000:000:01.0 for device: 000:001:00.0 0:00:00:03.462 cpu0:2048)WARNING: PCI: 2633: No resources for device: 000:001:00.0, BAR[3]: 0xff88c000, size: 16384, type: 0x2, flags: 0x0 0:00:00:03.462 cpu0:2048)WARNING: PCI: 2567: No mem resources: Mem (0xff888000 - 0xff88bfff) out of range on parent: 000:000:01.0 for device: 000:001:00.1 0:00:00:03.462 cpu0:2048)WARNING: PCI: 2633: No resources for device: 000:001:00.1, BAR[3]: 0xff888000, size: 16384, type: 0x2, flags: 0x0 0:00:00:03.462 cpu0:2048)WARNING: PCI: 2567: No mem resources: Mem (0xff884000 - 0xff887fff) out of range on parent: 000:000:01.0 for device: 000:001:00.2 0:00:00:03.462 cpu0:2048)WARNING: PCI: 2633: No resources for device: 000:001:00.2, BAR[3]: 0xff884000, size: 16384, type: 0x2, flags: 0x0 0:00:00:03.462 cpu0:2048)WARNING: PCI: 2567: No mem resources: Mem (0xff880000 - 0xff883fff) out of range on parent: 000:000:01.0 for device: 000:001:00.3 0:00:00:03.462 cpu0:2048)WARNING: PCI: 2633: No resources for device: 000:001:00.3, BAR[3]: 0xff880000, size: 16384, type: 0x2, flags: 0x0 0:00:00:03.462 cpu0:2048)WARNING: PCI: 2567: No mem resources: Mem (0xff400000 - 0xff40ffff) out of range on parent: 000:000:06.0 for device: 000:002:00.0 0:00:00:03.462 cpu0:2048)WARNING: PCI: 2633: No resources for device: 000:002:00.0, BAR[3]: 0xff400000, size: 65536, type: 0x3, flags: 0x4
After re-installing the drivers again, I did see my device listed in "/etc/vmware/pci.ids":
150e 82580 Gigabit Network Connection103c 1780 NC365T 4-port Ethernet Server Adapter8086 12a1 Ethernet Server Adapter I340-T48086 12a2 Ethernet Server Adapter I340-T4
Which is nice, but it'd be better if the driver associated itself with the actual devices.
Here's the output of "lscpi -p" which again shows the igb module not claiming the four NICs:
Seg:Bus:Sl.F Vend:Dvid Subv:Subd ISA/irq/Vec P M Module Name Spawned bus 000:000:31.3 8086:1c22 15d9:0624 11/ / C V 000:001:00.0 8086:150e 8086:12a1 11/ / A V vmnic0 000:001:00.1 8086:150e 8086:12a1 5/ / B V vmnic1 000:001:00.2 8086:150e 8086:12a1 11/ / C V vmnic2 000:001:00.3 8086:150e 8086:12a1 5/ / D V vmnic3 000:002:00.0 1000:0058 1000:3140 5/ / A V vmhba1 000:004:00.0 8086:10d3 15d9:10d3 11/ 11/0x98 A V e1000e vmnic4
Any help would be appreciated.
Alright, I'm pretty sure the problem is related to ESXi 5.0. I just reinstalled ESXi 4.1, installed the drivers for my Intel 82580 based quad port NIC, and the vmnics came right back up.
Installed ESXi 5.0 and all four of the vmnics have vanished. ![]()
My system specs:
I'd like to stay with ESXi 5.0 since you can run nested hypervisors with this version.
Bumping this in case anyone has ideas.
Was wondering if you made any progress with this? I am having the same issue with an Intel I350T2 netcard on a supermicro X9SCM board. I have installed the driver but the netcard does not show up in the VI Client.
Currently running ESXi 5 build 469512. I am going to upgrade to the latest version of ESXi5 to see if that helps but it definetely looks like some kind of Vmware bug.
Any ideas would be appreciated.
I was eventually able to get this working by moving the card to the very last slot (furthest from the CPU) on my x9scm motherboard.
This is probably related to slot 4 being the only physical slot connected to the Cougar Point PCH (see Supermicro's documentation<http://www.supermicro.com/manuals/motherboard/C202_C204/MNL-1270.pdf>). I'm not sure why exactly this is the case, but perhaps this will be solved in a future bios firmware update. I sure hope so because I intended to use more than one quad port NIC with this motherboard.
Hope this helps!
The 350 card requires a driver download. You can push it out with Update Manager if managed by vcenter, otherwise you'll have to use the new esxcli to upload and install the 350's VIB driver.
