by: Helge, published: Nov 28, 2012, updated: Nov 29, 2012, in

Installing ESXi 4.1 on HP DL380 G8: No NICs Found

This kept us occupied quite a bit: after having worked with HP’s G7 line of servers for a long time, we ordered our first DL380 G8 for use with VDI. According to HP’s documentation the same custom image can (and must be) used when installing ESXi as with the G7. With that information, setting up the G8 sounded like an easy job: provision it via the existing automation mechanism and be done.


At first, everything went smoothly: the server booted from the network, loaded the install files and ran the first phase of the ESXi setup. Then it rebooted from its hard disk and continued with stage 2, happily loading the VMKernel – which displays the yellow screen. When the driver loading phase was over, the trouble started. We got this screen:

The error message is:

Error encountered before the user interface was initialized
Error (see log for more info):
This system does not have a network interface card that is plugged in, or all
network interface cards are already claimed. Installation cannot continue
as requested.

Switching to the log screen with ALT+F12 gave us this:

The relevant message is:

There is no supported nic on this host.

The message is nearly funny – the server had just booted from the network.


I will spare you the details of our bug hunt. Suffice to say, it resembled a wild goose chase that even involved HP Support. In the end we found out that it is the boot device order. It works like this:

…does not work like this:

…does not work like this:

…and works like this:

Did you notice a pattern? Sure you did. If the network card is higher up in the boot order than the hard disk, the error occurs.

Remedy (a Week Later)

After we had opened a support call with HP a technician turned up and replaced both mainboard and NIC. After that, the error was gone. Unfortunately he could not say what might have been the cause.

Previous Article XenApp and RDS Sizing Part 3 – Determining Farm Load
Next Article Citrix Profile Management Architecture - Why it is Not Based on a Mandatory Profile Any More