If you want to check if the VMware Tools ISO Image on one of your ESXi hosts is corrupt, perform the following steps.

A reason why you want to check your image is an error like this:

The required VMware Tools ISO image does not exist or is inaccessible.


  • open an SSH connection to your ESXi host
  • login as root (or as a user with root rights)
  • change to /vmimages/tools-isoimages

Check the md5sum for every .iso image with the following command:

md5sum xxxxxxx.iso

for example:

Now compare the md5sum output with other ESXi hosts of the same version where you have no problems with the VMware Tools.
Help – what can I do when the ISO Image is corrupt?

Just copy the the images from a working ESXi host of the same version to the ESXi host where the issue occures. You can use a tool like eg. WinSCP for this.

If you want to power off or kill a virtual machine running on an ESXi host you can do this using the following esxcli command:

  • connect a console to your ESXi host (eg. SSH or ESXi Shell)

To get a list of all VMs running on the host use this command:

esxcli vm process list

The list contains: World ID, Process ID, VMX Cartel ID, UUID, display name and the path to the vmx config file:


To kill / power off the virtual machine use the following command:

esxcli vm process kill -type=xxxx – world-id=yyyyy

for -type=xxxx use: soft, hard or force

for world-id=yyyy use the World ID listed in the command above (eg. World ID 39731 for the example VM “Cold”)

Some information about the three possible shutdown methods:

soft = prefer this if you want to shut down “softly”

hard = equal to an immediate shutdown

force = hard kill of the VM


You can use ESXTOP to kill a VM, too! Read more about this here: How to – kill a running virtual machine process with ESXTOP


When implementing the new HP DL380 Gen9 Server in our vSphere Environment I took care of the recommended BIOS settings. Here is a summary of the settings you should be aware of in my opinion.

If you feel that there is something wrong or not mentioned, please let me know.


—> System Options

USB Options:

  • Removeable Flash Media Boot Sequence -> Internal SD Card First (only necessary if you install ESXi on the internal SD card)

Processor Options:

  • Intel (R) Hyperthreading Options -> Enabled
  • Processor Core Disable -> 0 (0 = all cores enabled)
  • Processor x2APIC Support -> Enabled

Virtualization Options:

  • Virtualization Technology -> Enabled
  • Intel (R) VT-d -> Enabled
  • SR-IOV -> Enabled

Boot Time Optimizations:

  • Extended Memory Test -> Enabled

—> Power Management

HP Power Profile -> Maximum Performance

—> Performance Options

  • Intel (R) Turbo Boost Technology -> Enabled
  • ACPI SLIT Preferences -> Enabled

—> Server Availability

ASR Status -> Disabled

Note: ASR monitors an agent running in the Service Console. When this agent is not responding within 10 minutes, the host is rebooted. However, if the agent fails or the Service Console becomes sluggish (even though the VM’s are perfectly fine), ASR will detect this as a system hang and will reboot the server. Furthermore, in case of a PSOD, ASR will reboot the server as well. This reboot might cause a loss of some logfiles.

—> Advanced Options

Fan and Thermal Options – Thermal Configuration -> Optimal Cooling or Maximum Cooling

Note: I decided to use Optimal Cooling – but in some best practices you will read the recommendation to use “Maximum Cooling”.

Your Broadcom FCoE offload adapters are not listed or displayed in your vCenter configuration tab as  storage adapters?


By default, Broadcom FCoE adapters are not listed or displayed as storage adapters. You will have to activate them using CLI or vSphere Client/Webclient.

Before you begin please take care of the following:

Activate FCoE using the Webclient/vSphere Client:

  • open the “Configuration” tab of the host
  • under “Hardware” select “Storage Adapters”
  • click “Add…”
  • select “Add Software FCoE Adapter” – OK


Now select a physical Network Adapter and click “OK”:


Note: The Broadcom FCoE solution is full offload, but is referred to as software FCoE through the vSphere interfaces. You can read more about this in VMware KB 2034702 “FCoE Configuration and Basic Troubleshooting for Broadcom NetXtreme II FCoE Offload Capable Ethernet Devices”

Success – the NetXtreme FCoE Adapter is now listed under Storage Adapters: