VMware Support Insider » Alerts

ALERT: Login issue after updating to vCenter 5.1 Update 1

Rick Blythe — Mon, 29 Apr 2013 12:38:45 +0000

VMware has become aware of an issue that may occur after upgrading to vCenter Server 5.1 Update 1.

Specifically:

You are unable to log in using the vSphere Web Client or domain username/password credentials via the vSphere Client.

This issue can occur if the specified vCenter Server login domain user account is associated with a large number of domain groups and multiple domains are configured as SSO identity sources. The precise number of groups at which this issue can occur varies due to the nature of Active Directory internals. However, it is more likely to occur once domain-group membership for an account exceeds 19.

Customers with SSO configured with multiple domain-based identity sources along with vCenter Server domain user accounts that are associated with a large number of groups should not upgrade to vCenter Server 5.1 Update 1.

We urge you to read the official KB article for more details and/or updates:
Cannot log in to vCenter Server using the domain username/password credentials via the vSphere Web Client/vSphere Client after upgrading to vCenter Server 5.1 Update 1 (2050941).

ALERT: Performance history for Past Year may contain only 30 days

Rick Blythe — Wed, 02 Jan 2013 13:48:42 +0000

VMware has become aware of an issue that may occur whereby only one month of performance history appears when trying to see the past year in vSphere 5.1

Specifically, the symptoms are:

You see only the last 30 days of performance history in the ‘past year’ view
Only one month of performance history appears when trying to see the past year

We urge you to read the official KB article for more details:
Performance history for Past Year contains only 30 days of information in vCenter Server 5.1 (2042009).

ALERT: vCenter Server 5.0 and 5.1 does not function correctly when installed with Oracle 11.2.0.3 Patch 10

Rick Blythe — Fri, 21 Dec 2012 13:31:03 +0000

VMware has become aware of an issue that may occur wherein vCenter Server 5.x does not function correctly when installed with Oracle 11.2.0.3 Patch 10.

Symptoms may include:

vCenter Server 5.0 and 5.1 does not function correctly when installed with Oracle 11.2.0.3 Patch 10
Creating a virtual machine fails when vCenter Server 5.0 Update 1b or vCenter Server 5.1 is installed on Oracle 11.2.0.3 Patch 10
You experience issues after installing vCenter Server 5.0 Update 1b or vCenter Server 5.1 with Oracle 11.2.0.3 Patch 10
When creating a new virtual machine on vCenter Server 5.x, you see the error:

An internal error occurred in the vSphere Client.
 Details: Object reference not set to an instance of an object.

For further updates and more information on this alert, refer to KB article:
vCenter Server 5.x does not function correctly when installed with Oracle 11.2.0.3 Patch 10 (2039874).

UPDATE: This issue has been resolved with a new patch. Read more here…

ALERT: Upgrading to View Agent 5.1.2 can result in performance issues

Rick Blythe — Fri, 21 Dec 2012 13:15:05 +0000

VMware has become aware of an issue that may occur when using a View 5.1.2 Agent on a physical machine, the View Connection Broker will repeatedly attempt to configure the agent which can cause a significant performance impact particularly in large scale environments. If you do not use VMware View to access Physical Machine based desktops, no workaround is required.

Symptoms may include:

In environments with multiple physical machines, significant slowdowns occur and you may see stability issues.
When attempting to use the View 5.1.2 Agent on a physical machine, the system slows down.

For further updates and more information on this alert, refer to KB article:
Performance issue when using View 5.1.2 Agent on Physical Machine based desktops (2041977).

Virtual Machines crash after Apple Update

Rick Blythe — Mon, 26 Nov 2012 16:20:40 +0000

Recently Apple released an update for 2012 Macs named MacBook Air and MacBook Pro Update 2.0. The update includes graphics performance and reliability enhancements. Some customers have reported that their virtual machines can crash after applying the Apple MacBook Pro and Air Update 2.0. The issue appears to be most frequently on 2012 Macs with nVidia GPUs when using certain Windows applications that use 3D acceleration. The VMware Engineering team is currently investigating this issue.

VMware Fusion users should refrain from applying this update.

VMware Fusion users who have already applied this update and are affected by this issue can work around it by disabling the Accelerate 3D Graphics option under Virtual Machine > Settings > Display.

For more information, updates, and resolution to this issue, see this KB article: Virtual machines fail while using 3D applications after applying Apple MacBook Air and MacBook Pro Update 2.0 (2040249).

ALERT: Full disk on vShield Edge 5.1.x fails with error: VIX_E_DISK_FULL ERROR

Rick Blythe — Mon, 24 Sep 2012 16:10:42 +0000

VMware has become aware of an issue whereby vCloud Networking and Security 5.1 release can go into an Edge disk full state approximately 14 days after the first edge is deployed.

Symptoms include:

In vCloud Director, attempting a reconfig fails with this error:VIX_E_DISK_FULL
In vCloud Director, when looking at Edge Gateways, you receive this error:Edge VM backing the edge gateway is unreachable

For further updates and more information on this alert, refer to KB article:
Full disk on vShield Edge 5.1.x fails with error: VIX_E_DISK_FULL ERROR (2035939).

ALERT: vSphere Replication 5.1 unable to recover protected virtual machines

Rick Blythe — Mon, 24 Sep 2012 15:56:07 +0000

VMware has become aware of an issue whereby when the Recovery workflow is invoked through the VR 5.1 user interface, the VRMS are instructed to sync to the latest changes from the primary virtual machine. However, since the primary host (or its storage) is not accessible, the sync fails, hence the entire recovery fails. Symptoms include:

vSphere Replication 5.1 (VR) cannot recover protected virtual machines after the ESX host on the primary site is down, disconnected from the network, or its storage is not available.
Affected deployment topologies: 1 vCenter Server (ROBO), 2 vCenter servers:
With VR 5.1, 1 vCenter Server (ROBO) topology (Site A)
vSphere Replication is configured on at least one virtual machine from ESX1 to ESX2
ESX1 becomes unavailable (such as a host failure, power outage, or network issue) or its storage becomes unavailable
An attempt to recover any replicated virtual machine on may ESX2 fail.
With VR 5.1, 2 vCenter Servers topology (Primary Site A and Secondary Site B)
vSphere Replication is configured on at least one virtual machine from ESX1 (in Site A) to ESX2 (in Site B)
The ESX1 host becomes unavailable (such as a host crash, power outage, or network issue) or its storage becomes unavailable
An attempt to recover any replicated virtual machine on may Site B fail.

Note: This issue does not occur if the vCenter Server in Site A is also down.

Important Note: This issue does not occur in any deployments of VMware vCenter Site Recovery Manager where vSphere Replication is also being used.

For further updates and more information on this alert, refer to KB article:
vSphere Replication 5.1 (VR) unable to recover protected virtual machines (2035929).

ALERT: vCenter Server Services hang on startup after upgrading to vCenter Server 5.1

Rick Blythe — Sat, 15 Sep 2012 13:58:02 +0000

VMware has become aware of an issue where:

After upgrading to vCenter Server 5.1, the VMware VirtualCenter Server service fails to start
The VMware VirtualCenter Server service will not successfully stop or start.
The final log in the vpxd.log file shows:
CoreDump: Writing minidump

You see a backtrace near the very bottom of the vpxd.log file which begins with the following:

2012-09-13T11:53:46.802+02:00 [04468 info 'vmmoVm' opID=SWI-c5103928] [VmMo::SetComputeCompatibilityDirty] vm vm-5345 is marked dirty
2012-09-13T11:53:46.786+02:00 [05112 warning 'win32vpxdOsLayer_win32' opID=SWI-56f04b9c] [VpxUnhandledException] Backtrace

For further information, updates, and resolution to this issue, refer to KB article: vCenter Server Services hang on startup after upgrading to vCenter Server 5.1 (2035623).

ALERT: vSphere 5.1 is not compatible with any versions of VMware View

Rick Blythe — Wed, 12 Sep 2012 12:29:42 +0000

VMware vSphere 5.1 is not currently supported with any versions of VMware View.

vSphere 5.1 is in the process of being certified against VMware View. We recommend that you do not upgrade vSphere above the supported versions listed in the VMware View 5.1 Release Notes.

For further updates and more information on this alert, refer to KB article:
vSphere 5.1 is not compatible with any versions VMware View (2035268).

VMware ALERT: Increased restart times with vCenter Server 5.1

Rick Blythe — Tue, 11 Sep 2012 18:37:05 +0000

VMware has become aware of an issue where some customers may encounter increased restart times with the newly released vCenter Server 5.1.

This issue only impacts the start/re-start time for vCenter Server. It does not affect the ongoing operations after vCenter Server has started. In fact, due to improvements to the vCenter Server database, the use of vSphere Web Client, the Inventory Service cache, customers will notice significant performance improvements in vCenter Server 5.1.

For updates and further information on this restart issue, please refer to Knowledgebase article: vCenter Server 5.1 start up may take longer than previous versions (2034975).