VMware ESXi 7.0 Update 3f - Build 20036589

Release Notes for VMware Solutions
Audience
Public
Content Type
Release Notes
Technology Integrations
VMware
Source Type
Documentation
  • PR 2882789: While browsing a vSphere Virtual Volumes datastore, you see the UUID of some virtual machines, instead of their name In the vSphere Client, when you right-click to browse a datastore, you might see the UUID of some virtual machines in a vSphere Virtual Volumes datastore, such as naa.xxxx, instead of their names. The issue rarely occurs in large-scale environments with a large number of containers and VMs on a vSphere Virtual Volumes datastore. The issue has no functional impact, such as affecting VM operations, backup, or anything than VM display in the vSphere Client. This issue is resolved in this release.
  • PR 2928268: A rare issue with the ESXi infrastructure might cause ESXi hosts to become unresponsive Due to a rare issue with the ESXi infrastructure, a slow VASA provider might lead to a situation where the vSphere Virtual Volumes datastores are inaccessible, and the ESXi host becomes unresponsive. This issue is resolved in this release.
  • PR 2956080: Read and write operations to a vSphere Virtual Volumes datastore might fail If a SCSI command to a protocol endpoint of a vSphere Virtual Volumes datastore fails, the endpoint might get an Unsupported status, which might be cached. As a result, following SCSI commands to that protocol endpoint fail with an error code such as 0x5 0x20, and read and write operations to a vSphere Virtual Volumes datastore fail. This issue is resolved in this release.
  • PR 2944919: You see virtual machine disks (VMDK) with stale binding in vSphere Virtual Volumes datastores When you reinstall an ESXi host after a failure, since the failed instance never reboots, stale bindings of VMDKs remain intact on the VASA provider and vSphere Virtual Volumes datastores. As a result, when you reinstall the host, you cannot delete the VMDKs due to the existing binding. Over time, many such VMDKs might accrue and consume idle storage space. This issue is resolved in this release. However, you must contact VMware Global Support Services to implement the task.