Release Notes
Table Of Contents
- VMware vSphere 7.x on Dell EMC PowerEdge Servers Release Notes
- Contents
- Release summary
- Compatibility
- New and enhanced in VMware vSphere 7.0 release
- Known issues
- vLCM upgrade fails when Mellanox-nmlx4 Async 3.19.70.1 driver is installed
- Host seeding feature fails to perform when Dell EMC customized VMware 7.0 U2 A00 image is installed
- vLCM upgrade with Dell EMC 7.0 U1-A03 Custom Addon file with Intel-icen Async driver 1.4.2.0 fails
- VMware ESXi 7.0 U2 A00 fails to boot on upgrading from earlier ESXi version using custom offline bundles
- An ESXi host with Solarflare devices may experience PSOD during reboot post enabling SR-IOV
- Persistent memory datastore is not listed under vCenter
- iDRAC web interface displays incorrect status with ESXi inbox native driver
- Configuration changes made are not persistent across hosts that are restarted
- Operating system takes more time to complete boot when Intel DCPMM is configured in the interleaved app-direct mode
- All vCPUs assigned to a virtual machine are not visible in the guest operating system
- The Dell iSM and SFCB services fail to start after DCUI restarts the management agents
- Hostd core dump files are generated in /var/core on the VMware ESXi 7.0 host
- Virtual machine fails to start when Secure Encrypted Virtualization is enabled
- Virtual machine with Secure Encrypted Virtualization enabled uses only one VMware vCPU
- NVDIMM battery health status is displayed incorrectly on vCenter web client and ESXi host web client
- The health status of the SD cards are not updated under the Hardware Health tab
- Network connectivity is lost when virtual machines configured with Virtual Guest Tagging (VGT) are migrated to another ESXi host
- The Hardware Health tab of the vCenter Web Client does not display any information when a drive is removed
- Status of the NVMe devices configured as a host cache device is not updated after surprise removal
- Upgrading to ESXi 7.0 from earlier ESXi version fails
- VMware ESXi 7.0 does not boot after upgrading from VMware ESXi 6.5.x
- Upgrading to ESXi 7.0 from earlier ESXi version fails due to system management software incompatibility
- Installation of ESXi 7.0 fails on PowerEdge modular servers with BCM 5719 or 5720
- Surprise hot-plug of NVMe device is not supported
- Surprise hot-plug of an NVMe in a vSAN environment results in a PSOD
- The esxcli commands fail to locate the non-NVMe storage devices
- The option to start the NTP service does not work post configuration
- The driver modules qedf and qedi are not available for the QLogic 412xx adapter
- Unable to enable SRIOV on Solarfare devices with ESXi 7.0
- The rdma module for BCM 57416 devices fail to load in ESXi 7.0
- Uninstalling Dell EMC iSM VIB fails to delete files
- FCoE adapter speed is displayed as 0
- Status of the FCoE controller is displayed as offline
- The NIC description is incorrect
- The hardware label for PCIe devices is shown as Not appropriate
- Description of the NVMe drive displayed is incorrect
- Resources and support
- Contacting Dell EMC
Workaround: Dell EMC customized image A02 supports surprise removal of NVMe device.
Systems
affected:
All Dell EMC PowerEdge servers.
Tracking number: 161528
Surprise hot-plug of an NVMe in a vSAN environment
results in a PSOD
Description: When an NVMe drive, which is configured for the cache or capacity tiers in a vSAN environment, is
removed abruptly, a PSOD results.
Applies to: ESXi 7.0
Workaround: Dell EMC customized image A02 supports surprise removal of NVMe device.
Systems
affected:
All Dell EMC PowerEdge servers that support NVMe device.
Tracking number: 161528
The esxcli commands fail to locate the non-NVMe
storage devices
Description:
On Dell EMC PowerEdge yx4x servers, the LEDs of the storage devices do not provide a blink indication
after esxcli commands are run. The command for the LED blink indication for the storage device is:
esxcli storage core device set -l=off -d <storage device uuid>
Applies to: ESXi 7.0
Workaround: Use percli to get the LED blink indication for the storage device.
Systems
affected:
Dell EMC PowerEdge yx4x servers.
Tracking number: 160207
The option to start the NTP service does not work
post configuration
Description:
After the configuration of the NTP service, the option to start the service does not work with the Host
Web Client.
Applies to: ESXi 7.0
Workaround: The NTP service can be enabled or disabled from the Services tab of the Host Web Client. vCenter
Server Web Client also allows for the NTP configuration and the NTP service to be enabled or disabled.
Systems
affected:
All Dell EMC PowerEdge servers.
Tracking number: 165026
Known issues 17