VMware ESX Server 3.0.1 and VirtualCenter 2.0.1 RC Documentation
Knowledge Base

VMware ESX Server 3.0.1 and VirtualCenter 2.0.1 RC Release Notes

Check back frequently for additions and updates to these release notes.

ESX Server Version 3.0.1 | 8/18/06 | Build 30353

VirtualCenter Version 2.0.1 | 8/14/06 | Build 30060

Last Document Update: 8/21/06

What's in the Release Notes

The release notes cover the following topics:

What's new

This release of VMware Infrastructure, comprised of ESX Server and VirtualCenter, is comprised of many improvements including:
  • 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:

 VirtualCenter version  ESX Server version  GSX Server version
2.0.1 2.0.1, 2.1.x, 2.5.x, 3.0, 3.0.1  
2.0 2.0.1, 2.1.x, 2.5.x, 3.0  
1.3, 1.3.1 2.0.1, 2.1, 2.1.1, 2.1.2, 2.5.x 3.1, 3.2
1.2 2.0.1, 2.1, 2.1.1, 2.1.2, 2.5.0, 2.5.1 3.1, 3.2
1.1 2.0.1, 2.1, 2.1.1 3.1
1.0.1 2.0.1, 2.1  
1.0 2.0.1  

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.
To modify installed Fibre Channel 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-
    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-
    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.


Security Alerts for This Release

Please refer to KB 1107 for VMware product security alerts.

The Known Issues are grouped as follows:

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.


Upgrade Issues



VMware Consolidated Backup (VCB) Issues Server Configuration Issues


Storage VirtualCenter, VI Client, and Web Access Issues

Virtual Machine Management Issues

Guest Operating System

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

Miscellaneous Issues

Resolved Issues

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

Install Issues

Upgrade Issues


VMware Consolidated Backup (VCB) Issues Server Configuration Issues


Storage VirtualCenter, VI Client, and Web Access Issues Virtual Machine Management Issues

Guest Operating System

Miscellaneous Issues

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.