<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: cannot 'reserve all guest memory' - cannot satisfy failover for HA in vCenter™ Server Discussions</title>
    <link>https://communities.vmware.com/t5/vCenter-Server-Discussions/cannot-reserve-all-guest-memory-cannot-satisfy-failover-for-HA/m-p/936200#M28526</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks both. I changed the HA policy to reserve 20% as failover spare capacity, then set the 'reserve all guest memory' on the vm, which completed successfully. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;After reading through more discussions I am now beginning to suspect this issue might have started after changing the pagefile recently. It was set to 12GB + 10MB as per Microsoft's recommendation. Due to space constraints on the C: drive, this was lowered to 'system managed size' (5119MB). I have now extended the C drive so can restore the pagefile back to my previous Microsoft recommended figure. I'll do this out of hours tonight as it'll require a reboot.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If correct, then my vm is paging to memory, which is not ideal. I'll bump up the memory to 16GB to see if that helps. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I can report that putting the vm into the newly created resource pool, which had a memory reservation of over 12GB did nothing to stop the Information Store errors mentioned in my first post.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'll update again tomorrow after the reboot.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 01 Dec 2014 12:15:30 GMT</pubDate>
    <dc:creator>miyo360</dc:creator>
    <dc:date>2014-12-01T12:15:30Z</dc:date>
    <item>
      <title>cannot 'reserve all guest memory' - cannot satisfy failover for HA</title>
      <link>https://communities.vmware.com/t5/vCenter-Server-Discussions/cannot-reserve-all-guest-memory-cannot-satisfy-failover-for-HA/m-p/936197#M28523</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have a 3-host cluster running ESXI 5.1. Each host has 96GB of memory and around 5-6 running vm's. Each host is showing memory usage around 40%. I have an Exchange 2013 server which is reporting 'memory allocation failures' that are causing databases to go offline momentarily. The full error is &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;BLOCKQUOTE&gt;
&lt;P&gt;&lt;EM&gt;Information Store - MailDB4 (8096) MailDB4: The system is experiencing memory allocation failures that are preventing proper operation of database 'MailDB4' ('777d4e3c-d5fd-4a65-93cf-bdb12ca9e4d2').&amp;nbsp; The error could occur due to a mis-configuration or excessive memory consumption on the machine. &lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;&lt;EM&gt;Additional diagnostic information:&amp;nbsp; cc95a8ab-7b96-45e2-bcad-9da4323e74b0 &lt;/EM&gt;&lt;/P&gt;
&lt;/BLOCKQUOTE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This VM has been given 12GB of memory and supports around 50 active mailboxes. I would like to reserve all guest memory for the vm, to ensure the host does not interfere. This is my first attempt at tackling the errors above. However, when I attempt to reserve the memory, I get the error &lt;/P&gt;&lt;BLOCKQUOTE&gt;
&lt;P&gt;Insufficient resources to satisfy configured failover level for vSphere HA.&lt;/P&gt;
&lt;/BLOCKQUOTE&gt;&lt;P&gt;My HA settings allow for 1 host failure in the cluster. The cluster total memory is 287GB. If a host fails, then approx 196GB is available in the cluster. Counting used space shows all vm's are consuming around 107GB, so there is plenty of memory available in the event of a single host failure. Therefore I'm not sure why I am seeing the error above when trying to reserve memory for this vm.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What I have done now is create a new resource pool for just this server, reserve over 12GB for that pool, then I have added the vm to that pool, which seems happy. I presume this achieves the same result? Time will tell whether it will resolve the Exchange errors above though.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thoughts and comments appreciated.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 01 Dec 2014 10:38:31 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vCenter-Server-Discussions/cannot-reserve-all-guest-memory-cannot-satisfy-failover-for-HA/m-p/936197#M28523</guid>
      <dc:creator>miyo360</dc:creator>
      <dc:date>2014-12-01T10:38:31Z</dc:date>
    </item>
    <item>
      <title>Re: cannot 'reserve all guest memory' - cannot satisfy failover for HA</title>
      <link>https://communities.vmware.com/t5/vCenter-Server-Discussions/cannot-reserve-all-guest-memory-cannot-satisfy-failover-for-HA/m-p/936198#M28524</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;another option could be to set a percentage of resources to set aside fro HA instead of # of hosts (i.e. 15 or 20% - something LESS than 1/3, just to test). another option would be to temporarily break out 2 hosts into a test cluster and test the single VM on that cluster. It 'sounds' more like an OS/Memory leak issue more than a cluster issue (rather, an OS issue CAUSING an HA problem). &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What is the error that prevents you from reserving all of the VM's memory?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 01 Dec 2014 11:21:21 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vCenter-Server-Discussions/cannot-reserve-all-guest-memory-cannot-satisfy-failover-for-HA/m-p/936198#M28524</guid>
      <dc:creator>ExpletiveDelete</dc:creator>
      <dc:date>2014-12-01T11:21:21Z</dc:date>
    </item>
    <item>
      <title>Re: cannot 'reserve all guest memory' - cannot satisfy failover for HA</title>
      <link>https://communities.vmware.com/t5/vCenter-Server-Discussions/cannot-reserve-all-guest-memory-cannot-satisfy-failover-for-HA/m-p/936199#M28525</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I would also try setting a failover consisting of % resources, rather than the whole host value (which will soon be deprecated according to literature) and test it out again. Also, the issue seems to be springing up from the OS. Could you try bumping up the memory a little and observe if your guest OS is making any kind of swapping? Is the swap file set accordingly in your OS?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 01 Dec 2014 11:52:57 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vCenter-Server-Discussions/cannot-reserve-all-guest-memory-cannot-satisfy-failover-for-HA/m-p/936199#M28525</guid>
      <dc:creator>Alistar</dc:creator>
      <dc:date>2014-12-01T11:52:57Z</dc:date>
    </item>
    <item>
      <title>Re: cannot 'reserve all guest memory' - cannot satisfy failover for HA</title>
      <link>https://communities.vmware.com/t5/vCenter-Server-Discussions/cannot-reserve-all-guest-memory-cannot-satisfy-failover-for-HA/m-p/936200#M28526</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks both. I changed the HA policy to reserve 20% as failover spare capacity, then set the 'reserve all guest memory' on the vm, which completed successfully. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;After reading through more discussions I am now beginning to suspect this issue might have started after changing the pagefile recently. It was set to 12GB + 10MB as per Microsoft's recommendation. Due to space constraints on the C: drive, this was lowered to 'system managed size' (5119MB). I have now extended the C drive so can restore the pagefile back to my previous Microsoft recommended figure. I'll do this out of hours tonight as it'll require a reboot.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If correct, then my vm is paging to memory, which is not ideal. I'll bump up the memory to 16GB to see if that helps. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I can report that putting the vm into the newly created resource pool, which had a memory reservation of over 12GB did nothing to stop the Information Store errors mentioned in my first post.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'll update again tomorrow after the reboot.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 01 Dec 2014 12:15:30 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vCenter-Server-Discussions/cannot-reserve-all-guest-memory-cannot-satisfy-failover-for-HA/m-p/936200#M28526</guid>
      <dc:creator>miyo360</dc:creator>
      <dc:date>2014-12-01T12:15:30Z</dc:date>
    </item>
    <item>
      <title>Re: cannot 'reserve all guest memory' - cannot satisfy failover for HA</title>
      <link>https://communities.vmware.com/t5/vCenter-Server-Discussions/cannot-reserve-all-guest-memory-cannot-satisfy-failover-for-HA/m-p/936201#M28527</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Please note that resource pools come into play only when the ESXi host is facing resource contention - it then decides which VMs to keep in memory and which portion of VMs' memory can be swapped out. The same with frequency - that is a matter of cycle priority then &lt;img id="smileyhappy" class="emoticon emoticon-smileyhappy" src="https://communities.vmware.com/i/smilies/16x16_smiley-happy.png" alt="Smiley Happy" title="Smiley Happy" /&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 01 Dec 2014 12:18:04 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vCenter-Server-Discussions/cannot-reserve-all-guest-memory-cannot-satisfy-failover-for-HA/m-p/936201#M28527</guid>
      <dc:creator>Alistar</dc:creator>
      <dc:date>2014-12-01T12:18:04Z</dc:date>
    </item>
    <item>
      <title>Re: cannot 'reserve all guest memory' - cannot satisfy failover for HA</title>
      <link>https://communities.vmware.com/t5/vCenter-Server-Discussions/cannot-reserve-all-guest-memory-cannot-satisfy-failover-for-HA/m-p/936202#M28528</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Just wanted to report back. I have made the following changes to our Exchange server&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Increased server memory from 12GB to 16GB&lt;/LI&gt;&lt;LI&gt;Set pagefile to 16GB+10MB as per Microsofts recommendation (it was previously set to 'system managed' (approx 5GB))&lt;/LI&gt;&lt;LI&gt;Bumped up my C drive another 20GB to accommodate the increased page file&lt;/LI&gt;&lt;LI&gt;Rebooted&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This seems to have fixed the error logs about memory allocation failures. I suspect an inadequate pagefile was the main culprit here. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Meanwhile, I will review my use of resource pools.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks to ExpletiveDeleted and Alistar for their advice.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 02 Dec 2014 12:09:56 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vCenter-Server-Discussions/cannot-reserve-all-guest-memory-cannot-satisfy-failover-for-HA/m-p/936202#M28528</guid>
      <dc:creator>miyo360</dc:creator>
      <dc:date>2014-12-02T12:09:56Z</dc:date>
    </item>
  </channel>
</rss>

