Tag Archives: Vmware


For those who kept close watch on 5.1 Update 1 – you are aware of the failed domain login attempts to the vsphere client or the web client which will basically lock you out of your own vmware environment. What vmware had to say about the issue,

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.

So if you have an SSO configured for multiple domain identity sources or if you have vcenter domain user accounts associated with large number of groups – updating to 5.1 Update 1 will break things for you!

If you already updated to vCenter 5.1 Update 1 – then the fix is you simply update vCenter to 5.1 Update 1a. The KB article is here.

The article explaining what went wrong is here. The issue was identified to have caused because of the way Active directory domain trusts work.

vCenter 5.1 Update 1 has been replaced with vCenter 5.1 Update 1a for you to download and install.

Lets hope 1a won’t break anything else 🙂

Please do comment if you feel like!





vQuicky –

> DRS has a bug that shows multiple vmotions or svmotions for a single vm

> The bug reports operation not allowed in current state.

> The DRS operation, however succeeds.

> The bug is harmless and can be ignored according to vmware.

inDepth  – 

So, in the latest KB articles come up a DRS bug in 5.1 where you will see multiple vmotions or svmotions for a single vm. The alerts end up throwing an error saying – “The operation is not allowed in the current state.”

The kicker is that the vmotion or svmotion that was being performed completes without any issue.

You will also see some logs in the vpxd log file as follows –


[07208 error ‘drmLogger’ opID=task-internal-1-2cbc1369-5e-72-b5] [DrmExecute::ExecuteVMotion] VM FW.host.local (/vpx/vm/#2/) is already in VMotion, so not executing another vmotion
> 2013-01-16T15:55:32.018+01:00 [07208 info ‘Default’ opID=task-internal-1-2cbc1369-5e-72-b5] [VpxLRO] — ERROR task-13275 — vm-2 — Drm.ExecuteVMotionLRO: vim.fault.InvalidState:

> –> Result:
> –> (vim.fault.InvalidState) {
> –> dynamicType = <unset>,
> –> faultCause = (vmodl.MethodFault) null,
> –> msg = “”,
> –> }
> –> Args:
> –>


The vmware kb article says that this is a bug that can be safely ignored. Apparently they are working on a fix but watch out for your monitoring systems ringing the alarm bells 🙂

You can find the kb article here.

VMware will soon allow Openstack hosting!


At OpenStack summit in SanDiego and news from the VMware booth is that VMware ESXi will soon support spinning up OpenStack instances on VMware.

So does that mean the compute node will manage ESXi? Or does it mean ESXi will manage the compute nodes?
It surely is exciting. VMware already bought Nycera which is virtualization for networking and PAAS with Cloudfoundry.

I suspect it will be more than just this!

More as we know it 🙂

VMware Announces no more vRAM Entitlements!

Lets not even debate the whole structure about the vRAM pricing but VMware at VMWorld just announced (a minute back) that there are no more vRAM license entitlements. No vRAM, no per vm licensing model. Only per socket model which makes a lot of things easier. This was received with a lot of applause!