Sufficient memory: Your hosts must have at least 4 GB of RAM, 8 GB of RAM is recommended to take advantage of all features and run virtual machines in a typical production environment.
Sufficient network adapters:Your host has one or more Gigabit or faster Ethernet controllers. For a list of supported network adapter models, see the VMware Compatibility Guide.
ESXi 6.0 Booting Requirements
vSphere 6.0 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. Network booting or provisioning with VMware Auto Deploy requires the legacy BIOS firmware and is not available with UEFI BIOS configurations.
Changing the host boot type between legacy BIOS and UEFI is not supported after you install ESXi 6.0. Changing the boot type from legacy BIOS to UEFI after you install ESXi 6.0 might cause the host to fail to boot. The host displays an error message similar to:
Not a VMware boot bank
ESXi can boot from a disk larger than 2 TB provided that the system firmware and the firmware on any add-in card that you are using supports it. Check your hardware documentation.
ESXi 6.0 has these storage requirements:
1 Gigabyte+ boot device: Installing or upgrading to ESXi 6.0 requires a minimum of a 1 GB boot device.
Note: Although a 1 GB USB or SD device suffices for a minimal installation, you should use a 4 GB or larger device. The extra space is used for an expanded coredump partition on the USB/SD device.
4 GB extra for scratch partition: When booting from a local disk, a SAN or an 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 another available local disk. If no local disk can be found to serve as a scratch partition,/scratchis located on the ESXi host ramdisk, linked to/tmp/scratch. You can later reconfigure /scratch to use a separate disk or LUN.
Due to the I/O sensitivity of USB and SD devices the installer does not create a scratch partition on these devices. Again, the host attempts to configure the/scratch on an available local disk, if no local disk is available it is placed on the ramdisk.
For environments that boot from a SAN or use Auto Deploy, it is not necessary to allocate a separate LUN for each ESXi host. You can co-locate the scratch regions for many ESXi hosts onto a single LUN. The number of hosts assigned to any single LUN should be weighed against the LUN size and the I/O behavior of the virtual machines.
For best performance and memory optimization, do not leave the /scratch partition configured to use the ramdisk. To reconfigure /scratch, see theSet the Scratch Partition from the vSphere Web Client section in the vSphere Installation and Setup Guide.
Best practices for upgrading or migrating ESXi hosts
For a successful upgrade or migration, perform these best practices:
If your vSphere system includes VMware solutions or plug-ins, ensure that they are compatible with the vCenter Server version that you are upgrading to. For more information, see theVMware Product Interoperability Matrix.
Check if the version of ESXi or ESX you are currently running is supported for migration or upgrade. For more information, see theSupported Upgrades to ESXi 6.0section in thevSphere Upgrade Guide.
Check the VMware Compatibility Guide to ensure that your host hardware is tested and certified as compatible with the new version of ESXi. Check for system compatibility, I/O compatibility (network and HBA cards), and storage compatibility.
Note: It is not recommended to upgrade a host with hardware that is not certified for use with ESXi 6.0. If your host model is not on the VMware Compatibility guide, VMware recommend you contact your hardware vendor, and check if they plan to support your hardware devices on ESXi 6.0.
Ensure that sufficient disk space is available on the host for the upgrade or migration. VMware recommend a minimum of 50 MB free disk space on the installation disk of the host you are upgrading.
If you use remote management software to interact with your hosts, ensure that the software is supported and the firmware version is sufficient. For more information, see the Supported Remote Management Server Models and Firmware Versionssection in thevSphere Upgrade Guide.
If a Fiber Channel SAN is connected to the host, detach the fiber connections before continuing with the upgrade or migration. Do not disable HBA cards in the BIOS.
Ensure you have sufficient access to VMware product licenses to assign a vSphere 6.0 license to the hosts post upgrade. After the upgrade, you can use evaluation mode for 60 days. For more information, see theApplying Licenses After Upgrading to ESXi 6.0section in thevSphere Upgrade Guide.
Back up the host before performing an upgrade. If the upgrade fails, you can restore the host.