<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:clearspace="http://www.jivesoftware.com/xmlns/clearspace/rss" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:opensearch="http://a9.com/-/spec/opensearch/1.1/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>VMware Communities: Message List - Could not power on VM : Limit exceeded -   What limit?</title>
    <link>http://communities.vmware.com/community/vmtn/mgmt/labmanager?view=discussions</link>
    <description>Most recent forum messages</description>
    <language>en</language>
    <pubDate>Tue, 09 Jun 2009 23:30:24 GMT</pubDate>
    <generator>Clearspace 1.10.12 (http://jivesoftware.com/products/clearspace/)</generator>
    <dc:date>2009-06-09T23:30:24Z</dc:date>
    <dc:language>en</dc:language>
    <item>
      <title>Re: Could not power on VM : Limit exceeded -   What limit?</title>
      <link>http://communities.vmware.com/message/1278537?tstart=0#1278537</link>
      <description>&lt;br /&gt;
&lt;a class="jive-link-external" href="http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&amp;#38;cmd=displayKC&amp;#38;externalId=1009144"&gt;http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&amp;#38;cmd=displayKC&amp;#38;externalId=1009144&lt;/a&gt;&lt;br /&gt;
&lt;p /&gt;
I'll just bet it's the COW settings. Also, ensure your Service Console is set to 800MB (Max.)&lt;br /&gt;
&lt;p /&gt;
Default is 32 (minimum)&lt;br /&gt;
&lt;p /&gt;
When you exhaust the allocated COW heap size and you cannot power-on the virtual machines, check the var/log/vmkernel file for messages indicating that the COW heap has been exhausted. If you have exhausted the COW heap, reconfigure the values on ESX Server. You cannot update the values on Lab Manager. &lt;br /&gt;
To update the values on ESX Server: &lt;br /&gt;
&lt;br /&gt;
&lt;ol&gt;
&lt;li&gt;log in to ESX Server by using the VI Client.&lt;/li&gt;
&lt;li&gt;Click the &lt;b&gt;Configuration&lt;/b&gt; tab.&lt;/li&gt;
&lt;li&gt;Click the &lt;b&gt;Advanced Settings&lt;/b&gt; link. &lt;br clear="all" /&gt; 	The Advanced Settings window appears.&lt;/li&gt;
&lt;li&gt;Select &lt;b&gt;COW&lt;/b&gt;.&lt;/li&gt;
&lt;li&gt;Update the value for the COW.MaxHeapSizeMB parameter.&lt;/li&gt;
&lt;/ol&gt;
&lt;br /&gt;
Best of luck!</description>
      <pubDate>Tue, 09 Jun 2009 23:30:24 GMT</pubDate>
      <author>jjgunn</author>
      <guid>http://communities.vmware.com/message/1278537?tstart=0#1278537</guid>
      <dc:date>2009-06-09T23:30:24Z</dc:date>
      <clearspace:dateToText>5 months, 2 weeks ago</clearspace:dateToText>
    </item>
    <item>
      <title>Re: Could not power on VM : Limit exceeded -   What limit?</title>
      <link>http://communities.vmware.com/message/1276924?tstart=0#1276924</link>
      <description>Also check under Manage -&amp;gt; Resources.  Go to the Hosts tab and check the properties for the ESX hosts.&lt;br /&gt;
On mine, there is a line that says "Maximum Number of VMs      Automatically managed by DRS"&lt;br /&gt;
&lt;br /&gt;
You mention that you're using HA &amp;#38; VMotion, but you didn't mention DRS.&lt;br /&gt;
&lt;br /&gt;
Is the "Max Number of VM's" a configurable option if you're not using DRS on your Lab Manager cluster?  (I know it used to be, in the older versions of Lab Manager that weren't 100% integrated with VirtualCenter.)</description>
      <pubDate>Mon, 08 Jun 2009 21:53:21 GMT</pubDate>
      <author>PezJunkie</author>
      <guid>http://communities.vmware.com/message/1276924?tstart=0#1276924</guid>
      <dc:date>2009-06-08T21:53:21Z</dc:date>
      <clearspace:dateToText>5 months, 2 weeks ago</clearspace:dateToText>
    </item>
    <item>
      <title>Re: Could not power on VM : Limit exceeded -   What limit?</title>
      <link>http://communities.vmware.com/message/1273586?tstart=0#1273586</link>
      <description>Do you have the fail over capacity in HA set to do not allow constraint violations? If so you may need to uncheck that and then try. What is the fail over capacity compaired to the configured?</description>
      <pubDate>Fri, 05 Jun 2009 04:24:16 GMT</pubDate>
      <author>Chamon</author>
      <guid>http://communities.vmware.com/message/1273586?tstart=0#1273586</guid>
      <dc:date>2009-06-05T04:24:16Z</dc:date>
      <clearspace:dateToText>5 months, 3 weeks ago</clearspace:dateToText>
    </item>
    <item>
      <title>Could not power on VM : Limit exceeded -   What limit?</title>
      <link>http://communities.vmware.com/message/1273584?tstart=0#1273584</link>
      <description>&lt;br /&gt;
I using LM 3.0.1 and ESX 3.5 in the lab.  The LM cluster is two nodes configured with HA and Vmotion enabled. I count about 37 VM's deployed, 22 networks. I recently tried to power-on one of my configs and got an error:&lt;br /&gt;
&lt;p /&gt;
VirtualMachine.powerOn task on PowerOnVM_Task failed: Could not power on VM : Limit exceeded. Failed to power on VM. &lt;br /&gt;
&lt;p /&gt;
 I checked the VIC logs and found basically the same error:  Could not power on VM : Limit exceeded&lt;br /&gt;
&lt;p /&gt;
 Q: Where can I find details of exactly what limit was exceeded?   From the ESX summary page , the server seems to have enough memory and other resources.&lt;br /&gt;
&lt;p /&gt;
Thanks for advice/suggestions.&lt;br /&gt;
&lt;p /&gt;
-Greg</description>
      <pubDate>Fri, 05 Jun 2009 04:17:50 GMT</pubDate>
      <author>gbaysden5150</author>
      <guid>http://communities.vmware.com/message/1273584?tstart=0#1273584</guid>
      <dc:date>2009-06-05T04:17:50Z</dc:date>
      <clearspace:dateToText>5 months, 3 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>3</clearspace:replyCount>
    </item>
  </channel>
</rss>

