VMware VirtualCenter 2.0.2 Update 5 Release Notes

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

VMware VirtualCenter 2.0.2 Update 5| 08 August 2008 | Build 104182

Last Document Update: 08 August 2008

What's in the Release Notes

VirtualCenter 2.0.2 Update 5 release includes all the fixes from the VirtualCenter 2.0.2 Update 4 release and also includes fixes for certain security, virtual machine management, installation, and globalization issues. The globalization fixes are primarily for the Japanese version of the VirtualCenter Server.

This maintenance release includes changes to the VirtualCenter Server and the VI Client software. If you upgrade a VirtualCenter Server host using this maintenance release, you must also upgrade all VI Client installations. You can upgrade the VI Client by downloading the software from an upgraded VirtualCenter Server host, or by selecting VI Client from the VirtualCenter installation startup page.

These release notes cover the following topics:

Resolved Issues

VirtualCenter 2.0.2 Update 5 resolves a variety of issues and includes several improvements:

Security Issues

Note: These vulnerabilities can be exploited remotely only if the attacker has access to the service console network. Security best practices provided by VMware recommend that the service console be isolated from the virtual machine network. For more information on VMware security best practices, refer http://www.vmware.com/resources/techresources/726.

  • VirtualCenter Server Users Without the Modify Permission Privilege Can No Longer View User Name Details of Other System Users
    Starting with this VirtualCenter Server release, only users with the Modify Permission privilege can view details of other system users. When users with read-only or similar roles attempt to assign permissions to other system users, user name details of other system users are not displayed, instead, a message similar to the following appears:
    Permissions to perform this operation was denied.
    The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2008-3514 to this issue.

Virtual Machine Management Issues

  • e1000 Is the Default Network Adapter Driver for Windows Vista Ultimate 32-Bit Guest Operating Systems
    Starting with this release, the Windows Vista Ultimate 32-bit guest operating systems correctly detects the e1000 driver as the default network adapter driver, instead of the vlance driver.
  • Multiple Virtual Machines Can Be Scheduled to Power On Simultaneously
    This release fixes an issue where multiple tasks that are scheduled to power on virtual machines at the same time might result in one of the following:
    • The scheduled tasks might fail, with log entries similar to the following in the vpxd.log file:
      [2008-02-25 03:35:04.185 'App' 6708 verbose] [VpxdMoEventManager] Event[12597]: Task <virtualmachine _name>_PowerON on <virtualmachine _name> in Data Center failed: The request refers to an unexpected or unknown type.
    • The VirtualCenter Server might stop responding, with log entries similar to the following in the vpxd.log file:
      Exception: Not reached!
      [2008-02-26 03:35:03.260 'App' 4848 error] Backtrace:
      backtrace[00] eip 0x016dc006 Ordinal788
      backtrace[01] eip 0x0167248a Ordinal400
  • VirtualCenter Server Accepts Suffix Less Domain Entries When Updating the DNS Configuration of an ESX Server Host
    This release fixes an issue where, when updating the DNS configuration of an ESX Server host, the VirtualCenter Server fails to accept valid host domain names that do not have suffixes, and displays an error message similar to the following:
    The Domain name is not in the correct format
  • Viewing the Event Tab Page No Longer Causes the Japanese Version of VirtualCenter Server to Stop Responding
    This release fixes an issue where, if an event that writes multi-byte characters to the ARG_DATA column of VPX_EVENT_ARG database table, such as accessing the console of a virtual machine, is followed by viewing the Event tab page, the Japanese version of the VirtualCenter Server might stop responding. Entries similar to the following are logged in the vpxd.log file:
    [2008-03-05 17:12:18.302 'App' 5012 error] An unrecoverable problem has occurred, stopping the VMware VirtualCenter service. Check database connectivity before restarting. Error: Error[VdbODBCError] (-1) ODBC error: () -
    [2008-03-05 17:12:18.302 'App' 5012 verbose] Backtrace:

Installation Issues

  • VirtualCenter Server No Longer Fails to Start When Japanese Version of VirtualCenter 2.0.2 Update 2 is Upgraded
    The VirtualCenter Server might fail to start when the Japanese version of VirtualCenter 2.0.2 Update 2 is upgraded to VirtualCenter 2.0.2 Update 3, or VirtualCenter 2.0.2 Update 4, with entries similar to the following in the vpxd.log log file:
    [2008-05-07 15:56:59.953 'App' 5840 error] [VpxdVdb] Database version value
    'VirtualCenter Database 2.0.2u1' is incompatible with this release of VirtualCenter.
    [2008-05-07 15:56:59.953 'App' 5840 error] Failed to initialize VMware
    VirtualCenter. Shutting down...

    This release fixes the issue. The VirtualCenter Server is capable of starting, when the Japanese version of VirtualCenter 2.0.2 Update 2 is upgraded to VirtualCenter 2.0.2 Update 5.

Known Issues

Please refer the known issues associated with the previous releases. Except for the issues listed in the Resolved Issues section of these release notes, and the issues listed in this section, all known issues are the same as with previous releases. For more information, refer VirtualCenter 2.0.2 Release Notes and VirtualCenter 2.0.2 Update 3 Release Notes.

The following is a recently identified known issue:

  • VirtualCenter Server Might Export Incomplete Performance Chart Data
    A performance chart exported using the Export Performance wizard might not contain data for the specified start and end dates.
    Workaround: In the Export Performance wizard, enter a From date that is earlier than required, and a To date that is later than required.

Before Installing VirtualCenter 2.0.2 Update 5

Back up the VirtualCenter database before you install this maintenance release.

Before you begin the installation process, complete the following preinstallation tasks relevant to your Virtual Infrastructure configuration:

Managed ESX Server 3.0.x Preinstallation Tasks

Before upgrading VirtualCenter Server, all ESX Server 3.0.1 hosts must have patch ESX-1002083, and all ESX Server 3.0.2 hosts must have patch ESX-1002088. Without these patches, the required VirtualCenter Agent update on a host might fail, as the hosts might appear in the disconnected state. See KB 1002083 and KB 1002088 to download the patches, and KB 4478241 for more background on this issue.

Oracle Database Server Preinstallation Tasks
The schema used for managing the VirtualCenter objects requires execute privileges on DBMS_LOCK built in package. Prior to installing the upgrade on an existing system, you (or your Oracle DBA) must log in to the Oracle Database server as the sysdba and grant the privilege, as follows:

sqlplus system/<password>@<systemname> as sysdba
grant execute on dbms_lock to vpxadmin;

Note that the @<systemname> is relevant for a remote database host connection only. For example, assuming a database instance installed on the same host as the VirtualCenter Server system, the session might look as follows:

C:\oracle\product\10.2.0\10gR2_Home\BIN>sqlplus system/techpubs as sysdba
SQL*Plus: Release - Production on Fri Jan 5 10:01:51 2007
Copyright (c) 1982, 2005, Oracle. All rights reserved.

Connected to:
Oracle Database 10g Enterprise Edition Release - Production
With the Partitioning, OLAP and Data Mining options

SQL> grant execute on dbms_lock to vpxadmin;

Grant succeeded.

SQL> exit
Disconnected from Oracle Database 10g Enterprise Edition Release - Production
With the Partitioning, OLAP and Data Mining options


For a fresh install of VirtualCenter on an existing Oracle Database server, you must create the schema and grant it the appropriate privileges prior to VirtualCenter installation. Here's an example of a SQL*Plus schema-creation session for an Oracle Database Server 10gR2 instance, from a Windows console:

sqlplus system/<password>[@<systemname>] as sysdba



Microsoft SQL Server Preinstallation Tasks
If your current VirtualCenter installation is configured to use an ODBC System Data Source Name (DSN) that points to the master database, perform the following tasks:
  1. Create a new database for the VirtualCenter Server.
  2. Stop the VirtualCenter Server service.
  3. Migrate all VirtualCenter-related data from the master database to the new database. Database objects associated with a VirtualCenter installation start with VPX. The data migration be performed by a qualified DBA.
  4. Modify the ODBC System DSN used by your VirtualCenter installation to point to the new database.

For a fresh install of VirtualCenter, perform the following tasks:

  1. Create a new database for the VirtualCenter Server.
  2. Create an ODBC System DSN that points to this database.

For information on using SQL Server 2005 as a VirtualCenter Server database, see KB 6565318.

Installing VirtualCenter 2.0.2 Update 5

VirtualCenter software maintenance releases comprise a complete software installation (rather than being supplemental software or patches). As with a fresh install, the VirtualCenter installation program examines the local system, identifies any existing VirtualCenter installation, and guides you through the installation (or upgrade) process.

Note: If VirtualCenter components are already installed on the host machine, the installation program prompts for confirmation that you want to upgrade.

  1. Back up your VirtualCenter database (as recommended above).
  2. Download the software installation file from http://www.vmware.com/download/vi/.
  3. Stop the VirtualCenter Server service.
  4. Use autorun.exe to start the installation. Select VirtualCenter Management Server from the VMware VirtualCenter Installer startup page.
  5. Select Yes to upgrade an existing Installation.
  6. Note: If you are using Microsoft SQL Server as your database server, using the master database for VirtualCenter Server tables is not a supported configuration. If your previous VirtualCenter Server installation was configured to use the master database instead of a specific database created for VirtualCenter Server, a warning message is displayed stating that your current configuration is not supported and that it has to be manually corrected. This warning message is displayed in a GUI-based installation only.

  7. Step through the VirtualCenter Installation wizard, which guides you through several configuration details, including identifying your database instance. You will need to select your existing VirtualCenter database and enter the VirtualCenter database user name and password.
  8. After upgrading the VirtualCenter Server, you must also upgrade all Windows host systems to the upgraded VI Client software. Use the autorun.exe again to start the installer but select Virtual Infrastructure Client from the VMware VirtualCenter Installer startup page.

Note: If the existing installation of the VirtualCenter service fails to shut down gracefully by releasing all the system resources, the upgraded installation of the VirtualCenter service will be prevented from starting. In this case, you must reboot the VirtualCenter Server machine.

For complete information about installing or upgrading VirtualCenter, see the Installation and Upgrade Guide.

Installing Language Packs on the ESX Server Host

If you want German or Japanese language support when using VI Web Access or the VI Client with your ESX Server host, you must install language packs.

To install language packs:

  1. Locate the language pack ZIP file in the langpack directory on the ESX Server installation CD, or download the language pack ZIP file from http://www.vmware.com. The file has the name VMware-esxlangpack-2.0.2-build#.zip.
  2. Extract the contents of the ZIP file into a temporary directory.
  3. Copy the files from the ESX-LangPack/hostd/ directory to the hostd installation directory on your ESX Server host (usually usr/lib/vmware/hostd/).

    cp -pr ESX-LangPack/hostd/locale /usr/lib/vmware/hostd

  4. Copy the files from the ESX-LangPack/webAccess/ directory to the VI Web Access installation directory on your ESX Server host (usually /usr/lib/vmware/webAccess/tomcat/apache-tomcat-5.5.17/webapps/).

    cp -pr ESX-LangPack/webAccess/webapps/ui /usr/lib/vmware/webAccess/tomcat/apache-tomcat-5.5.17/webapps/
    cp -pr ESX-LangPack/webAccess/webapps/WEB-INF /usr/lib/vmware/webAccess/tomcat/apache-tomcat-5.5.17/webapps/ui/
    cp -pr ESX-LangPack/docroot /var/lib/vmware/hostd/

  5. Edit the /etc/vmware/hostd/config.xml file to enable the correct default language:

    For German, add the following lines to the config.xml file:


    For Japanese, add the following lines to the config.xml file:


  6. Type the following commands to restart VI Web Access and host agent services:

    service mgmt-vmware restart
    service vmware-webAccess restart