Release Notes

4 Release Notes
ESXi reports an incorrect MAC address for PowerEdge M-Series modular
systems enabled with FlexAddress.
The network connection to one of the 10G ports may drop.
ESXi fails to reboot from the OpenManage BIOS setup page.
Error messages related to SFCB are displayed on ESX Service Console.
System hangs during reboot when ESX is deployed through PXE
environment.
Symbolic link warning messages are displayed on ESX service console.
If you make licensing changes using vSphere Client and then reboot ESXi,
the changes are lost.
ESX 4.x stops responding with a Purple Screen on the Intel Xeon 3400
series processor-based systems.
ESX 4.x fails to boot and may drop into the recovery shell when you
replace the storage controller or import foreign configuration.
ESX installation on a Dell PowerEdge R815 system stops responding.
iDRAC vKVM input devices fail to function on Dell PowerEdge R815
systems.
VMware VMotion without Enhanced VMotion Compatibility (EVC)
enabled fails on AMD Opteron 61xx and 41xx series processors.
ESX has performance issues because of interrupt request (IRQ) sharing.
The Windows Server 2008 operating system cannot be automatically pre-
activated on VMs.
One or more uplink adapters (physical network adapter) may stop
functioning on heavy network stress.
ESX 4.0 Update 1 fails to start after the installation of QLogic CNA
drivers.
The target name of iSCSI LUNs may not be displayed in VMware vSphere
Server/VI Client.
Incorrect devices are classified under the Processor section in the Hardware
Status tab of the VMware vSphere Server.
RAID 10 virtual disks are displayed as RAID 1 in VMware vSphere Server/
VI Client.
In Critical Array, the sensor is not asserted in VMware vSphere Server/ VI
Client.