Release Date: 05 March, 2024

IMPORTANT:

This patch is only available for Extended Support Customers at https://customerconnect.vmware.com/downloads/#extended_support

What's in the Release Notes

The release notes cover the following topics:

• Patch Build Details
• Resolved Issues

Build Details

Download Filename:	ESXi670-202403001.zip
Build:	23084122
Download Size:	330.5 MB
md5sum:	142bb6a101f9f5ecf727abdd94e1401d
sha256checksum:	6ed73043b280bfbec0ae5dc13f17af7c6db1141f3a4951c447e24682b91e98c7
Host Reboot Required:	Yes
Virtual Machine Migration or Shutdown Required:	Yes

Bulletins

Bulletin ID	Category	Severity
ESXi670-202403401-SG	Security	Critical
ESXi670-202403402-SG	Security	Critical

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-202403001	Security	Critical

IMPORTANT: For clusters using VMware vSAN, you must first upgrade the vCenter Server system. Upgrading only the ESXi hosts is not supported.
Before an upgrade, always verify in the VMware Product Interoperability Matrix compatible upgrade paths from earlier versions of ESXi, vCenter Server and vSAN to the current version. 

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-20240304001-standard

ESXi-6.7.0-20240304001-no-tools

For more information about the individual bulletins, see the Product Patches page and the Resolved Issues section.

Patch Download and Installation

The typical way to apply patches to ESXi hosts is by using the VMware vSphere Update Manager. For details, see the About Installing and Administering VMware vSphere Update Manager.
ESXi hosts can be updated by manually downloading the patch ZIP file from VMware Customer Connect. From the Select a Product drop-down menu, select ESXi (Embedded and Installable) and from the Select a Version drop-down menu, select 6.7.0. Install 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-202403401-SG
• ESXi670-202403402-SG
• ESXi-6.7.0-20240304001-standard
• ESXi-6.7.0-20240304001-no-tools

ESXi670-202403401-SG

Patch Category	Security
Patch Severity	Critical
Host Reboot Required	Yes
Virtual Machine Migration or Shutdown Required	Yes
Affected Hardware	N/A
Affected Software	N/A
VIBs Included	VMware_bootbank_esx-update_6.7.0-3.193.23084122 VMware_bootbank_esx-base_6.7.0-3.193.23084122 VMware_bootbank_vsanhealth_6.7.0-3.193.22695748 VMware_bootbank_vsan_6.7.0-3.193.22695747
PRs Fixed	N/A
CVE numbers	CVE-2024-22253, CVE-2024-22254, CVE-2024-22255

Updates esx-update, esx-base, vsanhealth, and vsan VIBs to resolve the following issue:

• This release resolves CVE-2024-22253, CVE-2024-22254, and CVE-2024-22255. For more information on these vulnerabilities and their impact on VMware products, see VMSA-2024-0006.

ESXi670-202403402-SG

Patch Category	Security
Patch Severity	Critical
Host Reboot Required	Yes
Virtual Machine Migration or Shutdown Required	Yes
Affected Hardware	N/A
Affected Software	N/A
VIBs Included	VMW_bootbank_xhci-xhci_1.0-3vmw.670.3.193.23084122
PRs Fixed	N/A
CVE numbers	CVE-2024-22252

Updates the xhci VIB to resolve the following issue:

• This release resolves CVE-2024-22252. For more information on this vulnerability and its impact on VMware products, see VMSA-2024-0006.

ESXi-6.7.0-20240304001-standard

Profile Name	ESXi-6.7.0-20240304001-standard
Build	For build information, see Patches Contained in this Release.
Vendor	VMware by Broadcom, Inc.
Release Date	March 05, 2024
Acceptance Level	PartnerSupported
Affected Hardware	N/A
Affected Software	N/A
Affected VIBs	VMware_bootbank_esx-update_6.7.0-3.193.23084122 VMware_bootbank_esx-base_6.7.0-3.193.23084122 VMware_bootbank_vsanhealth_6.7.0-3.193.22695748 VMware_bootbank_vsan_6.7.0-3.193.22695747 VMW_bootbank_xhci-xhci_1.0-3vmw.670.3.193.23084122
PRs Fixed	N/A
Related CVE numbers	CVE-2024-22252, CVE-2024-22253, CVE-2024-22254, CVE-2024-22255

• This patch updates the following issue:

  • This release resolves CVE-2024-22252, CVE-2024-22253, CVE-2024-22254, and CVE-2024-22255. For more information on these vulnerabilities and their impact on VMware products, see VMSA-2024-0006.

ESXi-6.7.0-20240304001-no-tools

Profile Name	ESXi-6.7.0-20240304001-no-tools
Build	For build information, see Patches Contained in this Release.
Vendor	VMware by Broadcom, Inc.
Release Date	March 05, 2024
Acceptance Level	PartnerSupported
Affected Hardware	N/A
Affected Software	N/A
Affected VIBs	VMware_bootbank_esx-update_6.7.0-3.193.23084122 VMware_bootbank_esx-base_6.7.0-3.193.23084122 VMware_bootbank_vsanhealth_6.7.0-3.193.22695748 VMware_bootbank_vsan_6.7.0-3.193.22695747 VMW_bootbank_xhci-xhci_1.0-3vmw.670.3.193.23084122
PRs Fixed	N/A
Related CVE numbers	CVE-2024-22252, CVE-2024-22253, CVE-2024-22254, CVE-2024-22255

• This patch updates the following issue:

  • This release resolves CVE-2024-22252, CVE-2024-22253, CVE-2024-22254, and CVE-2024-22255. For more information on these vulnerabilities and their impact on VMware products, see VMSA-2024-0006.

Known Issues from Prior Releases

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

The earlier known issues are grouped as follows.

• CLI Issues
• vSAN Issues
• Internationalization Issues
• Tools Issues
• Installation, Upgrade, and Migration Issues
• Security Features Issues
• Networking Issues
• Storage Issues
• Backup and Restore Issues
• vCenter Server Appliance, vCenter Server, vSphere Web Client, and vSphere Client Issues
• Virtual Machine Management Issues
• vSphere HA and Fault Tolerance Issues
• Auto Deploy and Image Builder Issues
• Miscellaneous Issues

CLI Issues

• Views might switch from the appliance shell to the Direct Console User Interface during an upgrade of the vCenter Server Appliance by using the CLI installer

  During an upgrade of the vCenter Server Appliance by using the CLI installer, views might switch intermittently from the appliance shell to the Direct Console User Interface. Restarts of the applmgmt service during updates causes the issue.

  Workaround: Switch to appliance shell tty to monitor the progress. 

vSAN Issues

• PR 2855671: vSAN disk format upgrade fails, objects not upgrading to version 3

  When you upgrade host software from 6.0 to 6.0 Update 2, and the vCenter Server software version is 6.7, vSAN disk format upgrade fails. Objects do not upgrade to version 3. When the error occurs, the vSAN upgrade task fails with an error message such as General vSAN error. Disk format conversion failed due to unexpected error. and the host disk group format version remains unchanged.

  Workaround: Upgrade the host software to version ESXi650-201704001 that includes new features and bug fixes related to vSAN 6.6, or higher, and then upgrade the disk format version. 

Internationalization Issues

• A VMkernel network using an NSX logical switch might fail for stateless hosts if you register vCenter Server with non-ASCII characters on VMware NSX Manager

  If you register vCenter Server to an NSX Manager with a password containing characters from the extended ASCII codes between 128 and 255, or non-ASCII characters, a VMkernel network using an NSX logical switch might be lost after deploying a stateless host.

  Workaround: Register vCenter Server to an NSX Manager with a password containing only ASCII characters.

• An ESXi host might stop responding if you add a vSphere Distributed Switch named with a string containing tens of non-ASCII characters to a physical adapter in a hyper-converged infrastructure (HCI) cluster

  If you name a VDS with a string containing more than 40 characters from the extended ASCII codes between 128 and 255, or more than 26 non-ASCII characters, ESXi hosts might stop responding when you attempt to add the VDS to a physical adapter during the configuration of a hyper-converged infrastructure (HCI) cluster.

  Workaround: Use strings with less than 40 characters from the extended ASCII codes and 26 non-ASCII characters when naming a VDS.

Tools Issues

• The OVF Tool might fail to verify an SSL thumbprint if you use CLI

  If you set the SSL thumbprint value by using CLI, the OVF Tool might fail to verify the thumbprint. The issue is not monitored if you use the Direct Console User Interface (DCUI).

  Workaround: Use any of the following alternatives:

  • In the DCUI, specify the thumbprint in the section of ssl_certificate_verification.
  • In the DCUI, specify to ignore certificate thumbprint for ESXi by putting ssl_certificate_verification verification_mode to False.
  • Ignore all certificate thumbprints globally by using the command-line parameter: --no-ssl-certificate-verification.
  • Wait for the CLI prompt to accept the thumbprint that it receives from the source. 

Installation, Upgrade, and Migration Issues

• After update to ESXi670-202210001, you see an error for failed verification of the VIB signature for the esx-ui VIB

  After you complete an update to ESXi670-202210001, in the esxupdate.log for the esx-ui VIB you might see an error such as: esxupdate: xxxxx: root: ERROR: Failed to verify VIB signature #2: ('VMware_bootbank_esx-ui_xxxxx, 'Could not find a trusted signer: self signed certificate') The issue affects VIBs signed with keys expired on or after July 19, 2019, to align with NIAP compliance.

  Workaround: Ignore the message. For more information, see VMware knowledge base article 76276.

• ESXi installation or upgrade fail due to memory corruption on HPE ProLiant - DL380/360 Gen 9 Servers

  The issue occurs on HPE ProLiant - DL380/360 Gen 9 Servers that have a Smart Array P440ar storage controller.

  Workaround: Set the server BIOS mode to UEFI before you install or upgrade ESXi.

• After an ESXi upgrade to version 6.7 and a subsequent rollback to version 6.5 or earlier, you might experience failures with error messages

  You might see failures and error messages when you perform one of the following on your ESXi host after reverting to 6.5 or earlier versions:

  • Install patches and VIBs on the host
    Error message: [DependencyError] VIB VMware_locker_tools-light requires esx-version >= 6.6.0
  • Install or upgrade VMware Tools on VMs
    Error message: Unable to install VMware Tools.

  After the ESXi rollback from version 6.7, the new tools-light VIB does not revert to the earlier version. As a result, the VIB becomes incompatible with the rolled back ESXi host causing these issues.

  Workaround: Perform the following to fix this problem.

  SSH to the host and run one of these commands:

  esxcli software vib install -v /path/to/tools-light.vib

  or

  esxcli software vib install -d /path/to/depot/zip -n tools-light

  Where the vib and zip are of the currently running ESXi version.

  Note: For VMs that already have new VMware Tools installed, you do not have to revert VMware Tools back when ESXi host is rolled back.

• Special characters backslash (\) or double-quote (") used in passwords causes installation pre-check to fail

  If the special characters backslash (\) or double quote (") are used in ESXi, vCenter Single Sign-On, or operating system password fields during the vCenter Server Appliance Installation templates, the installation pre-check fails with the following error:

  Error message: com.vmware.vcsa.installer.template.cli_argument_validation: Invalid \escape: line ## column ## (char ###)

  Workaround: If you include special characters backslash (\) or double quote (") in the passwords for ESXi, operating systems, or Single-Sign-On, the special characters need to be escaped. For example, the password pass\word should be escaped as pass\\word.

• Windows vCenter Server 6.7 installer fails when non-ASCII characters are present in password

  The Windows vCenter Server 6.7 installer fails when the Single Sign-on password contains non-ASCII characters for Chinese, Japanese, Korean, and Taiwanese locales. 

  Workaround: Ensure that the Single Sign-on password contains ASCII characters only for Chinese, Japanese, Korean, and Taiwanese locales. In case your vCenter Server system is installed on an external database, both the user and password for vCenter Server login must not include non-ASCII characters for Simplified Chinese, Japanese, Korean, Traditional Chinese, French, German and Spanish locales.

• Cannot log in to vSphere Appliance Management Interface if the colon character (:) is part of vCenter Server root password

  During the vCenter Server Appliance UI installation (Set up appliance VM page of Stage 1), if you include the colon character (:) as part of the vCenter Server root password, logging into the vSphere Appliance Management Interface (https://vc_ip:5480) fails and you are unable to login. The password might be accepted by the password rule check during the setup, but login fails.

  Workaround: Do not use the colon character (:) to set the vCenter Server root password in the vCenter Server Appliance UI (Set up appliance VM of Stage 1).

• vCenter Server Appliance installation fails when the backslash character (\) is included in the vCenter Single Sign-On password

  During the vCenter Server Appliance UI installation (SSO setup page of Stage 2), if you include the backslash character (\) as part of the vCenter Single Sign-On password, the installation fails with the error Analytics Service registration with Component Manager failed. The password might be accepted by the password rule check, but installation fails.

  Workaround: Do not use the backslash character (\) to set the vCenter Single Sign-On password in the vCenter Server Appliance UI installer (SSO setup page of Stage 2)

• Scripted ESXi installation fails on HP ProLiant Gen 9 Servers with an error 

  When you perform a scripted ESXi installation on an HP ProLiant Gen 9 Server under the following conditions: 

  • The Embedded User Partition option is enabled in the BIOS. 
  • You use multiple USB drives during installation: one USB drive contains the ks.cfg file, and the others USB drive is not formatted and usable.

  The installation fails with the error message Partitions not initialized.

  Workaround:

  1. Disable the Embedded User Partition option in the server BIOS.
  2. Format the unformatted USB drive with a file system or unplug it from the server.
• Upgrading vCenter Server 6.5 for Windows to vCenter Server 6.7 might fail if the vSphere Authentication Proxy service is active

  If the vSphere Authentication Proxy service is active while you perform an upgrade from vCenter Server 6.5 for Windows to vCenter Server 6.7, the operation might fail during the pre-check. You might see an error similar to:

  The following non-configurable port(s) are already in use:
2016, 7475, 7476
Stop the process(es) that use these port(s).

  Workaround: Stop the vSphere Authentication Proxy service. You can restart the service after the successful upgrade to vCenter Server 6.7.

• Patching to vCenter Server 6.7 Update 1 from earlier versions of vCenter Server 6.7 might fail when vCenter Server High Availability is active

  Patching to vCenter Server 6.7 Update 1 from earlier versions of vCenter Server 6.7 might fail when vCenter Server High Availability is active due to a DB schema change. For more information, see VMware knowledge base article 55938.

  Workaround: To patch your system to vCenter Server 6.7 Update 1 from earlier versions of vCenter Server 6.7, you must remove vCenter Server High Availability and delete passive and witness nodes. After the upgrade, you must re-create your vCenter Server High Availability clusters.

• Windows vCenter Server 6.0.x or 6.5.x upgrade to vCenter Server 6.7 fails if vCenter Server contains non-ASCII or high-ASCII named 5.5 host profiles

  When a source Windows vCenter Server 6.0.x or 6.5.x contains vCenter Server 5.5.x host profiles named with non-ASCII or high-ASCII characters, UpgradeRunner fails to start during the upgrade pre-check process.

  Workaround: Before upgrading Windows vCenter Server 6.0.x or 6.5.x to vCenter Server 6.7, upgrade the ESXi 5.5.x with the non-ASCII or high-ASCII named host profiles to ESXi 6.0.x or 6.5.x, then update the host profile from the upgraded host by clicking Copy setting from the hosts.

• Upgrade to vCenter Server Appliance 6.7 Update 1 from vCenter Server Appliance 6.5 Update 2 and later, using custom HTTP and HTTPS ports, might fail

  Upgrades from vCenter Server Appliance 6.5 Update 2 and later, using custom HTTP and HTTPS ports, to vCenter Server Appliance 6.7 Update 1 might fail. You might see the issue regardless if you use the GUI or CLI installer.

  Workaround: None

• Converging an external Platform Services Controller to a vCenter Server might fail if the Platform Services Controller uses a custom HTTPS port

  You might fail to converge an external Platform Services Controller to a vCenter Server system, if the vCenter Server system is configured with the default HTTPS port, 443, and the Platform Services Controller node is configured with a custom value for the HTTPS port. The operation fails in the firstboot stage due to convergence issues.

  Workaround: Change the HTTPS port value to the default value, 443, for Platform Services Controller nodes before running vCenter External to Embedded Convergence tool. You can run the following commands to do the same:

  1. /usr/lib/vmware-vmafd/bin/vmafd-cli set-dc-port --server-name localhost --dc-port 443
  2. /usr/lib/vmware-vmafd/bin/vmafd-cli set-rhttpproxy-port --server-name localhost --rhttpproxy-port 443
• After an upgrade of a vCenter Server system to version 6.7 Update 2, pre-upgrade First Class Disks (FCD) might not be listed in the Global Catalog

  During an upgrade of your vCenter Server system to version 6.7 Update 2, the FCD Global Catalog might pick an ESXi host that is not yet updated to invoke a sync and the sync fails. As a result, the listVStorageObjectForSpec API might not return all FCDs created prior to the upgrade.

  Workaround: After you upgrade all ESXi hosts in the inventory, start syncDatastore API with fullSync set to true.

• If you edit the etc/issue file, vCenter Server Appliance upgrade by using the Virtual Appliance Management Infrastructure user interface fails

  If you edit the etc/issue file while you upgrade a vCenter Server Appliance by using the Virtual Appliance Management Infrastructure user interface, for example to create a Custom Login Banner, and you do not split the text in new lines, the upgrade fails. In the interface, you see an error such as:
  Got exception while trying to save metadata to a file: Unexpected content in /etc/issue file.

  Workaround: Restore the contents of the /etc/issue file before an upgrade by using the Virtual Appliance Management Infrastructure user interface. 

• After an upgrade to vCenter Server 6.7 Update 3l and later, you might see existing or new HPE VASA providers in disconnected state

  If the inventory of your vCenter Server system has vSphere Virtual Volumes supported by either of HPE 3PAR StoreServ or HPE Primera VASA providers, you might see the providers get into a disconnected state after an upgrade to vCenter Server 6.7 Update 3l or later. The issue affects 3PAR 3.3.1 MU5 storage, but not 3PAR 3.3.1 MU3 storage. 

  Workaround: Upgrade to vCenter Server 7.0 Update 1c and later. For upgrade compatibility, see VMware knowledge base article 67077.
  Alternatively, you can restore your system to a backup prior to vCenter Server 6.7 Update 3l.
  If you are not already using HPE 3PAR 3.3.1 MU5 VASA provider, postpone the VASA provider upgrade to HPE 3PAR 3.3.1 MU5 until HPE resolves the issue. For more information, see VMware knowledge base article 83038.

• You cannot run the camregister command with the -x option if the vCenter Single Sign-On password contains non-ASCII characters

  When you run the camregister command with the -x file option, for example, to register the vSphere Authentication Proxy, the process fails with an access denied error when the vCenter Single Sign-On password contains non-ASCII characters.

  Workaround: Either set up the vCenter Single Sign-On password with ASCII characters, or use the –p password option when you run the camregister command to enter the vCenter Single Sign-On password that contains non-ASCII characters.

• The Bash shell and SSH login are disabled after upgrading to vCenter Server 6.7

  After upgrading to vCenter Server 6.7, you are not able to access the vCenter Server Appliance using either the Bash shell or SSH login.

  Workaround:

  1. After successfully upgrading to vCenter Server 6.7, log in to the vCenter Server Appliance Management Interface. In a Web browser, go to: https://appliance_ip_address_or_fqdn:5480
  2. Log in as root.
     The default root password is the password you set while deploying the vCenter Server Appliance.
  3. Click Access, and click Edit.
  4. Edit the access settings for the Bash shell and SSH login. 
     When enabling Bash shell access to the vCenter Server Appliance, enter the number of minutes to keep access enabled.
  5. Click OK to save the settings.
• Management node migration is blocked if vCenter Server for Windows 6.0 is installed on Windows Server 2008 R2 without previously enabling Transport Layer Security 1.2

  This issue occurs if you are migrating vCenter Server for Windows 6.0 using an external Platform Services Controller (an MxN topology) on Windows Server 2008 R2. After migrating the external Platform Services Controller, when you run Migration Assistant on the Management node it fails, reporting that it cannot retrieve the Platform Services Controller version. This error occurs because Windows Server 2008 R2 does not support Transport Layer Security (TLS) 1.2 by default, which is the default TLS protocol for Platform Services Controller 6.7.

  Workaround: Enable TLS 1.2 for Windows Server 2008 R2.1.

  1. Navigate to the registry key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols
  2. Create a new folder and label it TLS 1.2.
  3. Create two new keys with the TLS 1.2 folder, and name the keys Client and Server.
  4. Under the Client key, create two DWORD (32-bit) values, and name them DisabledByDefault and Enabled.
  5. Under the Server key, create two DWORD (32-bit) values, and name them DisabledByDefault and Enabled.
  6. Ensure that the Value field is set to 0 and that the Base is Hexadecimal for DisabledByDefault.
  7. Ensure that the Value field is set to 1 and that the Base is Hexadecimal for Enabled.
  8. Reboot the Windows Server 2008 R2 computer.

  For more information on using TLS 1.2 with Windows Server 2008 R2, refer to the operating system vendor's documentation.

• vCenter Server containing host profiles with version less than 6.0 fails during upgrade to version 6.7

  vCenter Server 6.7 does not support host profiles with version less than 6.0. To upgrade to vCenter Server 6.7, you must first upgrade the host profiles to version 6.0 or later, if you have any of the following components:

  • ESXi host(s) version - 5.1 or 5.5
  • vCenter server version - 6.0 or 6.5
  • Host profiles version - 5.1 or 5.5

  Workaround: See KB 52932

• After upgrading to vCenter Server 6.7, any edits to the ESXi host's /etc/ssh/sshd_config file are discarded, and the file is restored to the vCenter Server 6.7 default configuration

  Due to changes in the default values in the /etc/ssh/sshd_config file, the vCenter Server 6.7 upgrade replaces any manual edits to this configuration file with the default configuration. This change was necessary as some prior settings (for example, permitted ciphers) are no longer compatible with current ESXi behavior, and prevented SSHD (SSH daemon) from starting correctly.

  CAUTION: Editing /etc/ssh/sshd_config is not recommended. SSHD is disabled by default, and the preferred method for editing the system configuration is through the VIM API (including the ESXi Host Client interface) or ESXCLI.

  Workaround: If edits to /etc/ssh/sshd_config are needed, you can apply them after successfully completing the vCenter Server 6.7 upgrade. The default configuration file now contains a version number. Preserve the version number to avoid overwriting the file.

  For further information on editing the /etc/ssh/sshd_config file, see the following Knowledge Base articles:

  • For information on enabling public/private key authentication, see Knowledge Base article KB 1002866
  • For information on changing the default SSHD configuration, see Knowledge Base article KB 1020530

Security Features Issues

• Virtualization Based Security (VBS) on vSphere in Windows Guest OSs RS1, RS2 and RS3 require HyperV to be enabled in the Guest OS.

  Virtualization Based Security (VBS) on vSphere in Windows Guest OSs RS1, RS2 and RS3 require HyperV to be enabled in the Guest OS.

  Workaround: Enable Hyper-V Platform on Windows Server 2016. In the Server Manager, under Local Server select Manage -> Add Roles and Features Wizard and under Role-based or feature-based installation select Hyper-V from the server pool and specify the server roles. Choose defaults for Server Roles, Features, Hyper-V, Virtual Switches, Migration and Default Stores. Reboot the host.

  Enable Hyper-V on Windows 10: Browse to Control Panel -> Programs -> Turn Windows features on or off. Check the Hyper-V Platform which includes the Hyper-V Hypervisor and Hyper-V Services. Uncheck Hyper-V Management Tools. Click OK. Reboot the host.

• The TLS configuration utility in vCenter Server 6.7.x does not install on certain versions of ESXi

  The TLS Configuration utility does not install on certain early versions of ESXi due to the replacement of expired digital signing certificate and key. 

  Workaround: The utility is signed with the same certificate and key as ESX VIBs. For more information on the impacted ESXi versions, see VMware knowledge base article 76555.

• Remote HTTPS servers might not send the HTTP Strict-Transport-Security response header (HSTS) ports 5480 and 5580

  In some environments, remote HTTPS servers running on ports 5480 and 5580 might not return HSTS.

  Workaround: None

Networking Issues

• Hostprofile PeerDNS flags do not work in some scenarios

  If PeerDNS for IPv4 is enabled for a vmknic on a stateless host that has an associated host profile, the iPv6PeerDNS might appear with a different state in the extracted host profile after the host reboots.

  Workaround: None.

• When you upgrade vSphere Distributed Switches to version 6.6, you might encounter a few known issues

  During upgrade, the connected virtual machines might experience packet loss for a few seconds.

  Workaround: If you have multiple vSphere Distributed Switches that need to be upgraded to version 6.6, upgrade the switches sequentially.

  Schedule the upgrade of vSphere Distributed Switches during a maintenance window, set DRS mode to manual, and do not apply DRS recommendations for the duration of the upgrade.

  For more details about known issues and solutions, see KB 52621

• VM fails to power on when Network I/O Control is enabled and all active uplinks are down

  A VM fails to power on when Network I/O Control is enabled and the following conditions are met:

  • The VM is connected to a distributed port group on a vSphere distributed switch
  • The VM is configured with bandwidth allocation reservation and the VM's network adapter (vNIC) has a reservation configured
  • The distributed port group teaming policy is set to Failover
  • All active uplinks on the distributed switch are down. In this case, vSphere DRS cannot use the standby uplinks and the VM fails to power on.

  Workaround: Move the available standby adapters to the active adapters list in the teaming policy of the distributed port group.

• Network flapping on a NIC that uses qfle3f driver might cause ESXi host to crash

  The qfle3f driver might cause the ESXi host to crash (PSOD) when the physical NIC that uses the qfle3f driver experiences frequent link status flapping every 1-2 seconds.

  Workaround: Make sure that network flapping does not occur. If the link status flapping interval is more than 10 seconds, the qfle3f driver does not cause ESXi to crash. For more information, see KB 2008093.

• Port Mirror traffic packets of ERSPAN Type III fail to be recognized by packet analyzers

  A wrong bit that is incorrectly introduced in ERSPAN Type III packet header causes all ERSPAN Type III packets to appear corrupt in packet analyzers.

  Workaround: Use GRE or ERSPAN Type II packets, if your traffic analyzer supports these types. 

• DNS configuration esxcli commands are not supported on non-default TCP/IP stacks

  DNS configuration of non-default TCP/IP stacks is not supported. Commands such as esxcli network ip dns server add -N vmotion -s 10.11.12.13 do not work.

  Workaround: Do not use DNS configuration esxcli commands on non-default TCP/IP stacks.

• Compliance check fails with an error when applying a host profile with enabled default IPv4 gateway for vmknic interface

  When applying a host profile with enabled default IPv4 gateway for vmknic interface, the setting is populated with "0.0.0.0" and does not match the host info, resulting with the following error:

  IPv4 vmknic gateway configuration doesn't match the specification

  Workaround:

  1. Edit the host profile settings.
  2. Navigate to Networking configuration > Host virtual nic or Host portgroup > (name of the vSphere Distributed Switch or name of portgroup) > IP address settings.
  3. From the Default gateway Vmkernal Network Adapter (IPv4) drop-down menu, select Choose a default IPv4 gateway for the vmknic and enter the Vmknic Default IPv4 gateway.
• Intel Fortville series NICs cannot receive Geneve encapsulation packets with option length bigger than 255 bytes

  If you configure Geneve encapsulation with option length bigger than 255 bytes, the packets are not received correctly on Intel Fortville NICs X710, XL710, and XXV710.

  Workaround: Disable hardware VLAN stripping on these NICs by running the following command:

  esxcli network nic software set --untagging=1 -n vmnicX.

• RSPAN_SRC mirror session fails after migration

  When a VM connected to a port assigned for RSPAN_SRC mirror session is migrated to another host, and there is no required pNic on the destination network of the destination host, then the RSPAN_SRC mirror session fails to configure on the port. This causes the port connection to fail failure but the vMotion migration process succeeds.

  Workaround: To restore port connection failure, complete either one of the following:

  • Remove the failed port and add a new port.
  • Disable the port and enable it.

  The mirror session fails to configure, but the port connection is restored.

Storage Issues

• NFS datastores intermittently become read-only

  A host's NFS datastores may become read-only when the NFS vmknic temporarily loses its IP address or after a stateless hosts reboot.

  Workaround: You can unmount and remount the datastores to regain connectivity through the NFS vmknic. You can also set the NFS datastore write permission to both the IP address of the NFS vmknic and the IP address of the Management vmknic.

• When editing a VM's storage policies, selecting Host-local PMem Storage Policy fails with an error 

  In the Edit VM Storage Policies dialog, if you select Host-local PMem Storage Policy from the dropdown menu and click OK, the task fails with one of these errors:

  The operation is not supported on the object.

  or

  Incompatible device backing specified for device '0'"Detailed

  Workaround: You cannot apply the Host-local PMem Storage Policy to VM home. For a virtual disk, you can use the migration wizard to migrate the virtual disk and apply the Host-local PMem Storage Policy.

• Datastores might appear as inaccessible after ESXi hosts in a cluster recover from a permanent device loss state

  This issue might occur in the environment where the hosts in the cluster share a large number of datastore, for example, 512 to 1000 datastores.
  After the hosts in the cluster recover from the permanent device loss condition, the datastores are mounted successfully at the host level. However, in vCenter Server, several datastores might continue to appear as inaccessible for a number of hosts.

  Workaround: On the hosts that show inaccessible datastores in the vCenter Server view, perform the Rescan Storage operation from vCenter Server.

• Incorrect behavior of the backingObjectId and SnapshotInfo fields of VStorageObjectResult

  In non-vSAN datastores, the backingObjectId and SnapshotInfo fields of VStorageObjectResult for a First Class Disk are always set to null.
  In vSAN datastores, when you create a snapshot of a First Class Disk, backingObjectId and SnapshotInfo fields of VStorageObjectResult for the First Class Disk are populated. If the First Class Disk has multiple snapshots, deleting the latest snapshot updates the backingObjectId and SnapshotInfo fields, but deleting older snapshots does not update the fields.

  Workaround: None.

• Migration of a virtual machine from a VMFS3 datastore to VMFS5 fails in a mixed ESXi 6.5 and 6.7 host environment

  If you have a mixed host environment, you cannot migrate a virtual machine from a VMFS3 datastore connected to an ESXi 6.5 host to a VMFS5 datastore on an ESXi 6.7 host.

  Workaround: Upgrade the VMFS3 datastore to VMFS5 to be able to migrate the VM to the ESXi 6.7 host.

• Warning message about a VMFS3 datastore remains unchanged after you upgrade the VMFS3 datastore using the CLI

  Typically, you use the CLI to upgrade the VMFS3 datastore that failed to upgrade during an ESXi upgrade. The VMFS3 datastore might fail to upgrade due to several reasons including the following:

  • No space is available on the VMFS3 datastore.
  • One of the extents on the spanned datastore is offline.

  After you fix the reason of the failure and upgrade the VMFS3 datastore to VMFS5 using the CLI, the host continues to detect the VMFS3 datastore and reports the following error:

  Deprecated VMFS (ver 3) volumes found. Upgrading such volumes to VMFS (ver5) is mandatory for continued availability on vSphere 6.7 host.

  Workaround: To remove the error message, restart hostd using the /etc/init.d/hostd restart command or reboot the host.

• The Mellanox ConnectX-4/ConnectX-5 native ESXi driver might exhibit performance degradation when its Default Queue Receive Side Scaling (DRSS) feature is turned on

  Receive Side Scaling (RSS) technology distributes incoming network traffic across several hardware-based receive queues, allowing inbound traffic to be processed by multiple CPUs. In Default Queue Receive Side Scaling (DRSS) mode, the entire device is in RSS mode. The driver presents a single logical queue to OS and is backed by several hardware queues.

  The native nmlx5_core driver for the Mellanox ConnectX-4 and ConnectX-5 adapter cards enables the DRSS functionality by default. While DRSS helps to improve performance for many workloads, it could lead to possible performance degradation with certain multi-VM and multi-vCPU workloads.

  Workaround: If significant performance degradation is observed, you can disable the DRSS functionality.

  1. Run the esxcli system module parameters set -m nmlx5_core -p DRSS=0 RSS=0 command.
  2. Reboot the host.
• Datastore name does not extract to the Coredump File setting in the host profile

  When you extract a host profile, the Datastore name field is empty in the Coredump File setting of the host profile. Issue appears when using esxcli command to set coredump.

  Workaround:

  1. Extract a host profile from an ESXi host.
  2. Edit the host profile settings and navigate to General System Settings > Core Dump Configuration > Coredump File.
  3. Select Create the Coredump file with an explicit datastore and size option and enter the Datastore name, where you want the Coredump File to reside.
• Native software FCoE adapters configured on an ESXi host might disappear when the host is rebooted

  After you successfully enable the native software FCoE adapter (vmhba) supported by the vmkfcoe driver and then reboot the host, the adapter might disappear from the list of adapters. This might occur when you use Cavium QLogic 57810 or QLogic 57840 CNAs supported by the qfle3 driver.

  Workaround: To recover the vmkfcoe adapter, perform these steps:

  1. Run the esxcli storage core adapter list command to make sure that the adapter is missing from the list.
  2. Verify the vSwitch configuration on vmnic associated with the missing FCoE adapter.
  3. Run the following command to discover the FCoE vmhba:
     • On a fabric setup:
       #esxcli fcoe nic discover -n vmnic_number
     • On a VN2VN setup:
       #esxcli fcoe nic discover -n vmnic_number
• Attempts to create a VMFS datastore on an ESXi 6.7 host might fail in certain software FCoE environments

  Your attempts to create the VMFS datastore fail if you use the following configuration:

  • Native software FCoE adapters configured on an ESXi 6.7 host.
  • Cavium QLogic 57810 or 57840 CNAs.
  • Cisco FCoE switch connected directly to an FCoE port on a storage array from the Dell EMC VNX5300 or VNX5700 series.

  Workaround: None.

  As an alternative, you can switch to the following end-to-end configuration:
  ESXi host > Cisco FCoE switch > FC switch > storage array from the DELL EMC VNX5300 and VNX5700 series.

Backup and Restore Issues

• Windows Explorer displays some backups with unicode differently from how browsers and file system paths show them

  Some backups containing unicode display differently in the Windows Explorer file system folder than they do in browsers and file system paths.

  Workaround: Using http, https, or ftp, you can browse backups with your web browser instead of going to the storage folder locations through Windows Explorer.

vCenter Server Appliance, vCenter Server, vSphere Web Client, and vSphere Client Issues

• The time synchronization mode setting is not retained when upgrading vCenter Server Appliance

  If NTP time synchronization is disabled on a source vCenter Server Appliance, and you perform an upgrade to vCenter Server Appliance 6.7, after the upgrade has successfully completed NTP time synchronization will be enabled on the newly upgraded appliance.

  Workaround:

  1. After successfully upgrading to vCenter Server Appliance 6.7, log into the vCenter Server Appliance Management Interface as root.

     The default root password is the password you set while deploying the vCenter Server Appliance.

      https://IP_or_FQDN_of_appliance:5480

  2. In the vCenter Server Appliance Management Interface, click Time.
  3. In the Time Synchronization pane, click Edit.
  4. From the Mode drop-down menu, select Disabled.

     The newly upgraded vCenter Server Appliance 6.7 will no longer use NTP time synchronization, and will instead use the system time zone settings.

• Login to vSphere Web Client with Windows session authentication fails on Firefox browsers of version 54 or later

  If you use Firefox of version 54 or later to log in to the vSphere Web Client, and you use your Windows session for authentication, the VMware Enhanced Authentication Plugin might fail to populate your user name and to log you in.

  Workaround: If you are using Windows session authentication to log in to the vSphere Web Client, use one of the following browsers: Internet Explorer, Chrome, or Firefox of version 53 and earlier.

• vCenter hardware health alarm notifications are not triggered in some instances

  When multiple sensors in the same category on an ESXi host are tripped within a time span of less than five minutes, traps are not received and email notifications are not sent.

  Workaround: None. You can check the hardware sensors section for any alerts.

• The vSphere Client and vSphere Web Client might not reflect update from vCenter Server 6.7 to vCenter Server 6.7 Update 1 for vCenter Server for Windows

  If you update vCenter Server for Windows from vCenter Server 6.7 to vCenter Server 6.7 Update 1, the build number details for vpxd in the Summary tab of both the vSphere Client and vSphere Web Client might not reflect the update and show version 6.7.0.

  Workaround: None.

• When using the VCSA Installer Time Sync option, you must connect the target ESX to the NTP server in the Time & Date Setting from the ESX Management

  If you want to select Time Sync with NTP server from the VCSA Installer->Stage2->Appliance configuration->Time Sync option (ESX/NTP server), you also need to have the target ESX already connected to NTP server in the Time&Date Setting from the ESX Management, otherwise it'll fail in installation.

  Workaround:

  1. Set the Time Sync option in stage2->Appliance configuration to sync with ESX
  2. Set the Time Sync option in stage2->Appliance configuration to sync with NTP Servers, make sure both the ESX and VC are set to connect to NTP servers.
• When you monitor Windows vCenter Server health, an error message appears

  Health service is not available for Windows vCenter Server. If you select the vCenter Server, and click Monitor > Health, an error message appears:

  Unable to query vSAN health information. Check vSphere Client logs for details.

  This problem can occur after you upgrade the Windows vCenter Server from release 6.0 Update 1 or 6.0 Update 2 to release 6.7. You can ignore this message.

  Workaround: None. Users can access vSAN health information through the vCenter Server Appliance.

• vCenter hardware health alarms do not function with earlier ESXi versions

  If ESXi version 6.5 Update 1 or earlier is added to vCenter 6.7, hardware health related alarms will not be generated when hardware events occur such as high CPU temperatures, FAN failures, and voltage fluctuations.

  Workaround: None.

• vCenter Server stops working in some cases when using vmodl to edit or expand a disk

  When you configure a VM disk in a Storage DRS-enabled cluster using the latest vmodl, vCenter Server stops working. A previous workaround using an earlier vmodl no longer works and will also cause vCenter Server to stop working.

  Workaround: None

• vCenter Server for Windows migration to vCenter Server Appliance fails with error

  When you migrate vCenter Server for Windows 6.0.x or 6.5.x to vCenter Server Appliance 6.7, the migration might fail during the data export stage with the error: The compressed zip folder is invalid or corrupted.

  Workaround: You must zip the data export folder manually and follow these steps:

  1. In the source system, create an environment variable MA_INTERACTIVE_MODE.
  2. Go to Computer > Properties > Advanced system settings > Environment Variables > System Variables > New.
  3. Enter "MA_INTERACTIVE_MODE" as variable name with value 0 or 1.
  4. Start the VMware Migration Assistant and provide your password.
  5. Start the Migration from the client machine. The migration will pause, and the Migration Assistant console will display the message To continue the migration, create the export.zip file manually from the export data (include export folder).
  6. NOTE: Do not press any keys or tabs on the Migration Assistant console.
  7. Go to the %appdata%\vmware\migration-assistant folder.
  8. Delete the export.zip created by the Migration Assistant.
  9. To continue the migration, manually create the export.zip file from the export folder.
  10. Return to the Migration Assistant console. Type Y and press Enter.
• Discrepancy between the build number in VAMI and the build number in the vSphere Client

  In vSphere 6.7, the VAMI summary tab displays the ISO build for the vCenter Server and vCenter Server Appliance products. The vSphere Client summary tab displays the build for the vCenter product, which is a component within the vCenter Server product.

  Workaround: None

• vCenter Server Appliance 6.7 displays an error message in the Available Update section of the vCenter Server Appliance Management Interface (VAMI)

  The Available Update section of the vCenter Server Appliance Management Interface (VAMI) displays the following error message:

  Check the URL and try again.

  This message is generated when the vCenter Server Appliance searches for and fails to find a patch or update. No functionality is impacted by this issue. This issue will be resolved with the release of the first patch for vSphere 6.7.

  Workaround: None. No functionality is impacted by this issue.

Virtual Machine Management Issues

• Name of the virtual machine in the inventory changes to its path name

  This issue might occur when a datastore where the VM resides enters the All Paths Down state and becomes inaccessible. When hostd is loading or reloading VM state, it is unable to read the VM's name and returns the VM path instead. For example, /vmfs/volumes/123456xxxxxxcc/cs-00.111.222.333.

  Workaround: After you resolve the storage issue, the virtual machine reloads, and its name is displayed again.

• You must select the "Secure boot" Platform Security Level when enabling VBS in a Guest OS on AMD systems

  On AMD systems, vSphere virtual machines do not provide a vIOMMU. Since vIOMMU is required for DMA protection, AMD users cannot select "Secure Boot and DMA protection" in the Windows Group Policy Editor when they "Turn on Virtualization Based Security". Instead select "Secure boot." If you select the wrong option it will cause VBS services to be silently disabled by Windows.

  Workaround: Select "Secure boot" Platform Security Level in a Guest OS on AMD systems.

• You cannot hot add memory and CPU for Windows VMs when Virtualization Based Security (VBS) is enabled within Windows

  Virtualization Based Security (VBS) is a new feature introduced in Windows 10 and Windows Server 2016. vSphere supports running Windows with VBS enabled starting in the vSphere 6.7 release. However, Hot add of memory and CPU will not operate for Windows VMs when Virtualization Based Security (VBS) is enabled.

  Workaround: Power-off the VM, change memory or CPU settings and power-on the VM.

• Snapshot tree of a linked-clone VM might be incomplete after a vSAN network recovery from a failure

  A vSAN network failure might impact accessibility of vSAN objects and VMs. After a network recovery, the vSAN objects regain accessibility. The hostd service reloads the VM state from storage to recover VMs. However, for a linked-clone VM, hostd might not detect that the parent VM namespace has recovered its accessibility. This results in the VM remaining in inaccessible state and VM snapshot information not being displayed in vCenter Server.

  Workaround: Unregister the VM, then re-register it to force the hostd to reload the VM state. Snapshot information will be loaded from storage.

• The Virtual Appliance Management Interface might display a 0- message or a blank page during patching from vCenter Server 6.7 to later versions

  The Virtual Appliance Management Interface might display a 0- message or a blank page during patching from vCenter Server 6.7 to later versions, if calls from the interface fail to reach the back end applmgmt service. You might also see the message Unable to get historical data import status. Check Server Status.

  Workaround: These are not failure messages. Refresh the browser and log in to the Virtual Appliance Management Interface again once the reboot of appliance in the back end is complete.

• The Ready to Complete page of the Register Virtual Machine wizard displays only one horizontal line

  The Ready to Complete page of the Register Virtual Machine wizard might display content similar to one horizontal line due to a rendering issue. This issue does not affect the workflow of the wizard.

  Workaround: None

• VMware Service Lifecycle Manager restarts the vpxd service every couple of days

  If you enable Storage I/O Control for a datastore with a large number of connected ESXi hosts, a big amount of I/O events might pile up for handling by the vpxd service. In such a case, the VMware Service Lifecycle Manager might restart vpxd.

  Workaround: Disable Storage I/O Control for datastores with a large amount of connected ESXi hosts or reduce the number of connected hosts.

• An OVF Virtual Appliance fails to start in the vSphere Client

  The vSphere Client does not support selecting vService extensions in the Deploy OVF Template wizard. As a result, if an OVF virtual appliance uses vService extensions and you use the vSphere Client to deploy the OVF file, the deployment succeeds, but the virtual appliance fails to start.

  Workaround: Use the vSphere Web Client to deploy OVF virtual appliances that use vService extensions. 

vSphere HA and Fault Tolerance Issues

• When you configure Proactive HA in Manual/MixedMode in vSphere 6.7 RC build you are prompted twice to apply DRS recommendations    

  When you configure Proactive HA in Manual/MixedMode in vSphere 6.7 RC build and a red health update is sent from the Proactive HA provider plug-in, you are prompted twice to apply the recommendations under Cluster -> Monitor -> vSphere DRS -> Recommendations. The first prompt is to enter the host into maintenance mode. The second prompt is to migrate all VMs on a host entering maintenance mode. In vSphere 6.5, these two steps are presented as a single recommendation for entering maintenance mode, which lists all VMs to be migrated.

  Workaround: There is no impact to work flow or results. You must apply the recommendations twice. If you are using automated scripts, you must modify the scripts to include the additional step.

• Lazy import upgrade interaction when VCHA is not configured

  The VCHA feature is available as part of  6.5 release. As of 6.5, a VCHA cluster cannot be upgraded while preserving the VCHA configuration. The recommended approach for upgrade is to first remove the VCHA configuration either through vSphere Client or by calling a destroy VCHA API. So for lazy import upgrade workflow without VCHA configuration, there is no interaction with VCHA.

  Do not configure a fresh VCHA setup while lazy import is in progress. The VCHA setup requires cloning the Active VM as Passive/Witness VM. As a result of an ongoing lazy import, the amount of data that needs to be cloned is large and may lead to performance issues.

  Workaround: None.

• You cannot add ESXi hosts running vSphere Fault Tolerance workloads to a vCenter Server system by using the vSphere Client

  Attempts to add ESXi hosts running vSphere Fault Tolerance workloads to a vCenter Server system by using the vSphere Client might fail with the error Cannot add a host with virtual machines that have Fault Tolerance turned on as a stand-alone host.

  Workaround: As alternatives, you can:

  1. Schedule a task to add the host and execute it immediately.
     1. In the vSphere Client, navigate to Configure > Scheduled tasks for a selected cluster.
     2. Select New scheduled task > Add Host.
     3. Schedule a time to run the task.
     4. Add a host and run the task.
     5. Delete the task after the host is added.
  2. Use the vSphere Web Client to add the host. Login to the vSphere Web Client and execute the standard add host workflow.
  3. Turn off the fault tolerance virtual machines temporarily, add the host to the new vCenter Server system, and then turn it on back again.
• vCenter Server High Availability cluster configuration by using an NSX-T logical switch might fail

  Configuration of a vCenter Server High Availability cluster by using an NSX-T logical switch might fail with the error Failed to connect peer node.

  Workaround: Configure vCenter Server High Availability clusters by using a vSphere Distributed Switch.

Auto Deploy and Image Builder Issues

• Reboot of an ESXi stateless host resets the numRxQueue value of the host

  When an ESXi host provisioned with vSphere Auto Deploy reboots, it loses the previously set numRxQueue value. The Host Profiles feature does not support saving the numRxQueue value after the host reboots.

  Workaround: After the ESXi stateless host reboots:

  1. Remove the vmknic from the host.
  2. Create a vmknic on the host with the expected numRxQueue value.
• After caching on a drive, if the server is in the UEFI mode, a boot from cache does not succeed unless you explicitly select the device to boot from the UEFI boot manager

  In case of Stateless Caching, after the ESXi image is cached on a 512n, 512e, USB, or 4Kn target disk, the ESXi stateless boot from autodeploy might fail on a system reboot. This occurs if autodeploy service is down.

  The system attempts to search for the cached ESXi image on the disk, next in the boot order. If the ESXi cached image is found, the host is booted from it. In legacy BIOS, this feature works without problems. However, in the UEFI mode of the BIOS, the next device with the cached image might not be found. As a result, the host cannot boot from the image even if the image is present on the disk.

  Workaround: If autodeploy service is down, on the system reboot, manually select the disk with the cached image from the UEFI Boot Manager.

• If an ESXi host machine uses UEFI firmware, you cannot use VMware vSphere Auto Deploy in a VLAN network

  You might not be able to use vSphere Auto Deploy to deploy an ESXi image over a VLAN network environment when the ESXi host machine uses UEFI firmware. UEFI Secure boot fails at the ipxe binary loading stage because the implementation of VLAN support of some UEFI firmware vendors might not fully support iPXE.

  Workaround: None

• A stateless ESXi host boot time might take 20 minutes or more

  The booting of a stateless ESXi host with 1,000 configured datastores might require 20 minutes or more.

  Workaround: None.

Miscellaneous Issues

• When you add or edit ESXi users by using the VMware Host Client, you see the option Enable Shell Access

  When you log in to ESXi by using the VMware Host Client to modify or create ESXi users, you see the option Enable Shell Access along with the required user name, description and password. However, this option works only for users with full access admin permissions.

  Workaround: None.

• ESXi hosts might fail with a purple diagnostic screen and a #PF Exception 14 for the qfle3f driver

  An issue with the qfle3f driver when it loses Fibre Channel over Ethernet (FCoE) connections might cause ESXi hosts to fail with a purple diagnostic screen. In the error screen, you see messages such as: @BlueScreen: #PF Exception 14 in world 1001390820:qcnic IP 0xXXXXX addr 0xXX. The issue might trigger when you unload the qfle3f driver, reboot the ESXi host or switch or disable the FCoE port or link.

  Workaround: None.

• ESXi might fail during reboot with VMs running on the iSCSI LUNs claimed by the qfle3i driver

  ESXi might fail during reboot with VMs running on the iSCSI LUNs claimed by the qfle3i driver if you attempt to reboot the server with VMs in the running I/O state.

  Workaround: First power off VMs and then reboot the ESXi host.

• VXLAN stateless hardware offloads are not supported with Guest OS TCP traffic over IPv6 on UCS VIC 13xx adapters

  You may experience issues with VXLAN encapsulated TCP traffic over IPv6 on Cisco UCS VIC 13xx adapters configured to use the VXLAN stateless hardware offload feature. For VXLAN deployments involving Guest OS TCP traffic over IPV6, TCP packets subject to TSO are not processed correctly by the Cisco UCS VIC 13xx adapters, which causes traffic disruption. The stateless offloads are not performed correctly. From a TCP protocol standpoint this may cause incorrect packet checksums being reported to the ESXi software stack, which may lead to incorrect TCP protocol processing in the Guest OS.

  Workaround: To resolve this issue, disable the VXLAN stateless offload feature on the Cisco UCS VIC 13xx adapters for VXLAN encapsulated TCP traffic over IPV6. To disable the VXLAN stateless offload feature in UCS Manager, disable the Virtual Extensible LAN field in the Ethernet Adapter Policy. To disable the VXLAN stateless offload feature in the CIMC of a Cisco C-Series UCS server, uncheck Enable VXLAN field in the Ethernet Interfaces vNIC properties section.

• Significant time might be required to list a large number of unresolved VMFS volumes using the batch QueryUnresolvedVmfsVolume API

  ESXi provides the batch QueryUnresolvedVmfsVolume API, so that you can query and list unresolved VMFS volumes or LUN snapshots. You can then use other batch APIs to perform operations, such as resignaturing specific unresolved VMFS volumes. By default, when the API QueryUnresolvedVmfsVolume is invoked on a host, the system performs an additional filesystem liveness check for all unresolved volumes that are found.  The liveness check detects whether the specified LUN is mounted on other hosts, whether an active VMFS heartbeat is in progress, or if there is any filesystem activity. This operation is time consuming and requires at least 16 seconds per LUN. As a result, when your environment has a large number of snapshot LUNs, the query and listing operation might take significant time.

  Workaround: To decrease the time of the query operation, you can disable the filesystem liveness check. 

  1. Log in to your host as root.
  2. Open the configuration file for hostd using a text editor. The configuration file is located in /etc/vmware/hostd/config.xml under plugins/hostsvc/storage node.
  3. Add the checkLiveFSUnresolvedVolume parameter and set its value to FALSE. Use the following syntax:

     <checkLiveFSUnresolvedVolume>FALSE</checkLiveFSUnresolvedVolume>

  As an alternative, you can set the ESXi Advanced option VMFS.UnresolvedVolumeLiveCheck to FALSE in the vSphere Client.

• Importing a .csv file overwrites user input during host customization.

  User input in the Customize hosts pane is overwritten by the import process and the values from the .csv file.

  Workaround: Import the .csv file before adding manual changes in the Customize hosts pane.

• The vCenter Server Convergence Tool might fail to convert an external Platform Services Controller to an embedded Platform Services Controller due to conflicting IP and FQDN

  If you have configured an external Platform Services Controller with an IP address as an optional FQDN field during the deployment, the vCenter Server Convergence Tool might fail to convert the external Platform Services Controller to an embedded Platform Services Controller because of a name conflict.

  Workaround: Do not use the vCenter Server Convergence Tool for Platform Services Controllers installed with an IP address as an alternative or addition to the FQDN address.

• If you repoint and reconfigure the setup of a Platform Services Controller, the restore process might fail

  If you repoint and reconfigure the setup of a Platform Services Controller, the restore process might fail due to a stale service ID entry.

  Workaround: Follow the steps in VMware knowledge base article 2131327 to clean up the stale service ID before proceeding with restore.

• Attempts to log in to a vCenter Server system after an upgrade to vCenter Server 6.7 might fail with a credentials validation error

  After an upgrade of your system to vCenter Server 6.7, if you try to log in to the system by using either the vSphere Web Client or vSphere Client, and a security token or smartcard, the login might fail with an error Unable to validate the submitted credential.

  Workaround: Remove and re-add the identity source. For more information, see Add or Edit a vCenter Single Sign-On Identity Source. 

• An Enhanced vMotion Compatibility (EVC) cluster might show new CPU IDs such as IBPB even if you revert an ESXi host to an older version

  If you revert an ESXi host to an older version of ESXi, an EVC cluster might expose new CPU IDs, such as IBRS, STIBP and IBPB, even though the host does not have any of the features.

  Workaround: This issue is resolved in this release. However, a host that does not meet the requirements of an EVC cluster does not automatically reconnect and you must remove it from the cluster.

• Some vCenter Server plug-ins might not correctly render the dark theme mode in the vSphere Client

  If you change color schemes in the vSphere Client to display the interface in a dark theme, some vCenter Server plug-ins might not correctly render the mode.

  Workaround: None

• If you enable per-VM EVC, virtual machines might fail to power on

  If you install or use for upgrade only VMware vCenter Server 6.7 Update 1, but do not apply ESXi 6.7 Update 1, and if you configure or reconfigure per-VM EVC, virtual machines on unpatched hosts might fail to power on. You might also see the issue if you enable cluster-level EVC and even one of the hosts in the cluster is not patched with the latest update. The new CPU IDs of that cluster might not be available on the cluster. In such a cluster, if you configure or reconfigure per-VM EVC, virtual machines might fail to power on.

  Workaround: Before you configure or reconfigure per-VM EVC, upgrade all the standalone ESXi hosts, as well as hosts inside a cluster, to the latest update for hypervisor-assisted guest mitigation for guest operating systems.

• Edits to the DNS settings might cause deletion of the IPv6 loopback address from the /etc/resolv.conf and /etc/systemd/resolved.conf files

  Edits to the DNS settings by using either the Appliance Management Interface, appliance shell, or the vSphere Web Client, might cause deletion of the IPv6 loopback address from the/etc/resolv.conf and /etc/systemd/resolved.conf files.

  Workaround: To avoid deletion of the IPv6 loopback address, edit the resolv.conf files by using the Bash shell:

  1. In the /etc/resolv.conf file, set the following parameters:

     nameserver: ::1
     nameserver: <dnsserver 1>
     nameserver: <dnsserver 2>

  2. In the /etc/systemd/resolved.conf file, set the following parameters:

     [Resolve]
     LLMNR=false
     DNS=::1 <dnsserver 1> <dnsserver 2>

• The SSH service might be disabled after an external Platform Services Controller converts to an embedded Platform Services Controller

  If you convert an external Platform Services Controller to an embedded Platform Services Controller, the SSH service might be disabled based on Active Directory policies and restrictions.

  Workaround: Manually enable the SSH service after the conversion is complete.

• The Windows guest OS of a virtual machine configured with a virtual NVDIMM of size less than 16MB might fail while initializing a new disk

  If you configure a Windows virtual machine with a NVDIMM of size less than 16MB, when you try to initialize a new disk, you might see either the guest OS failing with a blue diagnostic screen or an error message in a pop-up window in the Disk Management screen. The blue diagnostic screen issue occurs in Windows 10, Windows Server 2022, and Windows 11 v21H2 guest operating systems. 

  Workaround: Increase the size of the virtual NVDIMM to 16MB or larger.

• Stateful ESXi installation might fail on hosts with a hardware iSCSI disk connected to a Emulex OneConnect OCe11100 or 14000 NIC device

  An issue with the IMA elx-esx-libelxima plug-in might cause the hostd service to fail and statefull ESXi installation cannot complete on hosts with hardware iSCSI disk connected to a Emulex OneConnect OCe11100 or 14000 NIC device. After a network boot, the ESXi server does not reboot, but you see no errors in the vSphere Client or vSphere Web Client.

  Workaround: Install a vendor-provided async version of the elx-esx-libelxima plug-in.

• The ESXi SNMP service intermittently stops working and ESXi hosts become unresponsive

  If your environment has IPv6 disabled, the ESXi SNMP agent might stop responding. As a result, ESXi hosts also become unresponsive. In the VMkernel logs, you see multiple messages such as Admission failure in path: snmpd/snmpd.3955682/uw.3955682.

  Workaround: Manually restart the SNMP service or use a cron job to periodically restart the service.

• The sensord daemon fails to report ESXi host hardware status

  A logic error in the IPMI SDR validation might cause sensord to fail to identify a source for power supply information. As a result, when you run the command vsish -e get /power/hostStats, you might not see any output.

  Workaround: None

• After upgrade to ESXi 6.7, networking workloads on Intel 10GbE NICs cause higher CPU utilization

  If you run certain types of networking workloads on an upgraded ESXi 6.7 host, you might see a higher CPU utilization under the following conditions:

  • The NICs on the ESXi host are from the Intel 82599EB or X540 families
  • The workload involves multiple VMs that run simultaneously and each VM is configured with multiple vCPUs
  • Before the upgrade to ESXi 6.7, the VMKLinux ixgbe driver was used

  Workaround: Revert to the legacy VMKLinux ixgbe driver:

  1. Connect to the ESXi host and run the following command:
     # esxcli system module set -e false -m ixgben
  2. Reboot the host.

  Note: The legacy VMKLinux ixgbe inbox driver version 3.7.x does not support Intel X550 NICs. Use the VMKLinux ixgbe async driver version 4.x with Intel X550 NICs.

• Initial install of DELL CIM VIB might fail to respond

  After you install a third-party CIM VIB it might fail to respond.

  Workaround: To fix this issue, enter the following two commands to restart sfcbd:

  1. esxcli system wbem set --enable false
  2. esxcli system wbem set --enable true

To collapse the list of previous known issues, click here.