Release Notes

Release Notes 5
• When you install ESX 4.0 on a PowerEdge T310 system with Intel Core i3
5xx processor, the 80.Iommu script fails to execute.
• Unknown entries are displayed when the lspci command is executed.
• The iDRAC communication stops when ESX loads network drivers.
• ESXi 4.0 (Embedded edition) installation fails.
• VMware vCenter Server does not display the correct network performance
details.
• When the storage controller battery is in the learning mode, VMware
vSphere Server displays the following message:
I2C error
detected.
• On a Non-Uniform Memory Access (NUMA) enabled system, ESX/ESXi
may fail to install or boot because of unbalanced memory distribution
across the nodes.
• The PowerEdge 6850 service console displays the following message:
Can't boot system as genuine NUMA.
• If a USB optical drive or an iDRAC virtual CD drive is connected to an
ESX/ESXi host after the system completes boot, the device may not be
available to the VMs.
• The contents of the PowerEdge RAID Controller (PERC) or Cost-
Effective RAID Controller (CERC) cache are not flushed to the disk
during a graceful shutdown of ESX/ESXi 4.0.
• Internet SCSI (iSCSI) storage volumes configured with ESX/ESXi may be
lost when the active storage controller fails and failover occurs.
• The PERC 6/i Integrated device name is displayed incorrectly as
MegaRAID SAS1078R .
• VMware vSphere Server or VMware vSphere Client displays the
USB storage controller on an ESX/ESXi system as
No Name provided
vmhba#
.
• VMware vSphere Server or VMware vSphere Client displays the Service
Tag of a blade enclosure instead of the Service Tag of the blade itself.
• When you run the lspci command on the service console, the PERC 4/DC
device name is displayed incorrectly as
MegaRAID .
• The ESX service console displays error messages related to the Small
Computer System Interface (SCSI) on some PowerEdge systems.
• The DRAC 4 adapter is displayed as
unknown in the service console of
ESX.