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:




If you have to install the Broadcom NetXtreme II Network/iSCSI/FCoE drivers on your ESXi Host you can do this via command line or – the easy way – using Update Manager.

Step 1 – Download the Driver Set and add them to your Patch Repository

  • Download the Driver Set (VMware Download Site)
  • extract the .zip file
  • open your vCenter/Update Manager
  • open the “Patch Repository” tab
  • select “Import Patches”
  • browse to the BCM-NetXtremeII-3.0-offline_bundle-1566459.zip file


After some seconds the content will be displayed – click “Finish”

Now you can see, that the following drivers are included to your patch repository as a Host Extension:

bnx2-2.2.4f.v553                  -> Broadcom NetXtreme II Gigabit Ethernet Driver
bnx2fc-1.7876.v55.1             -> Broadcom 10G FCoE Offload Driver
bnx2i-2.78.76.v55.1              -> Broadcom NetXtreme II iSCSI HBA Driver
bnx2x-1.78.80.v55.3            -> Broadcom NetXtreme II 10G/20G Ethernet Driver
cnic-1.78.76.v55.7                -> Broadcom NetXtreme II CNIC Ethernet Driver
cnic_register-1.78.75.v55.1 -> Broadcom NetXtreme II CNIC Registration Agent

Step 2 – Create a new Baseline for the Driver Set

Now we have to create a new Baseline that includes the new added driver set. You can also include only one or more dedicated drivers to this baseline if you want:

  • switch to the “Baselines and Groups” tab in your Update Manager
  • click “Create…”

Provide a Name for the Baseline and select “Host Extension” as Baseline Type:


In the next window select your drivers and add them to the field below. Then click “Next” and “Finish”

You have now successfully created a new baseline. Before you can use this baseleine for a dedicated host or cluster we have to attach it.

Step 3 – Attach the baseline

  • select a host or a cluster and change to the “Update Manager” Tab
  • select “Attach…” and activate the baseline you have created before
  • click “Attach”

The baseline is now ready to use for the selected host(s)/Cluster – right click the object and select “Remediate”

Select “Extension Baselines” and mark the baseline you have created before. Finish the wizzard – and your baseline will be executed at the host!