6.5.1

Table Of Contents
n
One or more Gigabit or faster Ethernet controllers. For a list of supported network adapter models,
see the VMware Compatibility Guide at http://www.vmware.com/resources/compatibility.
n
SCSI disk or a local, non-network, RAID LUN with unpartitioned space for the virtual machines.
n
For Serial ATA (SATA), a disk connected through supported SAS controllers or supported on-board
SATA controllers. SATA disks are considered remote, not local. These disks are not used as a scratch
partition by default because they are seen as remote.
Note You cannot connect a SATA CD-ROM device to a virtual machine on an ESXi 6.5 host. To use
the SATA CD-ROM device, you must use IDE emulation mode.
Storage Systems
For a list of supported storage systems, see the VMware Compatibility Guide at
http://www.vmware.com/resources/compatibility. For Software Fibre Channel over Ethernet (FCoE), see
Installing and Booting ESXi with Software FCoE.
ESXi Booting Requirements
vSphere 6.5 supports booting ESXi hosts from the Unified Extensible Firmware Interface (UEFI). With
UEFI, you can boot systems from hard drives, CD-ROM drives, or USB media.
Starting with vSphere 6.5, VMware Auto Deploy supports network booting and provisioning of ESXi hosts
with UEFI.
ESXi can boot from a disk larger than 2 TB if the system firmware and the firmware on any add-in card
that you are using support it. See the vendor documentation.
Note Changing the boot type from legacy BIOS to UEFI after you install ESXi 6.5 might cause the host
to fail to boot. In this case, the host displays an error message similar to Not a VMware boot bank.
Changing the host boot type between legacy BIOS and UEFI is not supported after you install ESXi 6.5.
Storage Requirements for ESXi 6.5 Installation or Upgrade
Installing ESXi 6.5 or upgrading to ESXi 6.5 requires a boot device that is a minimum of 1 GB. When
booting from a local disk, SAN or iSCSI LUN, a 5.2-GB disk is required to allow for the creation of the
VMFS volume and a 4-GB scratch partition on the boot device. If a smaller disk or LUN is used, the
installer attempts to allocate a scratch region on a separate local disk. If a local disk cannot be found the
scratch partition, /scratch, is on the ESXi host ramdisk, linked to /tmp/scratch. You can
reconfigure /scratch to use a separate disk or LUN. For best performance and memory optimization, do
not leave /scratch on the ESXi host ramdisk.
To reconfigure /scratch, see Set the Scratch Partition from the vSphere Web Client.
Due to the I/O sensitivity of USB and SD devices, the installer does not create a scratch partition on these
devices. When installing or upgrading on USB or SD devices, the installer attempts to allocate a scratch
region on an available local disk or datastore. If no local disk or datastore is found, /scratch is placed on
the ramdisk. After the installation or upgrade, you should reconfigure /scratch to use a persistent
vSphere Installation and Setup
VMware, Inc. 24