ESXi install error no network device. Intel Ethernet Connection I219-LM

[sunnyimran]

Hi, 

In a need to test experiment ESXi 8.0 on my test bed setup I am out of luck. with ERROR "No network device found"  

I have been trying a lot to nested install ESXi 8.0 inside my vmware workstation 8.0 but it always ends in :no network device found"

I have tried injecting a community dirver and ISO is created sucessfully with patched driver.injected driver: Net-Community-Driver_1.2.7.0-1vmw.700.1.0.15843807_19480755.zip

but installation ends with same error. 

I have also tried  Intel® Ethernet Adapter Complete Driver Pack which mentions VMware as OS in details but sadly it does not have any VIB and can not be injected

My NIC details are
Intel Ethernet Connection I219-LM VEN_8086 DEV_15B7

Can someone help on this issue?

[LittleOne]

Hi,

looks like not supported. Take a look Community Network Driver for ESXi Documentation - VMware Technology Network VMTN

[bluefirestorm]

First of all, installing ESXi 8.0 as VM inside Workstation means it does not need a native driver of the host NIC. It depends on what is configured as the virtual NIC (e1000e or vmxnet3).

Second, why is Workstation 8.0 being used? Version 8.x was last updated more than 10 years ago. This version won't expose the Haswell instruction/feature set. Version 8.x also does not support virtual UEFI, no virtual SATA. Trying to create an ESXi 8.x installation inside Workstation 8.x is akin to trying to install ESXi 8.0 on physical hardware from 2008 or earlier.

Suggest you use the latest version Workstation Pro or Player 17.5.x if you want to try installing ESXi 8.0 as a VM.

[LittleOne]

bluefirestorm you're right I misunderstand the question. 

https://kb.vmware.com/s/article/2009916

• Known working (however still unsupported) configurations for ESXi as a guest operating system nested in a virtual machine are the following:

  • ESXi 6.0: Requires ESXi 5.5 or later, Workstation 12.0 or later, Fusion 6.0 or later
  • ESXi 6.5/6.7: Requires ESXi 6.0 or later, Workstation 14.0 or later, Fusion 10.0 or later
  • ESXi 7.0: Requires ESXi 6.7 or later, Workstation 15.5 or later, Fusion 11.5 or later
  • ESXi 8.0: Requires ESXi 7.0 or later, Workstation 16.0 or later, Fusion 12.0 or later

[Philip2]

It appears you're encountering difficulties testing ESXi 8.0 within VMware Workstation, receiving a "No network device found" error despite your efforts to inject community drivers and explore driver packs. Given your NIC details (Intel Ethernet Connection I219-LM), ensure compatibility with VMware Workstation and review virtual hardware settings. Consider alternative testing methods and seek assistance from the VMware community or support channels. Additionally, ensure host system drivers and firmware are up-to-date and consult VMware documentation for troubleshooting guidance. By systematically addressing these steps, you may resolve the issue and successfully test ESXi 8.0 within your VMware Workstation environment.😊 

[sunnyimran]

Thanks for replying

I noticed, it is a typo in my question:

"I have been trying a lot to nested install ESXi 8.0 inside my vmware workstation 8.0"

actually I meant to say mware workstation 17.5

so as you mentioned Nested ESXi does not need host NIC driver. It depends on what is configured as the virtual NIC (e1000e or vmxnet3).

I have no idea where to confirm this and may be it would be helpful in my issue

[sunnyimran]

checked the link I think it is supported as appearing in table.

https://communities.vmware.com/t5/Flings-Docs/Community-Network-Driver-for-ESXi-Documentation/ta-p/2...

Intel Ethernet Connection I219-LM (VEN_8086 DEV_15B7)

Yeah but i noticed my DEV_15B7 is not appearing under product ID. Does it make unsupported?

igc-community (All devices below is now available in ESXi 8.0 and newer)

Vendor Chipset VendorID ProductID

Intel	Ethernet Connection (6) I219-LM	0x8086	0x15bd
Intel	Ethernet Connection (6) I219-V	0x8086	0x15be
Intel	Ethernet Connection (7) I219-LM	0x8086	0x15bb
Intel	Ethernet Connection (7) I219-V	0x8086	0x15bc
Intel	Ethernet Connection (10) I219-LM	0x8086	0x0d4e
Intel	Ethernet Connection (10) I219-V	0x8086	0x0d4f
Intel	Ethernet Connection (11) I219-LM	0x8086	0x0d4c
Intel	Ethernet Connection (11) I219-V	0x8086	0x0d4d
Intel	Ethernet Connection (12) I219-LM	0x8086	0x0d53
Intel	Ethernet Connection (12) I219-V	0x8086	0x0d55
Intel	Ethernet Connection (13) I219-LM	0x8086	0x155b
Intel	Ethernet Connection (13) I219-V	0x8086	0x155c
Intel	Ethernet Connection (13) I219-LM	0x8086	0x15fb
Intel	Ethernet Connection (13) I219-V	0x8086	0x15fc
Intel	Ethernet Connection (14) I219-LM	0x8086	0x15f9
Intel	Ethernet Connection (14) I219-V	0x8086	0x15fa
Intel	Ethernet Connection (15) I219-LM	0x8086	0x15f4
Intel	Ethernet Connection (15) I219-V	0x8086	0x15f5
Intel	Ethernet Connection (16) I219-LM	0x8086	0x1a1e
Intel	Ethernet Connection (16) I219-V	0x8086	0x1a1f
Intel	Ethernet Connection (17) I219-LM	0x8086	0x1a1c
Intel	Ethernet Connection (17) I219-V	0x8086	0x1a1d

[sunnyimran]

I have also tried to inject this driver too but failed:

https://vibsdepot.v-front.de/wiki/index.php/Net-e1000e

Supported Devices / PCI IDs   

• Offline Bundle of version 3.1.0.2-glr2

[bluefirestorm]

As already mentioned, it depends on what is configured in the ESXi VM. An ESXi system running as VM inside Workstation DOES NOT need the native driver of the host machine NIC. Just like a Windows VM or Linux VM running on inside Workstation, it does not install the Intel I219-LM drivers of the host.

Anyway, go to the vmx configuration file and check what is the virtualDev assigned for ethernet[n].virtualDev. If you use the Create Virtual Machine wizard in Version 17.5, it creates a vmxnet3 by default. The vmxnet3 driver should be in the ESXi ISO. 

Examples:
ethernet0.virtualDev = "vmxnet3" or ethernet0.virtualDev = "e1000e"

The e1000e is a virtual Intel 82574L NIC.
https://www.vmware.com/resources/compatibility/detail.php?deviceCategory=io&productid=42053

[sunnyimran]

Thanks for pointing:

I observed my vmx file for ESXi 8.0 for all enteries related to 'ethernet' and i found following:

ethernet0.addressType = "generated"
ethernet0.present = "TRUE"
ethernet0.pciSlotNumber = "32"
ethernet0.generatedAddress = "some MAC Address"
ethernet0.generatedAddressOffset = "0"
ethernet0.displayName = "VMnet0"
ethernet0.connectionType = "nat"

and following:

pciBridge4.virtualDev = "pcieRootPort"
pciBridge5.virtualDev = "pcieRootPort"
pciBridge6.virtualDev = "pcieRootPort"
pciBridge7.virtualDev = "pcieRootPort"
scsi0.virtualDev = "pvscsi"

but i can not find any ethernet related virtual device as you shown in example

so what next can be done?

[bluefirestorm · Accepted solution]

You can add either

ethernet0.virtualDev = "vmxnet3"
or
ethernet0.virtualDev = "e1000e"

to the vmx configuration and then start the ESXi install.

I have no idea why your vmx is missing the vmxnet3 virtual device key-value pair. The "Create Virtual Machine" wizard automatically sets it for vmxnet3 when ESXi is chosen as the operating system type.

[sunnyimran]

Thanks bluefirestorm for pointing out the issue. Though very small but I overlooked it.

adding suggested config made it to instsall and functioning.

‎ethernet0.virtualDev = "vmxnet3"

Now I have some quick questions

Q.1 vSphere Client Vs vSphere Remote Console difference?

I have setup my nested ESXi 8 on a PC-1 which is part of a domain.

it is like PC-1 > Windows 10 > VmWare Workstation 17.5 > ESXi 8.0 Host-1  (network type NAT)

I am able to access ESXi 8 host on Windows 10 PC-1 using web browser. 

I have another similar setup. anotehr PC with ESXi 8 host

PC-2 > Windows 10 > VmWare Workstation 17.5 > ESXi 8.0 Host-2 (network type ?)

and yet another PC setup I am going to install nested vCenter Server

PC-2 > Windows 10 > VmWare Workstation 17.5 > vCenter Server (network type ?)

PC-1, PC-2, PC-3 are all domain joined windwos 10 machines having vmware workstation 17.5 working.

Q.2 Please suggest the required configuration such that vCenter Server on PC-3 can be used to manage ESXi 8.0 Host-1 on PC-1 and ESXi Host-2 on PC-2