VMware
[an error occurred while processing this directive]

 

VMware VirtualCenter 1.1 Release Notes: Resolved Issues

Release Notes | Known Issues for This Release

The following items is 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 below.

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.