"I believe that if you show people the problems and you show them the solutions they will be moved to act" — Bill Gates
Log in

vSphere PowerCLI Blog: Checking the Pay-As-You-Go MHz Issue


Posted February 3, 2012 by
NOTE:  This is syndicated content from The VMware Blogs and as such any views or opinions presented are solely those of the respective author(s) and do not necessarily represent those of Jon Wallace or insidetheregistry.com

Copyright of this content belongs to the respective author(s)

Read the original content here

Whilst sitting in a vCD Deep Dive presentation by Aidan Dalgliesh and David Hill last week at the London VMUG they explained an issue which has been reported on multiple occasions, they have seen this more than once on customer deployments and the issue had been reported on the internet both by Massimo Re Ferre and Kendrick Coleman.

When setting up a new Organization vDC with a Pay-As-You-Go model the default vCPU Speed is set to 0.26 GHz, most people continue on through the wizard without changing this and end up crippling their VMs as this adds a CPU limit onto the VM meaning the VM will never get past this speed limit.

image

This of course gives us a great reason to produce a one-liner from the PowerCLI vCD snapin to check your complete cloud infrastructure for any Organization vDCs which may have this default still enabled.

Get-OrgVdc | Where {$_.AllocationModel -eq "PayAsYouGo"} | Where {$_.ExtensionData.VCpuInMhz -eq 260}

As you can see, the above one-liner firstly grabs all Organization vDCs and then checks these to see if their allocation model is “PayAsYouGo”, once it has found these it will check the vCPUInMHZ property to see if it is set to 260 or 0.26GHz.

An example of this can be seen below:

SNAGHTML4b994843