Comments on: PowerCLI: Reset CPU and Memory Limits

By: Arnim van Lieshout

Arnim van Lieshout — Wed, 08 Jun 2011 09:30:51 +0000

Arif,

no, they’re not the same!
a CPU Limit is a hard limit on the amount of CPU GHz a vCPU wil receive.
a CPU mask on the other hand is a way to hide specific bits that identify the CPU and its features. For vMotion compatibility certain bits MUST match otherwise vMotion will fail.

By: Arif

Arif — Wed, 25 May 2011 03:33:49 +0000

Arnim, I must tell you that VMware vSphere PowerCLI Reference: is a great book! I had to preorder this book
Regarding this script, I have a question, is CPU mask reset and CPU Limit reset to 1 are the same? I need to figure out a way to group vm cpu mask reset using PowerShell. Thanks

By: Top 5 Planet V12n blog posts week 22 | Download VDI Solutions

Top 5 Planet V12n blog posts week 22 | Download VDI Solutions — Wed, 27 Oct 2010 00:00:49 +0000

[...] van Lieshout – PowerCLI: Reset CPU and Memory LimitsToday I noticed a memory limit on a vm. After investigating my environment using the vEcoShell and [...]

By: Przykazania – po trzecie – NIE UŻYWAJ LIMITÓW PAMIĘCI do cholery! « Wirtualizacja w praktyce

Fri, 27 Aug 2010 02:12:20 +0000

[...] Arnim van Lieshout – skrypt do resetowania limitów http://www.van-lieshout.com/2010/06/powercli-reset-cpu-and-memory-limits/ [...]

By: Ed Grigson

Ed Grigson — Sat, 24 Jul 2010 11:58:10 +0000

That makes sense now that you point it out. Thanks for clarifying – I’d wondered why the powerpack sometimes duplicated built-in functionality and this explains perfectly.

By: Arnim van Lieshout

Arnim van Lieshout — Fri, 23 Jul 2010 13:12:00 +0000

You are absolutely right Ed!
Only that option uses the Set-VMResourceConfiguration cmdlet which is rather slow as described in my article. Accessing the API object to do this task is a much faster alternative.

By: Ed Grigson

Ed Grigson — Fri, 23 Jul 2010 12:24:09 +0000

Nice scripts, although can’t you already do this with the built in functionality (not the community powerpack)? Go to the VMWare node, then Virtual Machines then Links -> Resource Configurations. There’s are two Actions there – ‘Set CPU Limit to Unlimited’ and ‘Set Memory Limit to Unlimited’.

By: Brandon

Brandon — Tue, 29 Jun 2010 17:40:33 +0000

Thanks Arnim! I started playing around with it some more and it seems that about 50 of our 600 systems that did have limits are returning the same issue. Thankfully for the other 550 the script worked fine. I just needed to deselect the problem children.

Brandon

By: Arnim van Lieshout

Arnim van Lieshout — Tue, 29 Jun 2010 15:31:56 +0000

Brandon,
Your powerCLI version is ok.

The error message refers to System.Object[] so an array of objects is returned instead of a single object.
In other words the query for the vm returns more than one vm.
This could be caused by:
multiple VMs with the same name
multiple connections to the same server
multiple connections to different servers where a vm with the same name exists

Make sure the VM name is unique accross all connections.

An update to the script is needed to check for this condition. I’ll post an update when I find the time.

-Arnim

By: Brandon

Brandon — Tue, 29 Jun 2010 14:09:25 +0000

I tried adding your code to the Powerpack. It added OK, but when I run it I get an error at Line 10 char 24 “Method invocation failed because [System.Object[]] doesn’t contain a method named ‘ReconfigVM_Task’.”

I am going to take a guess that I might be needing an update to my powercli version..