82583V driver for ESXI 7.0 not work

[veentan]

I'm install esxi 7.0 in my 8635U 24GB mini pc with 6 82583V gigabit lan ports

but get the message "No network adapters"

I check for VMware Compatibility Guide, 82583V 8086:150c is support.

How can i get esxi 7.0 to support 82583V.

in ESXI 6.7 U3 is support for this.

Thanks.

[JafarTavana]

Download vib package and install it manually.

[veentan]

Where can i download the vib package.

i use https://vibsdepot.v-front.de/wiki/index.php/Net-e1000e to add the drive is failed.

[Nawals]

You can download the offline bundle vib which is in zip format. Once download upload to datastore and then run with following command to update it.

This command for install

esxcli software vib install -d “/vmfs/volumes/Datastore/DirectoryName/offlinebundledriver.zip”

This command to update the drive.

esxcli software vib update -d “/vmfs/volumes/Datastore/DirectoryName/offlinebundledriver.zip”

[veentan]

it is not work yet

[Nawals]

Please follow what I mentioned via SSH to esxi. Make sure don’t use esxi image. You have to download driver and follow that procedure.

You can also update or install the driver if you are using vmware update manager.

here is the refrence screenshot for install. same way you can update the drive however you just change the command esxcli software vib update -d / tmp/xyzdriver.zip

[yqowen]

@Nawals I encountered the same issue, Intel 82533V Network adapters works well in ESXi 6.7, but upgrade to ESXi7 will encounter No Network Adapter warning during the installation.

How to SSH to ESXi 7 when it's not installed yet? ( It couldn't be installed or upgraded successfully because the network adapter driver doesn't work)

In this case, do you mean we should SSH to host and update the drive on ESXi 6.7, then upgrade to ESXi7?

[Nawals]

Okay. So post upgrade this issue encounter. Then I would suggest to update the latest driver on ESXi 6.7 and then upgrade to ESXi to 7.0 Hope this will work...

[yqowen]

Thx, seems there's another issue, update the native driver on ESXi 6.7 was skipped. (Message: Host is not changed. VIBs Skipped.)

82583V network adapter consumed VMKLinux driver in ESXi 6.7 by default and recognized as e1000e, although the native driver (ne1000) was already in 6.7 U3 package.

Is there a way to disable the VMKLinux driver for this device on 6.7 and let it run with native driver?

[daphnissov]

No, it's not going to work. 7 does not any longer support vmklinux drivers. You need different hardware to run 7.0.

[Nawals]

Esxi 7.0 no longer supported vmklinux drivers. In this case looks like you to look new hardware. Below are the reference link vmklinux driver..

What is the Impact of the VMKlinux Driver Stack Deprecation? - VMware vSphere Blog

[yqowen]

Understand that, but as veentan 's screenshot, the VMware compatibility list indicated this device is support by ESXi 7.

[Nawals]

Correct. Is something lagging between compatibility matrix and vmware blog. We all know that vmklinux driver no longer supported. my assumption it may be bug in 7.0 if consider is supported as per matrix as shows. This need to report VMware to get more clarity about this.

[mjreagle2]

I'm new here - installed ESXi (free) for the first time a week ago, worked - then attempted to upgrade to 7 with this hardware.  Of course blocked despite the claimed compatibility.

- Anything I can do to help get this resolved?  How would I report it?

- If I'm still in the return window for the device that has this - should I consider returning it....I like it otherwise, but hard to predict if it will be compatible going forward with these mixed messages of compatibility and not.

[daphnissov]

If it's unsupported hardware to begin with, you're gambling regardless. If there's no native driver, you need different hardware. That's about all that can be said.

[mjreagle]

But that's the point, if you go to the compatibility matrix it says there is a native driver and it should be working.  It's just not.  If you look at 6.7 it says it was there then as well.....just it obviously wasn't using it.  If you read the forum above someone tried to force it to native in 6.7 without luck.

VMware Compatibility Guide - 82583V

[daphnissov]

Are you using the prescribed driver version? If so, you may want to open a case with GSS. It's also possible that this list isn't accurate for 7.0. Since it's such a new release, there are (and will be) things that are mistakes which are getting corrected.

[cesymphony]

[removed by moderator].

The HCL on VMWare's site definitely lists that the Intel 82583V driver is supported on previous versions which I have working, AND the 7.0 installation.  The issue is that it doesn't work.

[removed by moderator]

[paralens]

Stuck with the same issue in 2023
I know it's been 3 years since the first post in this thread but...
Maybe someone found a way to resolve or bypass the issue ;)))

My system have Intel 82583V (VID 8086, DID 150c) onboard adapters (integrated, non-discrete).
HCL is claiming Intel 82583V compatibility with both ESxi 7.0 and ESXi 7.0 U3, listed as 'ne1000' Native Async.
After upgrading to 7.0 U3g i have lost my 82583V Ethernet controllers.

Some of my hardware info below:

vmkchdev -l | grep vmnic0

0000:01:00.0 8086:150c 8086:0000 vmkernel vmnic0

lspci -v | grep -A1 -i ethernet

0000:01:00.0 Network controller Ethernet controller: Intel Corporation 82583V Gigabit Network Connection [vmnic0]
Class 0200: 8086:150c
0000:02:00.0 Network controller Ethernet controller: Intel Corporation 82583V Gigabit Network Connection [vmnic1]
Class 0200: 8086:150c

lspci -p | grep vmnic

0000:01:00.0 8086:150c 8086:0000  11/   /     A V              vmnic0
0000:02:00.0 8086:150c 8086:0000  10/   /     A V              vmnic1

vmkchdev -L

0000:00:1c.0 8086:9d10 0000:0000 vmkernel PCIe RP[0000:00:1c.0]
0000:00:1c.1 8086:9d11 0000:0000 vmkernel PCIe RP[0000:00:1c.1]

esxcfg-info | egrep -B9 -A26 "^[[:blank:]]+\|[-]+Device Id[\.]*0x150c$" | less

            \==+PCI Device :
               |----Segment.........................................0x0000
               |----Bus.............................................0x01
               |----Slot............................................0x00
               |----Function........................................0x00
               |----Runtime Owner...................................vmkernel
               |----Has Configured Owner............................true
               |----Configured Owner................................vmkernel
               |----Vendor Id.......................................0x8086
               |----Device Id.......................................0x150c
               |----Sub-Vendor Id...................................0x8086
               |----Sub-Device Id...................................0x0000
               |----Vendor Name.....................................Intel Corporation
               |----Device Name.....................................82583V Gigabit Network Connection
               |----Device Class....................................512
               |----Device Class Name...............................Ethernet controller
               |----PIC Line........................................11
               |----Old IRQ.........................................255
               |----Vector..........................................0
               |----PCI Pin.........................................0
               |----Spawned Bus.....................................0
               |----Flags...........................................12289
               \==+BAR Info :
               |----Module Id.......................................4294967295
               |----Chassis.........................................0
               |----Physical Slot...................................-1
               |----Numa Node.......................................-1
               |----VmKernel Device Name............................vmnic0
               |----Slot Description................................
               |----Device Layer Bus Address........................p0000:01:00.0
               |----Passthru Disabled...............................false
               |----Passthru Capable................................true
               |----Parent Device...................................PCI 0:0:28:0
               |----Dependent Device................................PCI 0:1:0:0
               |----Reset Method....................................4
               |----FPT Shareable...................................true

I have checked different 'ne1000' driver versions from both 6.7 and 7.x releases:
Unfortunately with no luck - none of the versions listed below are willing to work.

ne1000_0.8.4-10vmw.700.1.0.15843807
ne1000_0.8.4-11vmw.701.0.0.16850804
ne1000_0.8.4-11vmw.702.0.0.17867351
ne1000_0.8.4-11vmw.703.0.20.19193900
ne1000_0.8.4-2vmw.670.2.48.13006603
ne1000_0.9.0-1vmw.703.0.50.20036589

Also I have tried to install ESXi 7.0 GA build because this exact version is claimed by HCL as compatible with 82583V. No luck.

According to the log files, ESXi successfully detects Ethernet PCI device and even provides them with vmkX names:

2023-03-12T12:12:33.637Z vmkdevmgr[262504]: PciBus: Not committing alias vmnic0 for busAddress p0000:01:00.0
2023-03-12T12:12:33.639Z vmkdevmgr[262504]: PciBus: Not committing alias vmnic1 for busAddress p0000:02:00.0

2023-03-12T12:12:33.790Z vmkdevmgr[262504]: LoadAliases: Successfully restored ownership (OWNER_VMKERNEL) for device 'p0000:01:00.0'
2023-03-12T12:12:33.801Z vmkdevmgr[262504]: LoadAliases: Successfully restored ownership (OWNER_VMKERNEL) for device 'p0000:02:00.0'

2023-03-12T12:12:33.638Z cpu1:262504)PCI: 1016: 0000:01:00.0 named 'vmnic0' (was '')
2023-03-12T12:12:33.639Z cpu1:262504)PCI: 1016: 0000:02:00.0 named 'vmnic1' (was '')

2023-03-12T12:12:33.881Z vmkdevmgr[262504]: Spinning up thread for binding driver ne1000 in parallel.
2023-03-12T12:12:33.902Z vmkdevmgr[262504]: Module 'ne1000' load by uid=0 who=root successful

The ne1000 driver module loads successfully:

2023-03-12T12:12:33.894Z cpu1:262509)Loading module ne1000 ...
2023-03-12T12:12:33.895Z cpu1:262509)Elf: 2119: module ne1000 has license ThirdParty
...
2023-03-12T12:12:33.901Z cpu1:262509)Device: 211: Registered driver 'ne1000-driver' from 48
2023-03-12T12:12:33.901Z cpu1:262509)DEBUG (ne1000): module loaded
2023-03-12T12:12:33.901Z cpu1:262509)Mod: 4821: Initialization of ne1000 succeeded with module ID 48.
2023-03-12T12:12:33.901Z cpu1:262509)ne1000 loaded successfully.

Then we can see that the ne1000 driver successfully assigned to the Ethernet PCI device detected earlier.
But something goes wrong during driver initialization:

2023-03-12T12:12:33.927Z cpu2:262509)DEBUG (ne1000): attaching device 0x53724303e3c02ac3
2023-03-12T12:12:33.927Z cpu2:262509)Device: 395: ne1000-driver:driver->ops.attachDevice :0 ms
2023-03-12T12:12:33.927Z cpu2:262509)Device: 400: Found driver ne1000-driver for device 0x53724303e3c02ac3
2023-03-12T12:12:33.927Z cpu2:262509)VMK_PCI: 774: device 0000:01:00.0 pciBar 0 bus_addr 0xdf500000 size 0x20000
2023-03-12T12:12:33.927Z cpu2:262509)DEBUG (ne1000): mapped BAR[0]: start = df500000, size = 20000, mapped to 452044f80000
2023-03-12T12:12:33.927Z cpu2:262509)VMK_PCI: 774: device 0000:01:00.0 pciBar 2 bus_addr 0xe000 size 0x20
2023-03-12T12:12:33.927Z cpu2:262509)DEBUG (ne1000): mapped BAR[2]: start = e000, size = 20, mapped to 452044f8e000
2023-03-12T12:12:33.927Z cpu2:262509)VMK_PCI: 774: device 0000:01:00.0 pciBar 3 bus_addr 0xdf520000 size 0x4000
2023-03-12T12:12:33.927Z cpu2:262509)DEBUG (ne1000): mapped BAR[3]: start = df520000, size = 4000, mapped to 452046308000
2023-03-12T12:12:33.927Z cpu2:262509)DEBUG (ne1000): rx FIFO size 20 KB, tx FIFO size 12 KB
2023-03-12T12:12:33.927Z cpu2:262509)DEBUG (ne1000): recv FIFO size 16 KB, xmit FIFO size 16 KB
2023-03-12T12:12:33.927Z cpu2:262509)DEBUG (ne1000): tx.maxFrame = 16256
2023-03-12T12:12:33.927Z cpu2:262509)DEBUG (ne1000): mmio = 452044f80000, flashio = 0, portio = e000
2023-03-12T12:12:33.927Z cpu2:262509)DEBUG (ne1000): got port 0
2023-03-12T12:12:33.927Z cpu2:262509)DEBUG (ne1000): device ID: 8086:150c:8086:0
2023-03-12T12:12:33.927Z cpu2:262509)DEBUG (ne1000): hw_addr = 0x452044f80000, flash_addr = 0x0
2023-03-12T12:12:33.927Z cpu2:262509)DEBUG (ne1000): setting mac type
2023-03-12T12:12:33.927Z cpu2:262509)DEBUG (ne1000): setting init funcs
2023-03-12T12:12:33.927Z cpu2:262509)DEBUG (ne1000): tracked a mutex object
2023-03-12T12:12:33.927Z cpu2:262509)DEBUG (ne1000): created a mutex object
2023-03-12T12:12:33.928Z cpu2:262509)DEBUG (ne1000): getting bus info
2023-03-12T12:12:33.928Z cpu2:262509)DEBUG (ne1000): rx FIFO size 20 KB, tx FIFO size 12 KB
2023-03-12T12:12:33.928Z cpu2:262509)DEBUG (ne1000): recv FIFO size 16 KB, xmit FIFO size 16 KB
2023-03-12T12:12:33.928Z cpu2:262509)DEBUG (ne1000): tx.maxFrame = 16256
2023-03-12T12:12:33.928Z cpu2:262509)DEBUG (ne1000): identifying MAC via bridge
2023-03-12T12:12:33.928Z cpu2:262509)INFO (ne1000): MAC (0) not supported yet
2023-03-12T12:12:33.928Z cpu2:262509)DEBUG (ne1000): found an object to remove
2023-03-12T12:12:33.928Z cpu2:262509)ALERT: ALERT (ne1000): failed to identify hardware.
2023-03-12T12:12:33.928Z cpu2:262509)INFO (ne1000): failed to identify adapter for device 0x53724303e3c02ac3
2023-03-12T12:12:33.928Z cpu2:262509)Device: 685: ne1000-driver:driver->ops.startDevice:1 ms
2023-03-12T12:12:33.928Z cpu2:262509)Device: 690: Device 0x53724303e3c02ac3 start from driver ne1000-driver failed with bad0001
2023-03-12T12:12:33.928Z cpu2:262509)WARNING: Device: 2489: Failed to start device 0x4303e3c01e80 p0000:01:00.0 8086150c80860000020000.

vmkernel.log shows another bunch of errors:

2023-03-12T12:12:33.928Z vmkdevmgr[262504]: Failed to set driver for 0x53724303e3c02ac3: Unable to complete Sysinfo operation.  Please see the VMkernel log file for more details.: Failure
2023-03-12T12:12:33.928Z vmkdevmgr[262504]: Device 0x53724303e3c02ac3 was not bound to driver ne1000 (module 48) for bus=pci addr=p0000:01:00.0 id=8086150c80860000020000
2023-03-12T12:12:33.937Z vmkdevmgr[262504]: PciBus:  Try driver parameter.
2023-03-12T12:12:33.938Z vmkdevmgr[262504]: Failed to set driver for 0x70e94303e3c02dcb: Unable to complete Sysinfo operation.  Please see the VMkernel log file for more details.: Failure
2023-03-12T12:12:33.938Z vmkdevmgr[262504]: Device 0x70e94303e3c02dcb was not bound to driver ne1000 (module 48) for bus=pci addr=p0000:02:00.0 id=8086150c80860000020000
2023-03-12T12:12:33.941Z vmkdevmgr[262504]: Module 'vmkbsd' load by uid=0 who=root successful
2023-03-12T12:12:33.942Z vmkdevmgr[262504]: PciBus:  Try driver parameter.

vmkwarning.log log also shows some alerts:

2023-03-12T12:12:33.928Z cpu2:262509)ALERT: ALERT (ne1000): failed to identify hardware.
2023-03-12T12:12:33.928Z cpu2:262509)WARNING: Device: 2489: Failed to start device 0x4303e3c01e80 p0000:01:00.0 8086150c80860000020000.
2023-03-12T12:12:33.937Z cpu0:262509)ALERT: ALERT (ne1000): failed to identify hardware.
2023-03-12T12:12:33.937Z cpu0:262509)WARNING: Device: 2489: Failed to start device 0x4303e3c01e80 p0000:02:00.0 8086150c80860000020000.

In addition I have checked the driver device map file to ensure compatibility with by ethernet devices:

grep 150c /etc/vmware/default.map.d/ne1000.map

regtype=native,bus=pci,id=8086150c..............,driver=ne1000

In searching for a possible workaround I have tried to set the 'experimental' driver module parameter to value of 2 (Enabled)
Enable experimental device support:

esxcli system module parameters set --module ne1000 --parameter-string "experimental=2"
esxcli system module parameters list --module ne1000

Name          Type  Value  Description
------------  ----  -----  -----------
experimental  int   2      enable experimental device support: 0 = none, 1 = partial (default), 2 = all

But no luck either.

PS: Unfortunately my NUC-like system does not have any PCI slots available.

[paralens]

Stuck with the same issue in 2023
Tried to post here details of the issue but moderator erases all my messages ...

My system have Intel 82583V (VID 8086, DID 150c) onboard adapters (integrated, non-discrete).
HCL is claiming Intel 82583V compatibility with both ESxi 7.0 and ESXi 7.0 U3, listed as 'ne1000' Native Async.
After upgrading to 7.0 U3g i have lost my 82583V Ethernet controllers.

Driver fails to initialize device - unable to get MAC address maybe. There are many warnings and alerts in the vmkernet log regarding ne1000