8.0

Table Of Contents
7 Modify the boot.cfg file
a Add the following line:
prefix=http://XXX.XXX.XXX.XXX/ESXi-8.x.x-XXXXXX
where http://XXX.XXX.XXX.XXX/ESXi-8.x.x-XXXXXX is the location of the installer files on
the HTTP server.
b If the filenames in the kernel= and modules= lines begin with a forward slash (/) character,
delete that character.
c If the kernelopt= line contains the string cdromBoot, remove the string only.
8 (Optional) For a scripted installation, in the boot.cfg file, add the kernelopt option to the line
after the kernel command, to specify the location of the installation script.
Use the following code as a model, where XXX.XXX.XXX.XXX is the IP address of the server
where the installation script resides, and esxi_ksFiles is the directory that contains the
ks.cfg file.
kernelopt=ks=http://XXX.XXX.XXX.XXX/esxi_ksFiles/ks.cfg
9 If your ESXi host runs UEFI firmware, specify whether you want all UEFI hosts to boot the
same installer.
Option
Description
Same installer Copy or link the boot.cfg file to /tftpboot/boot.cfg
Different installers a Create a subdirectory of /tftpboot named after the MAC address of
the target host machine (01-
mac_address_of_target_ESXi_host
), for
example, 01-23-45-67-89-0a-bc.
b Place a copy of (or a link to) the host's boot.cfg file in that directory, for
example,
/tftpboot/01-23-45-67-89-0a-bc/boot.cfg.
Boot the ESXi Installer by Using Native UEFI HTTP
You can boot the ESXi installer directly from an HTTP server, without additional software to
support the process.
UEFI HTTP supports booting multiple versions of the ESXi installer. You use the same mboot.efi
initial boot loader for all target machines, but potentially different boot.cfg files depending on the
target machine's MAC address.
Note Do not mix IPv4 or IPv6 networking during the boot process. Use either IPv4 or IPv6
networking.
VMware ESXi Installation and Setup
VMware, Inc. 106