- Notes, cautions, and warnings
- Release summary
- Compatibility
- Known issues
- Downgrade i40en and Marvell E3 drivers on the systems with ESXi 6.5 U3 A08 image
- The UID information for the Dell PowerEdge RAID Controller H310 is displayed incorrectly
- 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
- The NIC description is incorrect
- FCoE adapter speed is displayed as 0
- The specific NVMe storage device model name is not displayed
- The vmkernel log displays a warning
- The vmkernel log displays an invalid support message on multiple PCIe devices
- PSOD is not seen in the host when the NMI option is selected in the iDRAC UI
- scsi-qla4xxx driver update fails with ESXi 6.0 U3 and ESXi 6.5.x Dell EMC customized images
- Virtual machines report guest data consistency errors after disk extend operation
- iDRAC web interface shows incorrect status with ESXi inbox native driver
- ESXi OS installed on IDSDM fails to boot when USB 3.0 is enabled
- Data integrity issue occurs when deleting virtual disks on ESXi system with PERC9 controller in RAID mode
- qedf driver data integrity may fail at 256 KB block size
- ESXi 6.5 U1 does not display the complete description of USB controller
- Critical issue observed on Dell EMC PowerEdge 14th generation servers with AMD processor and HBA330/12Gbps controller
- VMkernel logs may display a warning message in VSAN cluster configuration
- Uninstallation of Dell EMC OpenManage VIB fails to delete certain files
- Dell EMC PowerEdge servers with VSAN All-Flash configuration and deduplication enabled reports unrecoverable medium or checksum error
- ESXi 6.5 with dell-shared-perc8 driver fails to clone VMs simultaneously on a shared datastore
- qlnativefc driver does not load for QLE8262
- snmpd failure message is displayed in the vRealize log insight with snmp enabled
- ESXi OS with Secure boot enabled, the executables does not work on /scratch partition
- PowerEdge 14th generations servers installed with ESXi are configured with default login credentials
- By default, VMFS datastore is disabled on Dell EMC 14th generation PowerEdge Servers with factory-installed VMware ESXi on BOSS-S1
- Scratch partition stops working after hardware or software iSCSI is enabled on ESXi with elxiscsi Emulex driver
- Virtual machines fail to power on, when system BIOS has MMIO set to 56 TB with supported GPU configured as pass-through device
- In ESXi host client, physical NICs reports duplicate entries of the speed supported
- Embedded Host Client or vCenter Server reports an error when configuring SR-IOV
- Virtual machines fail to power on, when System BIOS has MMIO set to 56 TB with Network Controllers enabled with NPAR or NPAREP and SR-IOV
- In ESXi 6.5, xHCI related platform erratum is reported in VMkernel logs
- Hardware Health status reports the raw reading instead of the computed reading of IPMI Sensors
- iDRAC does not report the operating system information
- iDRAC does not report the operating system information
- Operating system reinstallation on top of an existing ESXi installation on a BOSS device fails
- NUMA related warning message is reported in VMkernel logs when Dell Fault Resilient Memory is enabled
- Hardware Health Status tab does not display sensor details
- VMKernel logs may display a warning message
- Hostd log may display warning message
- VMkernel logs may display a warning message related to jumpstart plugin
- SAS address of the Dell EMC PERC controller is displayed incorrectly
- SATA SSD disks may report disk protocol incorrectly
- Some Emulex controller models are displayed incorrectly
- Host platform fails due to unsupported sector sizes on the NVMe devices
- Intel Ethernet 10G 2P X520 adapter controller is displayed incorrectly
- vmnic enumeration for the Mellanox controller may display as vmnic 1000202
- Dell PERC H310 model name is displayed incorrectly
- System physical memory reported in DCUI varies
- vSphere web client displays incorrect Service Tag for Dell EMC PowerEdge blade servers
- Configuring NVMe devices as passthrough device to the guest operating system, ESXi host stops responding and results in PSOD
- Power supply unit status and details are displayed incorrectly in vSphere Web Client or vCenter Server
- Temperature status of the processor may display incorrectly in vSphere Web Client or vCenter Server
- Storage-related sensor details are not available in vSphere Web Client or vCenter Server
- Dell EMC PowerEdge Express Flash NVMe PCIe SSD device is not detected during hot-plug
- The status of LUN or disks is displayed as degraded
- Dual port Mellanox card displays incorrect vmnic number
- Incorrect name for Dell PowerEdge FD332 storage controller
- Software RAID is not supported for VMware ESXi
- Status of some of the PCI devices is listed as Unknown on vCenter server
- PSU wattage is not displayed for a ESXi host on the vCenter Server
- ESXi Direct Console User Interface displays the hardware label as N/A
- ESXi installation may fail while deploying from virtual media
- Unable to turn on Windows virtual machine when Dell PowerEdge Express Flash NVMe PCIe SSD is directly connected as a passthrough device
- VMware ESXi host periodically disconnect and reconnect from vCenter Server during heavy load on storage subsystem
- The PCI passthrough section on vSphere client or vCenter server does not display Dell PowerEdge Express Flash NVMe PCIe SSD
- esxcli command is unable to fetch hardware FRU list information in ESXi 6.5
- Unsafe shutdowns counter of a NVMe device is incremented for both soft and abrupt shutdowns
- Dell EMC PowerEdge servers running specific versions of ESXi 6.0 U3 fails to upgrade to ESXi 6.5.x or ESXi 6.7
- Resources and support
- Contacting Dell EMC
VMware vSphere 6.5.x on Dell EMC PowerEdge Systems Release Notes
Scratch partition stops working after hardware or software iSCSI is enabled on ESXi with elxiscsi Emulex driver
- Description:
-
When specific versions of elxiscsi Emulex driver are installed or is part of ESXi, then, enabling the hardware or software iSCSI stops the scratch partition to work. This prevents the redirection of logging to a persistent data store causing loss of log data across reboots.
- Applies to:
- ESXi 6.5.x
- Solution:
- Dell EMC recommends that you install ESXi 6.5U1-A05 customized image which has latest Emulex elxiscsi-11.2.1197.17 driver to resolve this issue.
Perform one of the following steps:
- Use syslog for logging on hardware or software iSCSI configurations with Emulex driver version elxiscsi-11.2.1152.0 and later. For more information about configuring syslog, see VMware Knowledge Base article 2003322.
- Uninstall the elxiscsi driver and the associated shared library elx-esx-libelxima.so, if Emulex is not part of the configuration. To uninstall the elxiscsi driver, run the following commands:
- /etc/init.d/hostd stop
- localcli software vib remove -n elxiscsi -n elx-esx-libelxima.so
- reboot
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please select whether the article was helpful or not.
Comments cannot contain these special characters: <>()\