VMware ESX Server 3.0.1 and VirtualCenter 2.0.1 RC Release Notes

What's in the Release Notes

The release notes cover the following topics:

• What's New
• Before You Begin
• Known Issues for Virtual Infrastructure 3.0.1
• Known Issues for Virtual Infrastructure 3.0
• Resolved Issues
• Installation Notes for This Release
• Upgrading or Migrating to VMware Infrastructure 3

What's new

• Support for selected 64-bit guest operating systems.
• Support for servers based on the AMD 2000/8000 series processors and Intel Xeon 7100 (codename Tulsa) series of processors.
• A self-certification program for iSCSI arrays.
• Support for iSCSI arrays such as EqualLogic PS300 and NetApp FAS3000.
• Addition of German and Japanese product versions.
• Critical bug fixes related to ESX Server 3.0 and VirtualCenter 2.0.
• Experimental support for iSCSI 4050/4052 HBA from Qlogic.
• Improved upgrade support from Virtual Infrastructure 2 to VMware Infrastructure 3. This is described in the Installation and Upgrade Guide.
• Support for Symmetric Multiprocessing (SMP) on Windows XP virtual machines.

Before You Begin

ESX Server, VirtualCenter, and GSX Server Compatibility

This release version requires or functions with the listed version of the following servers:

Known Issues for Virtual Infrastructure 3.0.1

Performance not Confirmed for Virtual Machines Hosted on a Linux NAS Appliance Using NFS

Using a Linux NAS server as a storage solution for hosting virtual machines may provide poor performance. No problems should occur with this configuration if the Linux NAS appliance being used has sufficient processing power, memory space, and network connectivity.

ESX 3.0 Hosts Become Unresponsive While Multiple Clone, Migrate, or Power Operations are Executed

ESX Server 3.0 hosts enter a "Not responding state" if multiple clone, migrate, or power operations are execute from VirtualCenter. During this unresponsive time, other operations fail with a misleading "command timed out" message or other network error. After the clone, migrate, or power operations complete, and the ESX Server becomes responsive, updated information reveals that the operations were successful.

Solaris 10 Guests with SMP May Hang When Powering On

Solaris virtual machines with virtual symmetric multiprocessing enabled may fail to finish the process of powering on due to problems with TSC calibration. This affects 32-bit and 64-bit versions of Solaris 10, Solaris 10 Update 1, and Solaris 10 Update 2. If this failure occurs, power off the virtual machine, and then power it back on again. This should resolve the problem with no data loss.

Taking More Than one Snapshot of a Suspended Virtual Machine Produces a Fault

If you suspend a virtual machine and then take two successive snapshots, the second snapshot operation will fail with the error Failure due to a malformed request to the server. This behavior is expected and is not problematic. Not taking additional snapshots is acceptable because suspended virtual machines do not change, so taking subsequent snapshots would involve overwriting existing snapshots with identical data.

Disabling Software iSCSI Requires Host Reboot

Disabling software iSCSI by unchecking the Enable checkbox from the General Properties dialog does not disable software iSCSI. To complete the process of disabling iSCSI, the host must be rebooted.

Misleading Time-Out Errors Occur When Rescanning iSCSI Storage Adapters

When rescanning a software iSCSI storage adapter for new storage devices and new VMFS volumes, an error message stating, "Timed out waiting for the server response." may appear. Despite the error, the rescan will complete successfully. Click OK to dismiss error message.

VI Client Cancel Button Does not Cancel Log Loading

In the VI Client, clicking Show All begins the process of displaying all log information. While the client is in the process of displaying the log information, clicking the Cancel button should stop this process, but it does not. While clicking Cancel should stop this process, the ongoing process of updating log information does not affect other VI Client functionality.

MSCS Requires 2 GB Fibre Channel Drivers

MSCS clustering on ESX Servers requires 2 GB Fibre Channel drivers, but ESX Server 3.0.1 is installed with 4 GB Fibre Channel drivers. To use MSCS with ESX Server, install the 2 GB Fibre Channel drivers, which are available on the VMware Infrastructure CD.

To determine which Fibre Channel drivers are installed

1. Determine which drivers are installed using the command vmkload_mod -l.
2. Review the command output. 4 GB drivers are indicated by lpfcdd_732, qla2200_707, or qla2300_707. If these are present, modify your drivers.

1. Uninstall 4 GB drivers using the command rpm -e 4GB_driver_name
   For example, rpm -e VMware-esx-drivers-scsi-qla2200-v7.07-7.7.4.1vmw-29822
   Note, the actual driver name varies based on Fibre Channel manufacturer and ESX Server build number.
2. Install 2 GB drivers using the command rpm -Uvh 2GB_driver_name
   For example, rpm -Uvh VMware-esx-drivers-scsi-qla2300-v7xx-7.4.0.1vmw-29822.i386.rpm
   Note, the actual driver name varies based on Fibre Channel manufacturer and ESX Server build number.
3. In the file /etc/vmware/esx.conf, change:
   • lpfcdd_732 to lpfcdd_7xx
   • qla2200_707 to qla200_7xx
   • qla2300_707 to qla2300_7xx
4. Issue the command esxcfg-boot -b
5. Reboot the system

You may want to repeat the process of checking which drivers are installed to ensure that all instances of 4 GB Fibre Channel drivers were replaced with 2 GB Fiber Channel drivers.

VMware HA May Incorrectly Handle Temporary Host Network Isolation

In VMware HA, host network isolation detection occurs within 15 seconds of host isolation. After a failure is detected, all virtual machines are failed over to other hosts. If the network connection is restored before 12 seconds have elapsed, other hosts in the cluster do not treat this as a host failure, and the virtual machines remain powered on on the original host. After 12 seconds, the clustering service on the isolated host shuts down and the virtual machines are powered off. If the network connection is restored shortly after 12 seconds, the virtual machines are not started on other hosts because the host is not considered to be isolated. As a result, if the network connection is restored shortly after 12 seconds after the host has lost connectivity, the virtual machines are powered off but not failed over.

New Hosts May not Automatically Use Expected License Servers

Hosts added to VirtualCenter should automatically use the license server being used by the VirtualCenter server to which they have just been added. This does not occur. To address this issue, manually configure the license server for the host.

To configure the license server for a host

1. In License Sources, click the Edit hyperlink.
2. Select Use License Server (Recommended).
3. Enter localhost.

Upgrading from ESX Server 3.0 to ESX Server 3.0.1 Requires Licenses be Re-Entered

When upgrading from ESX Server 3.0 to ESX Server 3.0.1, existing licensing information for the server is deleted and the original license is released back to the license pool. Because the license information is deleted, operations such as powering a machine on fail with an error indicating the required licenses are not available. To resolve this issue, after completing the upgrade, provide the license information from the original ESX Server installation to the upgraded host.

VMFS3 Volumes May not be Correctly Created

During an ESX Server 3.0.1 scripted installation on CCISS, VMFS3 volumes may not be correctly created. To address this issue, use vmkfstools to add an entry upon reboot to /etc/vmware/vmfs3queue. This entry indicates that the VMFS volume will be formatted and created.

Upgrade Migration of a Virtual Machine may Create a Duplicate RDM

During a migration upgrade, if you migrate a virtual machine using an RDM from an ESX Server 2.x host and VMFS2 datastore to an ESX Server 3.0.1 host and VMFS3 datastore, a duplicate RDM is created on the destination datastore. The original RDM remains in place on the VMFS2 datastore. This can create issues if two or more virtual machines were sharing the same RDM. After migration, the virtual machines still share the same raw disk, but use different RDMs.

To allow two or more virtual machines to continue to share an RDM, reconfigure them to do so after migration to the ESX Server 3.0.1 host and VMFS3 datastore. Then delete the extra RDMs created during the virtual machine migrations. After you have completed the migration upgrade, you can delete the original RDM on the VMFS2 datastore if it is no longer needed by any virtual machines.

Known Issues for Virtual Infrastructure 3.0

For any known issue that has a Knowledge Base article link, use this path to access the article. Change the Knowledge Base number in the URL.

kb.vmware.com/kb/xxxx

Security Alerts for This Release

Please refer to KB 1107 for VMware product security alerts.

• Installation Issues
• Upgrade Issues
• Backup Issues
• Server Configuration Issues
• VirtualCenter, VI Client, and Web Access Issues
• Virtual Machine Management Issues
• Guest Operating System Issues
• Miscellaneous Issues

Note: Some known issues with this release are covered in the VMware Virtual Infrastructure SDK Release Notes for VMware VirtualCenter 2.0.

Note: Windows 2000 must be updated with Rollup 1 for Service Pack 4. Download this Rollup from http://www.microsoft.com/windows2000/server/evaluation/news/bulletins/rollup.mspx. Refer to http://support.microsoft.com/kb/816542/ for details. This fix is essential for VirtualCenter Server to operate correctly..

For information about third-party software and the new VMware Service Console firewall, see KB 2143. View all the Knowledge Base articles related to the ESX Server 3.0 and VirtualCenter 2.0 releases.

Installation

• Graphical Installer Might Fail to Load on IBM x445 Server with RSAII Adapter (KB 2148)

• Display Goes Blank When Installing Using Remote Interface on Intel Blade Servers (KB 2149)

• Cannot Log Onto VirtualCenter Server Using VI Client After VirtualCenter Server Upgrade or Installation (KB 2150)

• Installing ESX Server 3.0 on IBM e326 Causes Keyboard to Become Unresponsive (KB 2152)

• When Attempting to Do a BootFromSan using LPe1150, the Link Never Comes up on the HBA (KB 2288)

• ESX Server 3.0 System with More than 128 LUNs Attached Fails to Install (KB 2154)

• USB Keyboard and Mouse Are Not Usable After Installation and Reboot of VMware ESX 3.0 Server (KB 2280)

• Virtual Machines' Raw Disks Cannot be Upgraded to RDMs by the Upgrade Script (KB 2168)

Upgrade Issues

• Some Storage Applications May Require Firewall Ports be Opened (KB 2143)

• Template Upgrades Do Not Work If the Host Is Running ESX Server 2.x (KB 2189)

• Adding a Legacy Virtual Disk to a Virtual Machine Downgrades it to a Legacy Virtual Machine (KB 2137)

• Creating a Virtual Machine Using an Existing Disk from a Legacy Virtual Machine Can Result in Anomalies (KB 2134)

• Installer Crashes During RPM Transaction While Upgrading ESX Server 2.x to 3.0 (KB 2195)

• ESX Server 3.0 Does Not Properly Support Upgrading Multi-Boot Installations (KB 2199)

• Additional VI Clients Unable to Connect to an ESX Server Host During a VMFS2 to VMFS3 Upgrade (KB 2236)

• Traffic Shaping Configuration Is Lost When Migrating or Upgrading Virtual Machine From ESX Server 2.x to ESX Server 3.0 (KB 2164)

Security

• Firewall Disabled Running Service Iptables Start (KB 2160)

• Nessus Generates a Warning Indicating a VERITAS Backup Exec Security Advisory for Windows Servers (KB 2206)

• Nessus Generates a Warning for Vulnerability at Port 9 with the Ascend Router (KB 2299)

Licensing

• Some Pre-Checked Items Cannot Be Checked Back to License Pool (KB 2170)

• Uninstalling VCB Using Add/Remove Programs Hangs (KB 2141)

• Only One Virtual Machine Appears in Legato Networker IM GUI After Backing Up Multiple Virtual Machines (KB 2144)

• File-Level Backup of a Virtual Machine with an Uninitialized Disk Fails (KB 2147)

• Warning on VCB Disconnect from VirtualCenter Server (KB 2151)

• NIC Team Stops Working After ESX Server Upgrade (KB 2201)

• VMware VirtualCenter and VMware ESX Server Provide Datastore URLs with Different Formats (KB 2305)

• Intermittent VMotion/NFS/ISCSI Failures can be Caused by Duplicate IP Addresses on your Network (KB 2253)

• Using Qlogic FC-HBA I/O Stalls on EMC Symmetrix (KB 2287)

• Virtual Machines or Processes Hang When ISO Image Is Used from Service Console NFS Share (KB 2296)

• VirtualCenter and "esxcfg-vswitch - l" Show Different Number of Ports (KB 2091)

• After VMFS Upgrade, VMX File Must Be Edited to Address Condition Producing Errors on Virtual Machine Startup (KB 2237)

• NIC Stops Transmitting When Using Broadcom 5700 Rev 14 and 5701 Rev 15 for Heavy Traffic (KB 2242)

• VI Client Loses Connectivity to the ESX Server System Host After Adding a new NIC (KB 2243)

• Some Storage Applications May Require Firewall Ports be Opened (KB 2143)

• In-Place Upgrade Only for Virtual Machines with RDM Disks (KB 2204)

• MSCS Clustering Can Trigger an Unnecessary Failover to the Backup Server on the IBM FastT Series Arrays (KB 2161)

• SAN LUNs Not Visible in VirtualCenter UI but Visible in MUI (KB 2278)

• Using HP Insight Manager 7.5.1a, Storage Controller Adapters Are Not Shown (KB 2223)

• Upgrading my VMFS-2 Volume Failed Due to Insufficient Free Space (KB 2210)

• Doing Multiple vmfs Upgrades at the Same Time Just Upgrades the First One (KB 2211)

• Additional VI Clients Unable to Connect to an ESX Server Host During a VMFS2 to VMFS3 Upgrade (KB 2236)

• Cannot See the /vmimages Datastores Directory When Attempting to Mount an ISO Image on a VirtualCenter 2.0-Managed ESX Server 2.x Host (KB 2162)

• When Using Serial Ports That Are Connected to Named Pipes, Relative Paths and Locations on VMFS Cannot Be Used (KB 2192)

• Create Datastore Operation Might Fail if the Disk also Contains the ESX Server Service Console File System (KB 2240)

• No Protection Against Deleting a Disk Backing File That Is Also Used by Another Powered-Off Virtual Machine (KB 2245)

• Disabling the Qlogic PCI Device in BIOS Results in a PSOD (KB 2209)

• NFS Mounts Are Restricted to 8 by Default (KB 2239)

• Problems with Configuring qla4010 Card when ESX Server Boots from iSCSI (KB 2207)

• System Time Accounting Incorrect for Software iSCSI (KB 2208)

• Inaccessible Virtual Machines Are Named "Unknown VM" (KB 2172)

• Real-time Statistics Data Has Gaps for the Host in VirtualCenter 1.x After Being Managed by VirtualCenter 2.0 (KB 2198)

• Intermittent SSL Warnings Appear During Logoff (KB 2169)

• Server on Localized Operating System Fails to Recognize Certain Locales (KB 2178)

• After I Move a Host out of a Cluster, the VI Client Inventory Doesn't Show the Host's Virtual Machines (KB 2165)

• Error Message in VI Client Indicates That esx.conf.WRITELOCK Cannot Be Obtained (KB 2183)

• After a Host Failure, when the Host Boots Up, the HA Service Does Not Start Up and an HA Error Occurs on the Host (KB 2300)

• Browse Datastores Option of the VI Client Cannot Recognize .vmdk File Created by vmkfstools (KB 2171)

• Unable to Log Onto the VI Client (KB 2184)

• Incorrect Input Text in Configuration Wizards Can Cause Unhandled Exceptions (KB 2186)

• Export Diagnostics Option in the VI Client Might Fail to Resolve Host Names on Other Domains (KB 2187)

• VI Client Fails to Add a Host (KB 2257)

• Different Error Messages for the Same Event (KB 2174)

• In Certain Fibre Channel Environments, VMotion Does Not Succeed and the Virtual Machine Remains Running on the Source Machine (KB 2265)

• Some Virtual Machines Might Not Power on Even if Their Reservation Is Less Than the Unreserved Capacity of Their Parent Resource Pool (KB 2158)

• Taking Snapshots of Upgraded Virtual Machines in Nonpersistent Mode Is Not Allowed (KB 2175)

• Floppy and CD-ROM Settings Are Dimmed When I Switch Between Other Hardware Options (KB 2179)

• Virtual Machine Startup/Shutdown Host Settings Require an Action and Delay Be Specified (KB 2190)

• Virtual Machine Startup/Shutdown Host Settings Do Not Reflect Changes to Virtual Machine Settings (KB 2194)

• vmware-cmd Doesn't Recognize Symbolic Links to VMFS3 (KB 2122)

• Delays When Writing to a New Virtual Disk for the First Time (KB 2191)

• Incorrect Error Message when a Virtual Machine Backed Up on ESX Server 2.x is Restored to ESX Server 3.x (KB 2307)

• The Virtual Machine May Still Be Running when VmPerl::VM::stop and "vmware-cmd stop" Return (KB 2295)

• Virtual Machine Powers Off if Attempting to Connect SCSI Device in a Powered On Virtual Machine (KB 2248)

• Installing VMware Tools from Virtual Infrastructure Client Does Not Eject CD-ROM from a Solaris Guest (KB 2157)

• Failure to Connect to CD-ROM due to Incorrect Path (KB 2303)

• Re-Editing a Virtual Machine Before a Previous Edit Completes Fails (KB 2205)

• Changing the Power Options in Virtual Machine Gives an Error Message if the Virtual Machine is Powered On (KB 2251)

• Unable to Run Tools Upgrader for Autotools Installation and Upgrade (KB 2121)

• Intermittent Virtual Machine Failures with NIS-Enabled ESX Server Hosts (KB 2255)

• VMotion Fails at 90% Progress when the Virtual Machine's Parallel Port is Set to Write to an Output File (KB 2284)

• The Virtual Machine Seems to be Installing VMware Tools but the Tools Never Get Installed (KB 2277)

Guest Operating System

You can find the latest version of the Guest Operating System Installation Guide by following these links: HTML | PDF | Japanese PDF.

• Negative Numbers Sometimes Appear for Disk Sizes in SMC 2.1 on the Solaris 10 Operating Environment and Update 1 (KB 2215)

• Cloning a Windows Virtual Machine Can Fail if the Virtual Machine Has a Nonstandard BootExecute Value (KB 2246)

• Large Network Transfers Can Cause a Solaris 10 Virtual Machine's Network Connection to Hang (KB 2176)

• Solaris 10 Update 1 Virtual Machines Might Not Properly Discover and Configure the Virtual Floppy Device, Virtual Parallel Port, or Virtual Serial Port (KB 2270)

• If No DHCP Server Is Available When a Windows Virtual Machine is Customized, the Virtual Machine Might Not Be Able to Join a Domain (KB 2262)

• Solaris 10 U1 Guest Operating System Is Not Supported on EMC CLARiiON Series and Symmentrix Series Storage Arrays (KB 2289)

• Customization of a Virtual Machine on a Linux Guest Might Fail (KB 2301)

• Older Guest Operating System Exhibits Unusual Behavior (KB 2225)

• Solaris Warning "Stopped tracking Time of Day Clock" (KB 2250)

• Dell PowerEdge 6850 Hosts Running ESX Server 3.0 Need A03 BIOS to Install 64-Bit Guests (KB 2087)

• Display and Mouse Problems in Solaris 10 Virtual Machines (KB 2254)

• Excessive Network Error Messages Detected in Solaris 10 Virtual Machine (KB 2258)

• Installation of 64-Bit Red Hat Enterprise Linux, Updates 3, 5, 6, 7, and 8 SMP Kernel Occasionally Fails with Anaconda ImportError Message (KB 2260)

• Red Hat Enterprise Linux Advanced Server 3.0 64-Bit Guest Produces Error on Intel VT Host (KB 2263)

• 64-Bit Linux Guests with Computer Using More Than 4 GB of Memory Might Experience a Guest or vmware-vmx Panic (KB 2269)

• Hewlett Packard DL760 G2 Servers Issue Warnings Whenever You Load the VMkernel (KB 2145)

• VirtualCenter's Datastore Browser Does Not Display Virtual Disk Files for Virtual Machines on ESX Server 2.x Hosts (KB 2203)

• Auto-Start Is Not Run When Manually Restarting a Host in Maintenance Mode (KB 2214)

• Disconnecting or Removing a Host Deletes a Scheduled Task (KB 2180)

Resolved Issues

The following are known issues in Virtual Infrastructure 3.0, which have since been resolved.

Install Issues

• iLO2 Virtual Media on a ML570 G4 or DL570 G4 Fails (KB 2285)

• ESX Server Installer is Unable to See Disks if Both SAS and SCSI Controllers are Used (KB 2167)

• Customization Is Broken when WorkStation 5.x or VMI 1.5 Are Installed on the same Machine as VirtualCenter Server 2.x (KB 2297)

Upgrade Issues

• Cold Migrating a Virtual Machine from ESX Server 2.x to 3.0 Fails (KB 2182)

• Virtual Machines That Were Participating in Auto-Start Are no Longer Involved in Auto-Start (KB 2232)

• Legacy Templates Upgrade Fails After Upgrading Shared LUN to VMFS-3 from Another Host (KB 2235)

• Upgrade Relayout Virtual Machine Operation Fails (KB 2181)

• VirtualCenter 1.x to VirtualCenter 2.0 Database Upgrade Using Oracle 10.2.0.1 May Fail (KB 2304)

• Upgrading from VMFS-2 to VMFS-3 May Make VI Client on ESX Server Unresponsive (KB 2233)

• VMFS Volume Upgraded From VMFS-2 to VMFS-3 May Display as Read-Only After Upgrading (KB 2197)

Licensing

• VC License Server Settings May Override ESX Server Host Settings (KB 2212)

• Using "pre-command.bat" and "post-command.bat" as Described in the README for the Netbackup Integration Module for VCB Does Not Work as Expected (KB 2249)

• File-Level Backup with VCB Fails When Attempted With Six or More Virtual Disks on the Backup Proxy (KB 2185)

• Service Console Networking Stops Working When Using vmxnet_console and Upgrading From ESX Server 2.x to 3 (KB 2202)

• Eleven Connections Appear on the Database Server Even Though the User Set the Maximum Number of Database Connections to a Value Less Than Ten (KB 2302)

• Using Intel e1000 NICs With Certain PCI IDs May Cause Kernel Panic (KB 2221)

• Network Connectivity Is Lost and "WARNING: Uplink: 1925: Couldn't allocate pkt for frame copy" Appears in the Log (KB 2274)

• Configuring a Duplicate IP Address for VMotion Causes an Error (KB 2224)

• ESX Server 2.1.x and 2.0.x Do Not Provide Expected Configuration or Information for Raw Disks (KB 2133)

• A Mapped SAN LUN Added to a Virtual Machine Is Not Visible from the List (KB 2216)

• Legacy Templates Will Fail After Upgrading the Shared LUN to VMFS-3 From Another Host (KB 2235)

• Problems when Using Emulex Fibre Channel Cards in Extreme Failover Conditions (KB 2244)

• "A Specified Parameter Was not Correct" Error in the VI Client Interface When a Virtual Machine Is Powered On (KB 2173)

• Changes Made for Database Password or Maximum Number of Database Connections to be Created in VI Client Do Not Take Effect Until the VirtualCenter Service is Restarted (KB 2218)

• Cannot Power On Virtual Machine That Has two or More CPUs (KB 2159)

• Creating a Virtual Machine or Disk on Host Client Fails When You Try to Create a Virtual Machine Disk Larger Than 262GB (KB 2177)

• All Paths to a LUN Are No Longer Accessible and an Infinite Abort Loop Results (KB 2298)

• Virtual Machine Cloning and Customization Operations Fail on Virtual Machines with Two Network Adapters Connected to One Network (KB 2200)

• System PSOD:"Spin count exceeded (EventQueue, 448) - possibile deadlock" Message (KB 2306)

• Windows Virtual Machines with Latency-Sensitive I/O Workloads May Slow Down in Four-Way SMP Configurations (KB 2231)

Guest Operating System

• Remote Floppy Does Not Work in Solaris 10 Operating Environment, Update 1 (KB 2220)

• 64-Bit Red Hat Enterprise Linux 4 Hangs During Installation (KB 2229)

• Storage Drivers for the VMware LSILogic Storage Adapter Are Not Available in Windows XP (KB 2241)

• Blue Screen On Windows 2003 SP1 When Mounting Volumes (KB 2267)

• VMotion Fails to Migrate Virtual Machine When Target System Runs ESX Server Version 2.5.3 or Lower (KB 2155)

• Virtual Machine Changes to Snapshot-Consolidate Mode During Delete-All-Snapshot Operation (KB 2222)

• HA Configuration Tasks Fail and an Error Message Appears When I Configure an HA Cluster (KB 2135)

• Configuring HA Task Fails or Virtual Machine Failover Does Not Happen (KB 2259)

• Template Upgrade Fails with Error, "Name Already Exists" (KB 2196)

• Re-enabling Never Takes Effect If you Re-enable After the Active Directory "Enable Validation" Setting Is Disabled for a While (KB 2279)

Installation Notes for This Release

Upgrading or Migrating to VMware Infrastructure 3

This release supports upgrading from ESX Server 2.x and VirtualCenter 1.x to VMware Infrastructure 3, which is ESX Server 3.0 and VirtualCenter 2.0. VMware highly recommends that you review the detailed upgrade instructions and guidelines that are provided in the Installation and Upgrade Guide.