VMware
[an error occurred while processing this directive]

 

VMware VirtualCenter 1.3.x Release Notes: Resolved Issues

Release Notes main page | Known Issues for This Release

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.

View all the Knowledge Base articles related to the VirtualCenter 1.3 and 1.3.1 releases.

For a list of resolved issues for each 1.x release of VirtualCenter, refer to the following links:

 

Issues Resolved in VirtualCenter Version 1.3.1 patch 1
The following issue is resolved in the patch 1 release for VirtualCenter 1.3.1.

Cold Migration of a Virtual Machine Might Lead to Data Loss if a Network Failure Occurs and the Disk Files Remain on the Same Shared VMFS SAN Volume
To correct this, upgrade to VirtualCenter 1.3.1 patch 1 or later. See KB article 2070 for additional information.

 

Issues Resolved in VirtualCenter Version 1.3.1
The following issue is resolved in the maintenance release of VirtualCenter 1.3.1.

Change to collecting log files with VirtualCenter 1.3.1.
To correct this, upgrade to VirtualCenter 1.3.1 or later. See KB article 1935 for additional information.

Installation fails if password field is left blank.
To correct this, upgrade to VirtualCenter 1.3.1 or later. See KB article 1807 for additional information.

When the Connect a Host process is cancelled, it removes the disconnected host from the VirtualCenter Inventory
When corrected, then cancelling the Connect a Host process returns a disconnected host instead of removing the host from the VirtualCenter inventory.
To correct this, upgrade to VirtualCenter 1.3.1 or later. See KB article 1833 for additional information.

Memory allocation allowed unacceptable maximum size.
VirtualCenter allowed a maximum memory size greater than a virtual machine's individual maximum memory size, which is 3600 KB. Though the Deploy Wizard accepted this invalid value, the virtual machine would not power on after the deployment or cloning.
To correct this, upgrade to VirtualCenter 1.3.1 or later.

Creating RDM using VirtualCenter resulted in RDM LUN mapped to wrong location
If a host had access to more than 10 RAW LUNs, creating an RDM for a virtual machine on the host using VirtualCenter results in the RDM LUN being mapped to the wrong location. To correct this, upgrade to VirtualCenter 1.3.1 or later.

Deploy to GSX Server host failed with possible error: Failed to find the session. It may have been destroyed due to a timeout.
Situations in which this might occur include: Cloning multiple virtual machines with different disk sizes from one GSX Server(Linux or Windows) to another GSX Server(similar Linux or Windows). Deploying multiple virtual machines from templates almost at the same time to a GSX Server (Windows) host.
To correct this, upgrade to VirtualCenter 1.3.1 or later.

Web Service does not allow customization of Guest operating system through a Scheduled Task.
To correct this, upgrade to VirtualCenter 1.3.1 or later.

Console enters infinite loop when started from inventory panel virtual machine and the target machine is same as the local host.
To correct this, upgrade to VirtualCenter 1.3.1 or later.

SID Not Changed When Customized Template Deployed from VirtualCenter Running on Windows
To correct this, upgrade to VirtualCenter 1.3.1 or later. See KB article 1806 for additional information.

Past and current performance statistic data are not showing in VirtualCenter client
This may occur when there is communication problem between the VirtualCenter database and the VirtualCenter server.
To correct this, upgrade to VirtualCenter 1.3.1 or later.

Memory and handle leak for each FilteredPerfCollector
To correct this, upgrade to VirtualCenter 1.3.1 or later.

 

Issues Resolved in VirtualCenter Version 1.3
The following issue is resolved in the minor release of VirtualCenter 1.3

Confusing messages during installation when trying to determine which choice overwrites an existing VirtualCenter database.
To correct this, upgrade to VirtualCenter 1.3 or later.

VMware Registration Service constantly stops.
To correct this, upgrade to VirtualCenter 1.3 or later. See KB article 1838 for additional information.

When Migrating with VMotion to a target machine, which has a fully loaded networking switch, warning issued.
If you continue with the migration with VMotion, it is successful, but the networking for the virtual machine is disabled.
To correct this, upgrade to VirtualCenter 1.3 or later.

Migration information for a host is not available.
This occurred if invalid migration information was entered through the VirtualCenter client.
To correct this, upgrade to VirtualCenter 1.3 or later.

Virtual Machines with More Than 2 GB of Memory Might Fail if Migrated with VMotion
Needed to avoid migrations with VMotion of Virtual Machines with more than 2 GB of memory while other migration operations are in process.
To correct this, upgrade to VirtualCenter 1.3 or later. See KB article 1509 for additional information.

VirtualCenter server received the panic PANIC: MEM_ALLOC F(4300):27 and shut itself down while concurrently deploying multiple virtual machines from templates which are located on the VirtualCenter server.
To correct this, upgrade to VirtualCenter 1.3 or later.
This fix reduces the possibility of getting the error due to VirtualCenter server running out of virtual address space while doing multiple concurrent template deployments.

Virtual center always shows the vmxnet NIC device status of a virtual machine running on an ESX Server as disconnected even though the device is connected.
The Connected checkbox in VirtualCenter pre-1.3 versions is always unchecked irrespective of the device status.
To correct this, upgrade to VirtualCenter 1.3 or later. See KB article 1785 for additional information.

Receive the error "Object reference not set to an instance of an object" in Inventory panel when clicking out of a host whose Performance tab has the Show Legend option enabled.
To correct this, upgrade to VirtualCenter 1.3 or later.
Alternatively, click Show legend before selecting a new host or farm. After you have selected the new host or farm, click Hide legend. See KB article 1784 for additional information.

Receive Vmdb error -18: Null cross reference error when attempting to remove a farm.
To correct this, upgrade to VirtualCenter 1.3 or later. See KB article 1800 for additional information.

VirtualCenter Server crashes with panic -- PANIC: ASSERT F(5296):130 bugNr=41550.
To correct this, upgrade to VirtualCenter 1.3 or later.
The number of multiple paths per LUN parameter is configurable in version VirtualCenter 1.3 or later. The default value is 4. To change this value add and/or edit the stats.lun.nummultiplepath parameter in VirtualCenter server config.ini file. See KB article 1783 for additional information.

Existing scheduled tasks show inconsistent run time after daylight savings time change.
After the daylight saving time change, existing scheduled tasks which were created prior the daylight saving time change display the next run time which is one hour ahead of the start time entered. However, if we right click on the scheduled task, the scheduled start time display is correct time.
To correct this, upgrade to VirtualCenter 1.3 or later.
Note: If a designated time to perform a scheduled task is 2:00 am on the day that enters the daylight saving time, the task will be scheduled to perform at 3:00 am on that day instead because 2:00 am on the day entering the DST does not exist. It will return to the normal scheduled time (2:00 am) the next day. See KB article 1814 for additional information.

Calculated next run time for scheduled tasks is incorrect when the VirtualCenter server is in a time zone with daylight savings time changes.
To correct this, upgrade to VirtualCenter 1.3 or later. See KB article 1800 for additional information.

The exported CPU stats will be 1/2 of what is seen in the client
To correct this, upgrade to VirtualCenter 1.3 or later. See KB article 1828 for additional information.

Red Hat Enterprise Linux 4 is not shown as an option when selecting the type of Linux operating system for a new virtual machine.
To correct this, upgrade to VirtualCenter 1.3 or later and GSX Server 3.1 or later.

A user that only has Read-Only access permission to a destination folder and has Virtual Machine Administrative access permission to a source folder is able to clone a virtual machine from the source folder into the destination folder.
There is no work around. To correct this, upgrade to VirtualCenter 1.3 or later.

Database administrator privileges are required while installing and configuring the VirtualCenter database.
After configuration is complete, CONNECT and RESOURCE roles for Oracle databases, and db_ddladmin role for Microsoft SQL databases, are sufficient to write to the database. No additional action required.

VirtualCenter crashes when username entry is a space
To correct this, upgrade to VirtualCenter 1.3 or later. See KB article 1839 for additional information.

 

Issues Resolved in VirtualCenter Version 1.2
The following issue is resolved in VirtualCenter 1.2 and 1.2 patch 1.

Virtual Machines on ESX Server 2.5 Hosts Managed by Virtual Center 1.2 Renamed When Management Server is Restarted
To correct this, upgrade to VirtualCenter 1.2 patch 1 or later.

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.

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 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.

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.

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 article14021806 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.

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 host name 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.