ESXi 7.0 Update 2a | 29 APR 2021 | ISO Build 17867351

Check for additions and updates to these release notes.

What's in the Release Notes

The release notes cover the following topics:

IMPORTANT: VMware removed the ESXi 7.0 Update 2 offline and online depots from all sites on March 12, 2021 due to an upgrade-impacting issue. Build 17867351 for ESXi 7.0 Update 2a replaces build 17630552 for ESXi 7.0 Update 2. All Components and Bulletins in the ESXi 7.0 Update 2a build are updated and replace the Components and Bulletins from the ESXi 7.0 Update 2 build. 

Earlier Releases of ESXi 7.0

New features, resolved, and known issues of ESXi are described in the release notes for each release. Release notes for earlier releases of ESXi 7.0 are:

For internationalization, compatibility, and open source components, see the VMware vSphere 7.0 Release Notes.

Patches Contained in This Release

This release of ESXi 7.0 Update 2a delivers the following patches:

Build Details

Download Filename: VMware-ESXi-7.0U2a-17867351-depot.zip
Build: 17867351
Download Size: 390.6 MB
md5sum: 9b676a33ef191221f8e456b63d46dd55
sha1checksum: ea71d5cf770e64359d1668a6ca49d5c4758d51f9
Host Reboot Required: Yes
Virtual Machine Migration or Shutdown Required: Yes

IMPORTANT:

  • To download the ESXi 7.0 Update 2a patch offline depot ZIP file from VMware Customer Connect, you must navigate to Products and Accounts > Product Patches. From the Select a Product drop-down menu, select ESXi (Embedded and Installable) and from the Select a Version drop-down menu, select 7.0.

  • If you have already downloaded the ESXi 7.0 Update 2 (VMware-ESXi-7.0U2-17630552-depot.zip) content in a vSphere Lifecycle Manager depot, when you download the ESXi 7.0 Update 2a base image (ESXi-7.0U2a), ESXi 7.0 Update 2a overrides ESXi 7.0 Update 2 and you cannot use the ESXi 7.0 Update 2 base image. Any operation against the ESXi 7.0 Update 2 base image returns the error A general system error occurred: The specified ESXi version cannot be found in depots. You must update the desired state to ESXi-7.0U2a base image and corresponding firmware and driver versions.

  • After you download the ESXi 7.0 Update 2a (ESXi-7.0U2a) content, you might still see the ESXi70U2-17630552 rollup bulletin. If you use patch baselines to update your system, for patch baselines with the ESXi70U2-17630552 rollup bulletin, compliance checks might return an error or a NotApplicable compliance status.

  • Starting with vSphere 7.0, VMware uses components for packaging VIBs along with bulletins. The ESXi and esx-update bulletins are dependent on each other. Always include both in a single ESXi host patch baseline or include the rollup bulletin in the baseline to avoid failure during host patching. 

  • When patching ESXi hosts by using VMware Update Manager from a version prior to ESXi 7.0 Update 2a, it is strongly recommended to use the rollup bulletin in the patch baseline. If you cannot use the rollup bulletin, be sure to include all of the following packages in the patching baseline. If the following packages are not included in the baseline, the update operation fails:
    • VMware-vmkusb_0.1-1vmw.701.0.0.16850804 or higher
    • VMware-vmkata_0.1-1vmw.701.0.0.16850804 or higher
    • VMware-vmkfcoe_1.0.0.2-1vmw.701.0.0.16850804 or higher
    • VMware-NVMeoF-RDMA_1.0.1.2-1vmw.701.0.0.16850804 or higher

Rollup Bulletin

This rollup bulletin contains the latest VIBs with all the fixes after the initial release of ESXi 7.0.

Bulletin ID Category Severity
ESXi70U2a-17867351 Enhancement Important

Image Profiles

VMware patch and update releases contain general and critical image profiles. Application of the general release image profile applies to new bug fixes.

Image Profile Name
ESXi-7.0U2a-17867351-standard
ESXi-7.0U2a-17867351-no-tools

ESXi Image

Name and Version Release Date Category Detail
ESXi_7.0.2-0.0.17867351 04/29/2021 Enhancement Bugfix image

For information about the individual components and bulletins, see the Products and Accounts > Product Patches page at VMware Customer Connect and the Resolved Issues section.

Patch Download and Installation

In vSphere 7.x, the Update Manager plug-in, used for administering vSphere Update Manager, is replaced with the Lifecycle Manager plug-in. Administrative operations for vSphere Update Manager are still available under the Lifecycle Manager plug-in, along with new capabilities for vSphere Lifecycle Manager.
The typical way to apply patches to ESXi 7.x hosts is by using the vSphere Lifecycle Manager. For details, see About vSphere Lifecycle Manager and vSphere Lifecycle Manager Baselines and Images.
You can also update ESXi hosts without using the Lifecycle Manager plug-in, and use an image profile instead. At VMware Customer Connect, for ESXi patches with an installation ISO, you can download the ISO image from Products and Accounts > All Products or navigate to Products and Accounts > Product Patches and download the patch offline bundle ZIP file. Use the esxcli software profile update command to apply the patch.
For more information, see the Upgrading Hosts by Using ESXCLI Commands and the VMware ESXi Upgrade guide.

Resolved Issues

The resolved issues are grouped as follows.

Installation, Upgrade and Migration Issues
  • PR 2727885: UEFI booting of ESXi hosts might stop with an error during an update to ESXi 7.0 Update 2 from an earlier version of ESXi 7.0

    If you attempt to update your environment to 7.0 Update 2 from an earlier version of ESXi 7.0 by using vSphere Lifecycle Manager patch baselines, UEFI booting of ESXi hosts might stop with an error such as:
    Loading /boot.cfg
    Failed to load crypto64.efi
    Fatal error: 15 (Not found)

    This issue is resolved in this release. For more information, see VMware knowledge base articles 83063 and 83107 .

  • PR 2745889: When you upgrade ESXi hosts by using the esxcli software vib update command, new VIBs might not be installed

    VMware ESXi 7.0 Update 2a adds a check to prevent missing new VIBs when upgrading ESXi hosts by using the esxcli software vib update command. By design, the esxcli software vib update command only installs VIBs that update the current system and skips new VIBs, which might lead to random system failures after the upgrade. With the new check, when you use the esxcli software vib update command, you see an InstallationError such as ESXi Base Image of version ... is not found or This upgrade transaction would skip ESXi Base Image VIB(s) ....

    This issue is resolved in this release. The new check prevents you from running an upgrade that might miss some VIBs. However, to avoid the errors with the esxcli software vib update command, you can use the esxcli software profile update command instead to perform an ESXi upgrade by using an image profile from a VMware or third-party depot. Alternatively, use the vSphere Lifecycle Manager to manage ESXi host upgrades with baselines or a desired software specification.

  • PR 2740544: Some NSX-T features might not be available after an NSX-T upgrade on ESXi 7.0 Update 2 hosts in an environment with VMware NSX-T Data Center

    Some NSX-T features and services, such as port mirroring, might not be available after an NSX-T upgrade on ESXi 7.0 Update 2 hosts in an environment with VMware NSX-T Data Center.

    This issue is resolved in this release.

Storage Issues
  • PR 2747220: After an ESXi host upgrade to ESXi 7.0 Update 2, VMFS volumes fail to mount on Serial Attached SCSI (SAS) storage

    For storage devices that support T10 standard-based VAAI specifications, VMFS provides ATS locking, also called hardware assisted locking. However, when an ESXi host upgrades to ESXi 7.0 Update 2, VMFS volumes fail to mount on SAS storage, because VAAI support is disabled due to a plug-in change. Prior to ESXi 7.0 Update 2, the Native Multipathing Plug-In (NMP) claimed SAS devices, but starting with 7.0 Update 2, the default multipathing plug-in for SAS devices has changed to the High-Performance Plug-in (HPP). HPP marks all SAS targets as local by default and disables VAAI operations, similar to the way VAAI operations are disabled on local HDDs.

    This issue is resolved in this release for SAS devices with Asymmetric Logical Unit Access (ALUA) support. However, before an update or upgrade to ESXi 7.0 Update 2a, for Active-Active and Active-Passive SAS storage controllers, you must follow the steps described in VMware knowledge base article 83249.

  • PR 2738401: Persistent volume claims (PVC) might fail because of first class disk (FCD) metadata overwrites

    If the same FCD is the target of multiple concurrent metadata write operations, some write operations might overwrite others. As a result, if many FCD happen to lose metadata, requests for persistent storage resources might fail.

    This issue is resolved in this release.

Miscellaneous Issues
  • PR 2740977: If ESXi fails to detect the end of the TPM2 ACPI table, then ESXi hosts fail with a purple diagnostic screen

    If TPM is enabled in the system firmware, ESXi might fail to detect the end of the TPM2 ACPI table during an install or upgrade operation. As a result, on some platforms, you see a system PANIC, because TPM initialization fails. In a purple diagnostic screen, you see an error such as: #PF Exception 14 in world 524288:bootstrap.

    This issue is resolved in this release. The fix detects the end of the TPM2 ACPI table in all cases.

Known Issues from Earlier Releases

To view a list of previous known issues, click here.

check-circle-line exclamation-circle-line close-line
Scroll to top icon