VMware Cloud Community
anonim1
Contributor
Contributor
Jump to solution

New NIC not visible: "disabled due to insufficient resources"

I have an ESXi 5 setup with a SUPERMICRO MBD-X9SCM-F-O board. The board has two onboard NICs, an Intel 82574L and an 82574LM. The 82574L was automatically detected during the install and is working fine. The 82574LM is not officially supported, so I haven't messed with it. I recently had a requirement for a second functional NIC, so I purchased the Intel EXPI9301CTBLK PCI Express card and put it in the first PCI Express slot.

After the system boots, I cannot see the new NIC. The NIC is plugged in to my internal switch and is showing activity. I followed the guide at http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=103478... to diagnose the issue. I can see all three NICs by quering "lspci". The new NIC is identified as another 82574L, with a Vendor ID of 8086 and Device ID of 10D3. I've verified the "1000e" driver is pre-installed using "vmkload_mod".

The article advises to check the /var/log/messages and /var/log/vmware/hostd-0.log files for instances of "/vmnic" or "/<drivername>"; however, neither of these log files exist on my ESXi 5 installation. The article does not claim to be applicable for version 5, and I could not find another article specifically for version 5.

After digging through the vmkernel.log file, I found the following tidbit:

0:00:00:03.475 cpu0:2048)PCI: 990: scanning pci bridge 0x410015051860 @ s=0 b=1
0:00:00:03.475 cpu0:2048)PCI: 6043: 001:00.0: PCIe v1 PCI Express Endpoint
0:00:00:03.475 cpu0:2048)PCI: 4942: 000:001:00.0: Found Advanced Error Reporting support
0:00:00:03.475 cpu0:2048)PCI: 4942: 000:001:00.0: Found Device Serial Number support
0:00:00:03.476 cpu0:2048)WARNING: PCI: 2567: No mem resources: Mem (0xffae0000 - 0xffae3fff) out of range on parent: 000:000:01.0 for device: 000:001:00.0
0:00:00:03.476 cpu0:2048)WARNING: PCI: 2633: No resources for device: 000:001:00.0, BAR[3]: 0xffae0000, size: 16384, type: 0x2, flags: 0x0
0:00:00:03.476 cpu0:2048)PCI: 3194: 000:001:00.0 8086:10d3 8086:a01f disabled due to insufficient resources.
0:00:00:03.476 cpu0:2048)PCI: 3202: 000:001:00.0 8086:10d3 8086:a01f added
0:00:00:03.476 cpu0:2048)PCI: 3204:   classCode 0200 progIFRevID 0000
0:00:00:03.476 cpu0:2048)Device: 514: Registered device: p=0x410015051860 0x410015051430 000:001:00.0 8086:10d3 8086:a01f bd=0x41000168f1a0

Having little experience with Linux, I can't say whether it really is an issue of insufficient resources. The system has 16 GB of RAM, and these logs are generated during boot before any VMs are powered on. I find it hard to believe there could be any memory shortage.

I googled this issue to death and am hoping an expert here can help troubleshoot it further. Thanks.

Reply
0 Kudos
1 Solution

Accepted Solutions
Fatalglitch
Enthusiast
Enthusiast
Jump to solution

Try moving the PCI card to the last slot on the motherboard, furthest from the CPU. Searching for issues similar to yours, that seemed to be a fix for the motherboard you have.

Tom Callahan, TESSCO Technologies Inc., 410-709-8662

View solution in original post

Reply
0 Kudos
5 Replies
firestartah
Virtuoso
Virtuoso
Jump to solution

Hi

Have you installed the latest driver and made sure it is on the HAL? As normally this error is from a driver conflict/error

Gregg

If you found this or other information useful, please consider awarding points for "Correct" or "Helpful". Gregg http://thesaffageek.co.uk
Reply
0 Kudos
Fatalglitch
Enthusiast
Enthusiast
Jump to solution

Try moving the PCI card to the last slot on the motherboard, furthest from the CPU. Searching for issues similar to yours, that seemed to be a fix for the motherboard you have.

Tom Callahan, TESSCO Technologies Inc., 410-709-8662
Reply
0 Kudos
anonim1
Contributor
Contributor
Jump to solution

Hi Gregg. Yes, I have verified that the NIC is in the HAL. The VID and DID in my post are identified as an Intel 82574L NIC, which is supported. The latest drivers are pre-included with the ESXi install. The one onboard working NIC is also an 82574L, so I've ruled out any sort of driver issue.

Tom, thanks for the suggestion. That was the next step I wanted to perform but couldn't last night, as I needed one VM to be running (serving as an iSCSI host for the recorded TV partition for my HTPC box). I did check the BIOS and made sure nothing was disabled as far as the PCI Express ports were concerned. I also enabled the detection of "unrecognized devices" or something to that effect, hoping it couldn't hurt. If moving the NIC to another slot makes it functional, that would lead me to believe the board only looks for display adapters in the first slot, which should be made clear in the manual.

In any case, I will try it tonight and let you all know. Thanks.

Reply
0 Kudos
jimraina
Enthusiast
Enthusiast
Jump to solution

Hi

there is more than one posibilites so please go one by one , the first this steps is if you have another NIC please add and check if not then check HAL and driver version if not then add driver manually through have disk .

____________________
Always desire to learn something useful.
http://imagicon.info/cat/5-59/vbsmile.png

Reply
0 Kudos
anonim1
Contributor
Contributor
Jump to solution

Moving the NIC to the bottom-most PCI-E slot did the trick.. thanks all for the suggestions. Hopefully this thread will show up in Google results for future cases.

Reply
0 Kudos