VMware Cloud Community
zhanasbay
Contributor
Contributor

VMware ESXi: No Network Adapters

VMware ESXi 7.0.3 (ESXi 7.0 U3 for Gen9 July 2022) is not installed on the computer. First comes a purple screen error. Attached is a photo below. I press Shift+O and write cpuUniformityHardCheckPanic=FALSE. The download continues and the error "No Network Adapters" appears. Tried downloading ESXi Customizer and integrating ESXi with Net-Community-Driver_1.2.7.0-1.zip drivers. I tried to install, got the same error with the drivers. Help me please.

 

Computer:

13th Gen Intel(R) Core(TM) i5-13600K
32 GB Memory
Motherboard H670 Steel Legend 
Dragon 2.5G LAN
SSD: 512GB+HDD 2 TB

IMG_0927.JPGIMG_0929 (1).jpg

Reply
0 Kudos
4 Replies
maksym007
Expert
Expert

Is this PC or whatever compatible with ESXi? 

Looks like CPU and network card are crazy from what you are trying to install :slightly_smiling_face: 

Now seriously, check if possible, BIOS settings, highly possible that CPU settings should be adjusted and check the network card. Maybe try another slot. IF this is LOM card, you are in a troubles

zhanasbay
Contributor
Contributor

I changed the network card, it worked. What needs to be done to load ESXi without problems. And then every time I reboot, an error occurs with the CPU.

Tags (1)
Reply
0 Kudos
bigelv
Contributor
Contributor

what network card are you used?
i saw in this video he dont even use other network card

https://www.youtube.com/watch?v=pUCGzA_wwo0

have you read this btw?
ESXi 7 and 8 Installation fails with "Fatal CPU mismatch on feature" | virten.net

Reply
0 Kudos
michelkeus_stwg
Enthusiast
Enthusiast

The CPU "problem" is related to the new Intel big.LITTLE architecture. Officially the 12th and 13th gen CPUs are not supported. The kernel parameter you set "cpuUniformityHardCheckPanic=FALSE" can be made permanent so you do not have to do it every time at boot.

The command for that is: esxcli system settings kernel set -s cpuUniformityHardCheckPanic -v FALSE

After setting that on the commandline you should be able to reboot normally (though keep in mind that the config is officially unsupported).