We’ve reviewed and changed the lay-out for ESXi system storage partitions on its boot device. This is done to be more flexible, and to support other VMware, and 3rd party solutions. Prior to vSphere 7, the ESXi system storage lay-out had several limitations. The partition sizes were fixed and the partition numbers were static, limiting partition management. This effectively restricts the support for large modules, debugging functionality and possible third-party components.
That is why we changed the ESXi system storage partition layout. We have increased the boot bank sizes, and consolidated the system partitions and made them expandable. This blog post details these changes introduced with vSphere 7 and how that reflects on the boot media requirements to run vSphere 7.
ESXi System Storage Changes
Partition Lay-out in vSphere 6.x
The partition sizes in vSphere 6.x are fixed, with an exception for the scratch partition and the optional VMFS datastore. These are created depending on the used boot media and its capacity.
Consolidated Partition Lay-out in vSphere 7
To overcome the challenges presented by using this configuration, the boot partitions in vSphere 7 are consolidated.
The ESXi 7 System Storage lay-out only consists of four partitions.
- System boot
- Stores boot loader and EFI modules.
- Type: FAT16
- Boot-banks (x2)
- System space to store ESXi boot modules
- Type: FAT16
- Acts as the unified location to store extra (nonboot) modules, system configuration and state, and system virtual machines
- Type: VMFS-L
- Should be created on high-endurance storage devices
The OSData partition is divided into two high-level categories of data called ROM-data and RAM-data. Frequently written data, for example, logs, VMFS global traces, vSAN EPD and traces, and live databases are referred to as RAM-data. ROM-data is data written infrequently, for example, VMtools ISOs, configurations, and core dumps.
ESXi 7 System Storage Sizes
Depending the boot media used, the capacity used for each partition varies. The only constant here is the system boot partition. If the boot media is larger than 128GB, a VMFS datastore is created automatically to use for storing virtual machine data.
For storage media such as USB or SD devices, the ESX-OSData partition is created on a high-endurance storage device such as an HDD or SSD. When a secondary high-endurance storage device is not available, ESX-OSData is created on USB or SD devices, but this partition is used only to store ROM-data. RAM-data is stored on a RAM disk.
ESXi 7 System Storage Contents
The sub-systems that require access to the ESXi partitions, access these partitions using the symbolic links. For example: /bootbank and /altbootbank symbolic links are used for accessing the active bootbank and alternative bootbank. The /var/core symbolic link is used to access the core-dumps.
Review the System Storage Lay-out
When examining the partition details in the vSphere Client, you’ll notice the partition lay-out as described in the previous chapters. Use this information to review your boot media capacity and the automatic sizing as configured by the ESXi installer.
A similar view can be found in the CLI of an ESXi host. You’ll notice the partitions being labeled as BOOTBANK1/2 and OSDATA.
You might notice the OSDATA partition being formatted as the Virtual Flash File System (VFFS). When the OSDATA partition is placed on a SDD or NVMe device, VMFS-L is labeled as VFSS.
vSphere supports a wide variety of boot media. This ranges from USB/SD media to local storage media devices like HDD, SSD and NVMe, or boot from a SAN LUN. To install ESXi 7, the following boot media requirements must be met:
- Boot media of at least 8GB for USB or SD devices
- 32GB for other boot devices like hard disks, or flash media like SSD or NVMe devices.
- A boot device must not be shared between ESXi hosts.
Upgrading to from ESXi 6.x to ESXi 7.0 requires a boot device that is a minimum of 4 GB. Review the full vSphere ESXi hardware requirements here. As always, the VMware Compatibility Guide is the source of truth for supported hardware devices.
Note: if you install ESXi 7 on a M.2 or other non-USB low-end flash media, beware that the storage device can be worn out quickly if you, for example, host a VM on the VMFS datastore on the same device. Be sure to delete the automatically configured VMFS datastore on the boot device when using low-end flash media. It is highly recommended to install ESXi on high-endurance flash media.
More Resources to Learn
- vSphere 7 – Why Upgrade? Here’s What Beta Participants Think!
- vSphere 7 – Lifecycle Management
- vSphere 7 – Certificate Management
- vSphere 7 – A Closer Look at the VM DRS Score
We are excited about vSphere 7 and what it means for our customers and the future. Watch the vSphere 7 Launch Event replay, an event designed for vSphere Admins, hosted by theCUBE. We will continue posting new technical and product information about vSphere 7 and vSphere with Kubernetes Monday through Thursdays into May 2020. Join us by following the blog directly using the RSS feed, on Facebook, and on Twitter. Thank you, and stay safe!