[RELEASE NOTES] VMware ESXi 7.0 Update 3r Release Notes

Products

• VMware vSphere ESX 7.x

Issue/Introduction

Note :- The public website hosting datacenter servers are undergoing maintenance, hence the Release notes is drafted and published in a Knowledge base article as a temporary solution.

VMware ESXi 7.0 Update 3r | 12 DEC 2024 | Build 24411414

This release resolves an issue with vSphere vMotion tasks that fail with an error NamespaceMgr could not lock the db file.

IMPORTANT: If your source system contains hosts of versions between ESXi 7.0 Update 2 and Update 3c, and Intel drivers, before upgrading to ESXi 7.0 Update 3r, see the What's New section of the VMware vCenter Server 7.0 Update 3c Release Notes, because all content in the section is also applicable for vSphere 7.0 Update 3r. Also, see the related VMware knowledge base articles: 86447, 87258, and 87308.

Environment

Build Details

Download Filename	VMware-ESXi-7.0U3r-24411414-depot.zip
Build	24411414
Download Size	382.0 MB
md5sum	03433d753ef408ce939dd3a59fd80594
SHA256 checksum	82724ee9d297a7cecb0f473c27b44b7401e227db99ea0046e15a2cd7a115ade7
Host Reboot Required	Yes
Virtual Machine Migration or Shutdown Required	Yes

Resolution

Resolved Issues:

• vSphere vMotion tasks fail with an error NamespaceMgr could not lock the db file
  
  When virtual machines are configured with namespaces, an issue with the namespace database might cause migration of such VMs with vSphere vMotion to fail. In the vSphere Client, you see errors such as:
  
  Failed to receive migration. The source detected that the destination failed to resume.

An error occurred restoring the virtual machine state during migration.NamespaceMgr could not lock the db file.
  
  The destination ESXi host vmware.log shows the following messages:
  
  [YYYY-MM-DDTHH:MM:SS] In(05) vmx - [msg.checkpoint.migration.failedReceive] Failed to receive migration.
[YYYY-MM-DDTHH:MM:SS] In(05) vmx - [msg.namespaceMgr.noLock] NamespaceMgr could not lock the db file.
  
  The issue is more likely to occur on VMs with hardware version earlier than 19, and impacts only VMs provisioned on shared datastores other than NFS, such as VMFS, vSAN, and vSphere Virtual Volumes.
  
  This issue was reported as known in KB 369767 and is resolved in this release.

Patch Download and Installation

Log in to the Broadcom Support Portal to download this patch.

For download instructions, see Download Broadcom products and software.

For details on updates and upgrades by using vSphere Lifecycle Manager, see About vSphere Lifecycle Manager and vSphere Lifecycle Manager Baselines and Images. You can also update
ESXi hosts without the use of vSphere Lifecycle Manager by using an image profile. To do this, you must manually download the patch offline bundle ZIP file.

For more information, see the Upgrading Hosts by Using ESXCLI Commands, and the VMware ESXi Upgrade guide.