Release Notes

32 Release Notes
Service console
becomes
inaccessible on
upgrading
to ESX 4.0 from
ESX 2.5.5.
When you follow the
upgrade path of ESX
2.5.5ESX 3.5.x
ESX 4.0, you cannot
log in to the service
console of the upgraded
system. This is due to
corruption of the
Pluggable
Authentication Module
(PAM) libraries in ESX
4.x COS when upgraded
from 2.5.x to 4.x.
For resolution, see
kb.vmware.com/kb/1013431.
ESX 4.0
For some
Ethernet network
cards, the Direct
Console User
Interface (DCUI)
displays the
Hardware Label
as N/A.
For some network cards,
the Hardware Label
field in the DCUI of
ESXi displays
N/A
instead of a valid device
description.
This issue occurs because of
the method in which ESXi
maps the device to the user
interface by checking the
output of the lspci and
smbios commands from the
system. This is a cosmetic
issue. There is no loss of
functionality.
ESXi 4.0
Upgrading from
ESXi 3.5 Update 4
to ESXi 4.0 may
fail on some
systems.
Upgrading ESXi 3.5
Update 4 to ESXi 4.0
may fail displaying the
following message on
some systems: ERROR:
Unsupported boot
disk.
The boot device
layout on the
host does not
support upgrade.
If the upgrade fails, backup
the ESXi 3.5 Update 4
configuration and the VMs
configured on that ESXi
host.
To setup the ESXi 4.0 host:
1 Perform a fresh
installation of ESXi 4.0
and restore the
configuration.
2 Add the previously
existing Virtual Machine
File System (VMFS)
datastore containing the
VMs to the ESXi 4.0 host
and then add them back
to the inventory.
ESXi 4.0
Installable
Issue Description Resolution Applies to