Comments for Resolving Improper Memory Limits on your Virtual Machines at http://www.vmguru.com , comment 1 to 3 out of 3 comments http://www.vmguru.com Sun, 01 Aug 2010 01:49:40 +0100 FeedCreator 1.7.3 http://www.vmguru.com/index.php/articles-mainmenu-62/scripting/98-resolving-improper-memory-limits-on-your-virtual-machines#comment-17 I am not sure if this is a bug or feature of DRS but I have also noticed that when you remove a host from a DRS enabled cluster and add the host back to the cluster all of the vm's on that host now have memory limits set. We ran into this with several of our vms. - jason robinson Mon, 03 Aug 2009 11:48:30 +0100 http://www.vmguru.com/index.php/articles-mainmenu-62/scripting/98-resolving-improper-memory-limits-on-your-virtual-machines#comment-14 From my experience the limit comes from either settings in the template, from where the VM orignates, or some kind of bug (as Scott mentions in his first post). I have seen templates configured with 256MB ram (Not as a limit, but as a memory configuration) which turns out to be set as a limit, once deployed to a VM. - Rasmus Jensen Tue, 09 Jun 2009 23:49:44 +0100 http://www.vmguru.com/index.php/articles-mainmenu-62/scripting/98-resolving-improper-memory-limits-on-your-virtual-machines#comment-13 Based on the articles, I checked my memory limits with the powershell script. Sure enough, memory limits existed. I was a bit stumped because I haven't explicitly set any limits. Checked my resource pools, and they indeed were unlimited. Decided to check the individual VMs, and there they were set. Do the individual VMs get this because they are built from a template? At any rate, thanks for the scripts to detect and fix the issue. - Erik Wed, 03 Jun 2009 10:17:31 +0100