VMware VirtualCenter 2.0.2 Update 1 Release Notes
Check back frequently for additions and updates to these release notes.
VMware VirtualCenter 2.0.2 Update 1| 10/29/2007 | Build 61426
Release notes last updated on 12/21/2007 with the following changes:
- Replaced ESX-H171726-01 patch with ESX-1002083 patch in "Snapshots of Virtual Machines with Pass-Through RDM Disks Can Be Taken" under "Virtual Machine Management Issues".
Release notes updated on 10/30/2007 with the following new additions:
- Added the section Installing Language Packs on the ESX Server Host.
What's in the Release Notes
VirtualCenter 2.0.2 Update 1 release fixes several high-priority issues from earlier patch releases, and includes several enhancements and improvements. This release resolves issues associated with the VirtualCenter install and upgrade, databases, and virtual machine management. It also includes two critical security updates. This release also introduces a new user role for VMware Consolidated Backup.
This maintenance release includes changes to VirtualCenter Management Server and VI Client software. If you upgrade a VirtualCenter Server host using this maintenance release, you must also upgrade all VI Client hosts. You can upgrade the Windows client hosts by downloading the software from an upgraded VirtualCenter Server host, or by selecting VI Client from the VirtualCenter installation startup page.
The release notes cover the following topics:
The New VCB Role
This release of VirtualCenter introduces a new role, VCB, with a specific set of privileges that are required for VMware Consolidated Backup. This role must be assigned to the user at the hosts and clusters level.
Also, if you are upgrading from an earlier version of VirtualCenter, you must upgrade the VirtualCenter database to avail this new role.
Image Customization Support for 64-Bit Guest Operating Systems
This release of VirtualCenter Server provides image customization support for the following 64-bit guest operating systems:
- Microsoft Windows 2003 (Standard and Enterprise editions)
- Microsoft Windows XP Professional
New Entry Related to the VirtualCenter Server Installation in the Windows Application Log
In this release, when you start the VirtualCenter Server, a new entry is logged in the Windows application log. This entry indicates the path to the logs directory, which contains diagnostic information. Similar to earlier releases, in this release, the build number of the VirtualCenter installation is also logged in the Windows application log.
New Configuration Parameter to Enhance Supportability
This release introduces the UseSETranslator configuration parameter to enhance the supportability of VirtualCenter. Setting this parameter to true will automatically log the details of exceptions encountered while the VirtualCenter service is running. You can add this parameter to the vpxd.cfg as follows:
It is recommended that you add this parameter to enhance the supportability of the product.
Note: Restart the VirtualCenter Server after making changes to the vpxd.cfg file.
VirtualCenter 2.0.2 Update 1 (Build 61426) resolves a variety of issues and includes several improvements:
- Tomcat Server Security Update
This release of VirtualCenter Server updates the Tomcat Server package from 5.5.17 to 5.5.25, which addresses multiple security issues that existed in the earlier releases of Tomcat Server. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the names CVE-2005-2090, CVE-2006-7195, and CVE-2007-0450 to these issues.
- JRE Security Update
This release of VirtualCenter Server updates the JRE package from 1.5.0_7 to 1.5.0_12, which addresses a security issue that existed in the earlier release of JRE. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2007-3004 to this issue.
- VirtualCenter Database Upgrade Process Can Be Cancelled
In this release, the VirtualCenter database upgrade process from VirtualCenter 1.x to VirtualCenter 2.0.2 Update 1 can be canceled using the Cancel button on the wizard. In earlier releases, on clicking the Cancel button, the wizard used to disappear but the database upgrade process ran in the background.
Note: It is advisable to take a backup of the VirtualCenter database before performing the upgrade.
- Hosts with Virtual Machines Can Be Moved Across Datacenters Successfully
In earlier releases, moving of hosts with virtual machines across datacenters sometimes failed due to some database constraint violation issue, which caused the VirtualCenter Server to restart. This issue has been fixed in VirtualCenter 2.0.2 Update 1.
- Increased Character Limit for VirtualCenter Database Password
In earlier releases, VirtualCenter restricted the database password to 32 characters. In this release, this restriction is relaxed and the character limit for the database password is the one that is imposed by the type of database the VirtualCenter installation points to.
Virtual Machine Management Issues
- The vmware-vmupgrade Script Upgrades Virtual Machines Containing Dynamic Disks
Prior to this release, the vmware-vmupgrade script failed and threw an error when run on Windows virtual machines containing dynamic disks. This release fixes this issue. You must, however, power off the virtual machine before running the script.
- Suspended or Powered-Off Virtual Machines in a Cluster Can Be Reverted to a Snapshot Taken in the Powered-On State
In earlier releases, VirtualCenter Server stopped responding when a suspended or powered-off virtual machine in a cluster was reverted to a snapshot taken in the powered-on state. You had to restart the VirtualCenter Server to continue normal functioning. In this release, this issue has been resolved.
- Snapshots of Virtual Machines with Pass-Through RDM Disks Can Be Taken
Prior to this release, VirtualCenter Server did not provide an option to take snapshots of virtual machines with pass-through RDM disks on an ESX Server 3.0.1 host with the ESX-1002083 patch applied. You could, however, take snapshots of these virtual machines by directly connecting to the ESX Server host from the VI Client. In this release, VirtualCenter Server enables you to take snapshots of virtual machines with pass-through RDM disks. However, you cannot take snapshots of the virtual machines' memory.
- Non-Default Configuration Parameter Settings on the Virtual Machine Are Preserved After VMotion
In this release, all non-default configuration parameter settings, that is, any new custom configuration parameter settings that you have added to a virtual machine, will be preserved and reflected on the destination host after a VMotion operation. However, if the settings are changed in the powered-on state, you must restart the virtual machine before performing the VMotion operation so that the configuration parameter settings are preserved.
- Summary Page No Longer Displays Negative Values for the Memory Usage of a Resource Pool
In earlier releases, the Summary page displayed a negative value for Memory Usage of a resource pool under certain circumstances. This was due to an issue in the calculation of memory utilized by virtual machines sharing the resource pool. This issue is now fixed.
- Reduced Default Log Information to Improve Viewer Usability
In this release, the information or messages logged by default in the System Logs is reduced. In earlier releases, when you selected Admin>System Logs, the log also included messages related to viewing and browsing the logs. In this release, these messages have been eliminated at the default logging level. To view these messages in the log, you must configure verbose logging.
- DRS Advanced Options Set on a Cluster Can Be Deleted
In prior releases, the DRS advanced options set on a cluster could not be deleted. Although you could change the value of an option, you could not delete an option once it was created. In this release, you can delete the DRS advanced options by clearing the name/value pair in the Advanced Options (DRS) dialog box and clicking OK.
- Changing the NIC Teaming Policy Appropriately Does Not Throw an Error
In earlier releases, when you tried to set the NIC teaming policy incorrectly, an error message was displayed. Following this, without closing and reopening the vSwitch Properties dialog box, if you tried to set the NIC teaming policy appropriately, the same error message was displayed again. This issue has been rectified in this release.
- Customization Specification Manager Wizard Can Be Accessed on Clients with Operating Systems that Have a Non-Default Timezone Configuration
Prior to this release of VirtualCenter, the Customization Specification Manager wizard in the VI Client used to fail and throw an error if a non-default timezone was configured without the INDEX key in the Windows registry. In this release, this issue has been addressed and the Customization Specification Manager wizard runs successfully.
- VirtualCenter Web Access Supports Mozilla Firefox 22.214.171.124
In this release, VirtualCenter Web Access provides support for Mozilla Firefox 126.96.36.199. In earlier releases, when using Mozilla Firefox 188.8.131.52, a "browser not supported" error message was displayed. However, this did not in any way affect the functioning of VirtualCenter Web Access on Mozilla Firefox 184.108.40.206. In this release, VirtualCenter Web Access does not display any error message when connecting to the VirtualCenter Server using Mozilla Firefox 220.127.116.11.
- VirtualCenter License Source Displays the Cost Unit for the Virtual Machine License Feature
In earlier releases, the Cost column in the VirtualCenter License Source page displayed only "1/" for the virtual machine license feature. The cost unit "Virtual Machine" was missing. In this release of VirtualCenter, the cost unit is correctly displayed in the Cost column.
- Answering the Redo Log Question Dialog Box Closes Any Additional Instances of the Same Redo Log Question
Prior to this release, users had to answer every instance of the redo log question, and answering the same question multiple times would throw an error. In this release, for each hard drive in the Undoable mode, answering a single instance of the redo question dialog box closes all the other instances of the same dialog box, and users do not encounter any errors.
- VMware HA Configuration Completes Successfully for ESX Server Hosts with Uppercase Characters in the Host Name
In VirtualCenter 2.0.2, the VMware HA configuration failed and displayed an error message for ESX Server hosts that contained uppercase characters in their host name. This release fixes this issue.
- Saving a Template Having More Than 255 Characters in the Notes Field Does Not Crash VirtualCenter Server
In earlier releases, the VirtualCenter Server crashed when you attempted to save a template having more than 255 characters in the Notes field. In this release, if more than 255 characters are entered in the Notes field of a template, the VirtualCenter Server will not crash. However, the contents of the Notes field will be truncated to 255 characters.
Note: It is advisable not to enter more than 255 characters in the Notes field of a Template.
Known issues and limitations of this update include the following:
Before Installing VirtualCenter 2.0.2 Update 1
As with any upgrade on a production system you should back up the VirtualCenter database before you install this maintenance release.
This release also includes modifications to the VirtualCenter database SQL scripts (required to support the changes to the statistics roll-up). These changes are mostly transparent and occur during the installation process. However, depending on the database service that you are using, you (or your organization's DBA) must perform the preinstall tasks described in the sections that follow.
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 you begin your installation process, you must ensure that the /tmp/vmware-root directory exists on the ESX Server 3.0.x host. If the directory does not exist, the VirtualCenter agent update will fail. See KB 4478241 for complete details on this issue.
Oracle Database Server Preinstallation Tasks
sqlplus system/<password>@<systemname> as sysdba
The schema used to manage the VirtualCenter objects must be able to use Oracle's DBMS_LOCK built-in package, which means it requires execute privileges on the package. Prior to installing the upgrade on an existing system, you (or your Oracle Database administrator (DBA)) must log in to the Oracle Database server as the sysdba and grant the privilege, as follows:
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 10.2.0.1.0 - Production on Fri Jan 5 10:01:51 2007
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
With the Partitioning, OLAP and Data Mining options
SQL> grant execute on dbms_lock to vpxadmin;
Disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - 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
CREATE SMALLFILE TABLESPACE "VIRTUALCENTER"
SIZE 500M AUTOEXTEND ON NEXT 10M MAXSIZE UNLIMITED LOGGING
EXTENT MANAGEMENT LOCAL SEGMENT SPACE MANAGEMENT AUTO;
ALTER DATABASE DEFAULT TABLESPACE "VIRTUALCENTER";
CREATE USER "VPXADMIN" PROFILE "DEFAULT"
IDENTIFIED BY "*******"
DEFAULT TABLESPACE "VIRTUALCENTER"
TEMPORARY TABLESPACE "TEMP"
GRANT "CONNECT" TO "VPXADMIN";
GRANT "RESOURCE" TO "VPXADMIN";
GRANT "CREATE VIEW" TO "VPXADMIN";
GRANT "EXECUTE ON DBMS_LOCK" TO "VPXADMIN";
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:
- Create a new database for the VirtualCenter Server.
- Stop the VirtualCenter Server service.
- Migrate all VirtualCenter-related data from the master database to the new database. Database objects associated with a VirtualCenter installation start with VPX. It is advisable that the data migration be performed by a qualified database administrator (DBA).
- 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:
- Create a new database for the VirtualCenter Server.
- 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 1
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.
- Back up your VirtualCenter database (as recommended above).
- Download the software installation file from
- Stop the VirtualCenter Server service.
- Use autorun.exe to start the installation. Select VirtualCenter Management Server from the VMware VirtualCenter Installer startup page.
- Select Yes to upgrade an existing Installation.
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.
- Step through the VirtualCenter Install 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.
- 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 VirtualCenter service fails to shut down gracefully by releasing all the system resources, the upgraded installation of 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 Installing and Upgrading the VirtualCenter Product.
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:
- 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.
- Extract the contents of the ZIP file into a temporary directory.
- 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
- 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/
- 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:
- Type the following commands to restart VI Web Access and host agent services:
service mgmt-vmware restart
service vmware-webAccess restart