VMware
[an error occurred while processing this directive]

VMware VirtualCenter 1.2 Release Notes: Resolved Issues

This section contains a partial list of resolved issues. Only items that were mentioned as Known Issues in previous VirtualCenter release notes or were of particular interest are included.

The following issue is resolved in VirtualCenter 1.2 patch 1.

The following list highlights the most significant issues resolved in VirtualCenter 1.2.

A more complete list of issues resolved in VirtualCenter 1.2, is organized by feature area below:

For a list of resolved issues for previous releases of VirtualCenter, refer to the following links:

 

 Migration and VMotion
Customized RHAS3 virtual machines might fail to obtain an IP address through DHCP
The deployed virtual machine might fail to obtain an IP address with an error like this:
Determining IP information for eth0 .. failed; no link present. Check cable?"
Perform an ifup eth0 to check for this error.
To correct this, upgrade to VirtualCenter 1.2 or later.
An SMP virtual machine migrated to a GSX Server host fails to power on
GSX Server hosts do not support 2 VCPU configurations. If the virtual machine has an SMP configuration and two virtual CPUs, power on fails on the GSX Server host with a message Operation failed to change the virtual machine to the expected power state
To correct this, upgrade to VirtualCenter 1.2 or later.
Migrating with VMotion between almost identical processors fails
If you are having problems migrating between two processors which you think are pretty closely related, it is possible that a non-essential mis-match is present.
To correct this, upgrade to VirtualCenter 1.2 or later. See KB article 1387 for additional information.

 

 Templates, Clones, and Customization
Deploying or Cloning to a SAN with SCSI reservations might crash the VirtualCenter host agent
Deploying a template or cloning a virtual machine may fail due to SCSI reservation conflicts on the LUN.
To correct this, upgrade to VirtualCenter 1.2 or later and ESX Server 2.5 or later. See KB article 1388 for additional information.
Cloning a large disk may seem extremely slow
Cloning a large disk may take an excessive amount of time to complete.
Sharing a VMFS volume between ESX Server 2.0.1 and ESX Server 2.1.0 hosts slows down all SAN related tasks for all servers on a shared LUN. This include migration and migration with VMotion.
To correct this, upgrade to ESX Server 2.1.0 or later. See KB article 1391 for additional information.
Cloning using same default name stops incrementing after 11 clones
When multiple clones are created using a default name, after the 11th clone, a naming error stops any additional clones from being made. VirtualCenter issues an error Another virtual machine with the given name already exists.
To correct this, upgrade to VirtualCenter 1.2 or later. See KB article 1394 for additional information.

 

 VirtualCenter Client
VirtualCenter users cannot access client log file
For VirtualCenter the client log file is stored in C:\Program Files\VMware\VMWare VirtualCenter\Client.log. Typical users do not have access privileges to this directory. Because the log file is created with write permission, you need to also have write permission for the directory where the file is placed.
To correct this, upgrade to VirtualCenter 1.2 or later. See KB article 1469 for additional information.
Virtual machine fails when viewing in Console
When viewing ESX Server 2.0.1 created virtual machines in either the GSX Server 3.x Console or the VirtualCenter 1.1 Console, the virtual machine might fail.
To correct this, upgrade to VirtualCenter 1.2 or later. See KB article 1399 for additional information.
Adding a host managed by another VirtualCenter server leaves the host in an added but disconnected state
If you are adding a host from one VirtualCenter server at the same time that it is being managed by another VirtualCenter server, the Add Host process incorrectly leaves the host in an added but disconnected state while leaving the Add Host dialog open.
To correct this, upgrade to VirtualCenter 1.2 or later. See KB article 1407 for additional information.
VirtualCenter client pops to the foreground
When the Performance tab is updated, VirtualCenter client forces its display to the top of the screen.
To correct this, upgrade to VirtualCenter 1.2 or later. See KB article 1408 for additional information.

 

 Performance, Alarms and Events
VirtualCenter service seems unresponsive or slow to respond
If any of the hosts under VirtualCenter management is heavily loaded or has a very large number of virtual machines (powered on or not), then VirtualCenter may seem unresponsive.
To correct this, upgrade to VirtualCenter 1.2 or later.
Memory and handle leak in scalability environment
For a large environments with over 500 virtual machines if the VirtualCenter Web service is being used, it is recommended that you turn off all performance collectors.
To correct this, upgrade to VirtualCenter 1.2 or later then turn off the performance collectors. See KB article 1398 for additional information.

 

 Creating and Editing Virtual Machines
Cannot choose two CPUs when creating an SMP virtual machine
When creating a virtual machine on an SMP enabled ESX Server host, the option to select two CPUs is not available.
To correct this, upgrade to VirtualCenter 1.2 or later.
Cannot select the location to add a virtual disk and do not receive error if add new disk fails
When adding a new virtual disk to an existing virtual machine, only a default location, as determined by VirtualCenter is available.
If the default VMFS volume does not have sufficient disk space, the new virtual disk is not created.
To correct this, upgrade to VirtualCenter 1.2 or later. See KB article 1402 for additional information.
Changed affinity setting does not change in virtual machine
Changing the affinity through the virtual machine Properties dialog, Resources tab, Scheduling Affinity option did not update the affinity settings in the .vmx file for the virtual machine.
To correct this, upgrade to VirtualCenter 1.2 or later.

 

 Permissions and Roles
Using "Delete all User account" while "customize" cloning Windows 2003 seems to violate the existing structure of User/Group assignments with Windows 2003
The "delete user account" option is enabled when customizing Windows 2003 virtual machines and should not be.
To correct this, upgrade to VirtualCenter 1.2 or later.
Displaying a large active directory domain may take several minutes
Listing all the members of a large active directory domain might take several minutes.
To correct this, upgrade to VirtualCenter 1.2 or later. See KB article 1404 for additional information.
User with read-only access can cancel tasks
Users who are assigned the Read-Only role may be able to cancel tasks such as virtual machine cloning, template creation, or template deployment.
To resolve the issue, upgrade to VirtualCenter 1.2.

 

Issues Resolved in VirtualCenter Version 1.1.1
The following is a partial list of issues that are resolved in release version 1.1.1.

Upgrading the VirtualCenter database from 1.0.1
The following two issues have been resolved.

  • Upgrading from VirtualCenter version 1.0.1 to version 1.1 takes a long time if you have a large database.
  • Cancelling the installation in the middle of an upgrade results in an inconsistent database state that cannot be used with either VirtualCenter 1.0.x or 1.1.
VirtualCenter 1.1.1 substantially reduces the time required to upgrade the database and allows you to cancel and resume an upgrade at any point during the installation process without impacting database consistency.
To correct this, upgrade to VirtualCenter 1.1.1 or later.
Remember: backup your VirtualCenter database prior to any product upgrade.

VMotion fails when creating a new unique identifier (UUID)
Attempting to migrate with VMotion virtual machines to an IBM x445 server running ESX Server 2.1.0 results in an error. VirtualCenter requires a user response about whether to generate a new UUID or keep the existing UUID at the destination host. Since prompted questions cannot be answered during migration with VMotion, the migration with VMotion fails.
To correct this, upgrade to VirtualCenter 1.1.1 or later.

Deleting then adding a virtual disk to the same virtual machine fails
When you delete a virtual disk from a virtual machine on an ESX Server 2.0.1 host, then you attempt to add another disk to the virtual machine, adding the disk fails with a duplicate name error.
To correct this, upgrade to VirtualCenter 1.1.1 or later.

Cannot create a second SCSI controller through VirtualCenter
When adding a second SCSI disk, if you selected 1:0 as the SCSI ID, VirtualCenter resets the address to 0:2 and does not create the second virtual SCSI controller.
To correct this, upgrade to VirtualCenter 1.1.1 or later.

The virtual machine Properties dialog is blank
VirtualCenter users with Virtual Machine Administrator roles are not able to view or edit the properties of virtual machines. The Properties dialog display was blank.
To correct this, upgrade to VirtualCenter 1.1.1 or later.

Reducing Performance intervals may cause VirtualCenter server failure
When you select File > VMware VirtualCenter Settings > Performance tab, you can modify, create or remove interval types. VirtualCenter fails when you remove an interval and then add an interval with the same sampling frequency, for example 5 minutes, but fewer total samples collected,for example 150 rather than 300.
To correct this, upgrade to VirtualCenter 1.1.1 or later.

Adding a disk to a virtual machine puts the disk file in a random location
When adding a disk for a virtual machine on an ESX Server, you could not select the datastore. VirtualCenter decided where to place the virtual disk files. This does not apply to virtual machines on GSX Servers because GSX Servers only have one datastore.
To correct this, upgrade to VirtualCenter 1.1.1 or later.

Installation fails during database phase
The VirtualCenter server requires that the system service for VMware Workstation is started. The system service Workstation executable name is: lanmanworkstation.
To correct this, upgrade to VirtualCenter 1.1.1 or later.

Issues Resolved in VirtualCenter Version 1.1
The following is a partial list of issues that are resolved in release version 1.1.

VirtualCenter installer produces registry errors during installation
During installation of the VirtualCenter Server component, a Registry Editor error might appear: Cannot import xxx.reg: Error accessing the registry.
To correct this, upgrade to VirtualCenter 1.1 or later.

Migration looks complete to ESX Server, but fails at power on
ESX Server believes a virtual machine has been moved, but the virtual machine fails to power on at the new host.
To correct this, upgrade to VirtualCenter version 1.1 or later.

Clone and migrate limitation for virtual machines with more than eight virtual disks
Some operations on virtual machines with more than eight virtual disks are not supported. The unsupported operations are those that need to copy the disk, this includes cloning, migration to a different datastore, and creating templates.
To correct this, upgrade to VirtualCenter version 1.1 or later.

Browse button not functioning when adding an existing disk to a virtual machine
When you create a virtual machine using an existing disk or add an existing disk to an existing virtual machine, the browse button is not functioning.
Browse function for changing a virtual machine points to an image file, floppy image or iso image, to a physical drive, floppy disk or CD-ROM drive, does not work.
To correct this, upgrade to VirtualCenter version 1.1 or later.

VirtualCenter server fails to start after server hostname changed
If you are running your VirtualCenter server in a virtual machine and you change the host name assigned to that virtual machine, upon reboot of the host virtual machine, VirtualCenter may not restart.
To correct this, upgrade to VirtualCenter version 1.1 or later.

Changing NIC adapter type is not accepted
Changes to the NIC adapter type through the virtual machine Properties dialog are not always applied to the virtual machine.
To correct this, upgrade to VirtualCenter version 1.1 or later.

Templates on a VMFS volume not accessible to the destination host cannot be deployed to that host
Templates stored on a VMFS volume can only be deployed to hosts that have access to that VMFS volume.
To correct this, upgrade to VirtualCenter version 1.1 or later.

VirtualCenter Server must be on same side of firewall as monitored ESX Servers 2.0.1 or older
The VirtualCenter Server connects to the VirtualCenter Agent on the ESX Server for management purposes. For certain operations, such as, installing the VirtualCenter-enabled Agent, deploying a template, etc., the VirtualCenter Agent connects back to the VirtualCenter Server through a random port number. A firewall present between the VirtualCenter Server and the VirtualCenter Agent may block these connections, thereby preventing the VirtualCenter from managing the host.
This restriction does not apply to the VirtualCenter Client.
To correct this, upgrade to ESX Server version 2.1.1 or later.

Cannot concurrently deploy multiple virtual machines from the same SAN-based template
When you try to deploy new virtual machines to two different hosts, only the virtual machine specified first is created.
To correct this, upgrade to VirtualCenter version 1.1 or later.

Cannot select the location when cloning a template
The Clone a Template wizard displays a screen to select where to store the new template, but it is dimmed and not accessible.
The screen indicates where the new template is going to be stored. The screen is for information only.
To correct this, upgrade to VirtualCenter version 1.1 or later.

Cannot enter blank password for the Domain Administrator during customization
When using the Guest Customization wizard you specify the domain the new virtual machine is to join. A password is required in the wizard. The wizard does not accept a blank password or a password with spaces only.
To correct this, upgrade to VirtualCenter version 1.1 or later.

IBM x445 is not listed as a Known Manufacturer or Model
VirtualCenter finds but might not identify an IBM x445 by manufacturer and model number.
To correct this, upgrade to VirtualCenter version 1.1 or later.

Issues Resolved in VirtualCenter Version 1.0.1
The following is a partial list of issues that are resolved in release version 1.0.1.

Clustering not allowed for various clustering products
VirtualCenter Management Server does not allow clustering using VCS, MSCS, Legato AAM, or any other clustering product.
To correct this, upgrade to VirtualCenter version 1.0.1 or later.

Manipulating large templates times out
When cloning or loading large templates, VirtualCenter times out.
To correct this, upgrade to VirtualCenter version 1.0.1 or later.

VMotion creates false CPU mismatch error
When attempting a VMotion, a warning displays indicating there has been a CPU mismatch, when there is no such mismatch.
To correct this, upgrade to VirtualCenter version 1.0.1 or later.

Permissions not allowed to nested domain administrators
VirtualCenter does not grant access privileges to any Domain Administrator users or groups located in nested Domain Administrator tiers.
To correct this, upgrade to VirtualCenter version 1.0.1 or later.

Permissions broken on VirtualCenter server machine
When the VirtualCenter management server machine name is changed, Windows might not startup the VirtualCenter management server correctly. This is due to a possible mismatch in user names and passwords.
To correct this, upgrade to VirtualCenter version 1.0.1 or later.

IBM NUMA machines experiencing migration problem
Migration with VMotion might fail when the source or destination host is an IBM numa machine (x440, x445)
To correct this, upgrade to VirtualCenter version 1.0.1 or later.

SCSI driver conflict when booting a Windows virtual machine
In VirtualCenter when there is a lot of background Vmotion activity, an error might occur when booting a Windows virtual machine.
To correct this, upgrade to VirtualCenter version 1.0.1 or later.