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
cable are disconnected. This issue is related to the HTML client used by both the ESXi host web client
and the vCenter web client.
Applies to: ESXi 7.0
Workaround: The esxcli hardware ipmi sdr list command displays the correct status of the NVDIMM
battery.
Systems
affected:
All Dell EMC PowerEdge servers.
Tracking number: 129009
The health status of the SD cards are not updated
under the Hardware Health tab
Description: The health status of the SD card from the Dell Internal Dual SD Module (IDSDM) is displayed as
Unknown on the respective Hardware Health tabs of the VMware ESXi web client and the vCenter
web client.
Applies to: ESXi 7.0
Workaround: The iDRAC page displays the status of the IDSDM SD cards correctly.
Systems
affected:
All Dell EMC PowerEdge servers.
Tracking number: 101450
Network connectivity is lost when virtual machines
configured with Virtual Guest Tagging (VGT) are
migrated to another ESXi host
Description:
When virtual machines that are configured with 802.1q VLAN tagging are migrated to another ESXi host,
the network connectivity is lost. The network connectivity is reestablished within a few minutes without
any user intervention.
Applies to: ESXi 7.0
Cause: VMware VMotion is unable to send a Reverse Address Resolution Protocol (RARP) for the tagged guest
virtual machine. For more information VMware Knowledge Base article 2113783.
Workaround: Force an Address Resolution Protocol (ARP) lookup request on the tagged network which generates an
egress traffic that is started from the new switch port and update the switch of the new location. Forcing
an ARP lookup request can be accomplished by performing a ping to another destination on the network
from inside the guest operating system running in the virtual machine.
Systems
affected:
All Dell EMC PowerEdge servers.
Tracking number: 173609
14 Known issues