Release Date: APR 7, 2020
Build Details
Download Filename: | ESXi670-202004001.zip |
Build: | 15820472 |
Download Size: | 340.7 MB |
md5sum: | 594e5e0bb88e1187b4b731b7ced07d9c |
sha1checksum: | dd70d556cf8c550ab324c555974302975749fe48 |
Host Reboot Required: | Yes |
Virtual Machine Migration or Shutdown Required: | Yes |
Bulletins
Bulletin ID | Category | Severity |
ESXi670-202004301-BG | Bugfix | Important |
Rollup Bulletin
This rollup bulletin contains the latest VIBs with all the fixes since the initial release of ESXi 6.7.
Bulletin ID | Category | Severity |
ESXi670-202004001 | Bugfix | 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-6.7.0-20200403001-standard |
ESXi-6.7.0-20200403001-no-tools |
For more information about the individual bulletins, see the Download Patches page and the Resolved Issues section.
Patch Download and Installation
The typical way to apply patches to ESXi hosts is through the VMware vSphere Update Manager. For details, see the About Installing and Administering VMware vSphere Update Manager.
You can update ESXi hosts by manually downloading the patch ZIP file from the VMware download page and installing the VIBs by using the esxcli software vib update
command. Additionally, you can update the system by using the image profile and the esxcli software profile update
command.
For more information, see the vSphere Command-Line Interface Concepts and Examples and the vSphere Upgrade Guide.
Resolved Issues
The resolved issues are grouped as follows.
ESXi670-202004301-BGPatch Category | Bugfix |
Patch Severity | Important |
Host Reboot Required | Yes |
Virtual Machine Migration or Shutdown Required | Yes |
Affected Hardware | N/A |
Affected Software | N/A |
VIBs Included |
|
PRs Fixed | 2515603 |
Related CVE numbers | N/A |
This patch updates the esx-base, esx-update, vsan and vsanhealth
VIBs to resolve the following issue:
- PR 2515603: Incorrect allocation of persistent memory (PMem) in non-uniform memory access (NUMA) nodes might cause performance issues
In certain cases, a virtual machine might run on one NUMA node and the VMkernel might allocate PMem to that virtual machine from a different NUMA node. As a result, access to non-volatile dual in-line memory modules (NVDIMM) in the virtual machine becomes remote and might cause performance issues.
This issue is resolved in this release. For more information, see VMware knowledge base article 78094.
Profile Name | ESXi-6.7.0-20200403001-standard |
Build | For build information, see the top of the page. |
Vendor | VMware, Inc. |
Release Date | April 7, 2020 |
Acceptance Level | PartnerSupported |
Affected Hardware | N/A |
Affected Software | N/A |
Affected VIBs |
|
PRs Fixed | 2515603 |
Related CVE numbers | N/A |
- This patch updates the following issue:
In certain cases, a virtual machine might run on one NUMA node and the VMkernel might allocate PMem to that virtual machine from a different NUMA node. As a result, access to non-volatile dual in-line memory modules (NVDIMM) in the virtual machine becomes remote and might cause performance issues. For more information, see VMware knowledge base article 78094.
Profile Name | ESXi-6.7.0-20200403001-no-tools |
Build | For build information, see the top of the page. |
Vendor | VMware, Inc. |
Release Date | April 7, 2020 |
Acceptance Level | PartnerSupported |
Affected Hardware | N/A |
Affected Software | N/A |
Affected VIBs |
|
PRs Fixed | 2515603 |
Related CVE numbers | N/A |
- This patch updates the following issue:
In certain cases, a virtual machine might run on one NUMA node and the VMkernel might allocate PMem to that virtual machine from a different NUMA node. As a result, access to non-volatile dual in-line memory modules (NVDIMM) in the virtual machine becomes remote and might cause performance issues. For more information, see VMware knowledge base article 78094.