<?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>Jonathan Marrott's VM Scripting Blog</title>
    <link>http://communities.vmware.com/blogs/froboy</link>
    <description>Comment Feed for Jonathan Marrott's VM Scripting Blog on post 'Set Service Console Memory (Updated)'</description>
    <pubDate>Tue, 09 Oct 2007 20:27:37 GMT</pubDate>
    <generator>Clearspace 1.10.12 (http://jivesoftware.com/products/clearspace/)</generator>
    <dc:date>2007-10-09T20:27:37Z</dc:date>
    <item>
      <title>RE:&amp;nbsp;Set Service Console Memory (Updated)</title>
      <link>http://communities.vmware.com/blogs/froboy/2008/01/18/set-service-console-memory-updated#comments-1558</link>
      <description>Configuration Maximums for VMware Infrastructure 3:&lt;br /&gt;
&lt;br /&gt;
Table 4. Memory Maximums    Maximum &lt;br /&gt;
Size of RAM per server 64GB &lt;br /&gt;
RAM allocated to service console 800MB  &lt;br /&gt;
&lt;br /&gt;
Installation and Upgrade Guide:&lt;br /&gt;
Enhanced Performance Recommendations&lt;br /&gt;
The lists in previous sections suggest a basic ESX Server configuration. In practice, you can use multiple physical disks, which can be SCSI disks, Fibre Channel LUNs, or RAID LUNs.&lt;br /&gt;
Here are some recommendations for enhanced performance:&lt;br /&gt;
• RAM – Having sufficient RAM for all your virtual machines is important to achieving good performance. ESX Server hosts require more RAM than typical servers. An ESX Server host must be equipped with sufficient RAM to run concurrent virtual machines, plus run the service console.  &lt;br /&gt;
&lt;br /&gt;
For example, operating four virtual machines with Red Hat Enterprise Linux or Windows XP requires your ESX Server host be equipped with over a gigabyte of RAM for baseline performance:&lt;br /&gt;
• 1024MB for the virtual machines (256MB minimum per operating system as recommended by vendors × 4) &lt;br /&gt;
&lt;br /&gt;
• 272MB for the ESX Server service console &lt;br /&gt;
&lt;br /&gt;
Running these example virtual machines with a more reasonable 512MB RAM requires the ESX Server host to be equipped with at least 2.2GB RAM.&lt;br /&gt;
• 2048MB for the virtual machines (512MB × 4) &lt;br /&gt;
&lt;br /&gt;
• 272MB for the ESX Server service console &lt;br /&gt;
&lt;br /&gt;
These calculations do not take into account variable overhead memory for each virtual machine. For more information, see the Resource Management Guide.&lt;br /&gt;
&lt;p /&gt;
 Note     &lt;br /&gt;
 The ESX Server host might require more RAM for the service console if you are running third-party management applications or backup agents.</description>
      <pubDate>Tue, 09 Oct 2007 20:27:37 GMT</pubDate>
      <author>froboy</author>
      <guid>http://communities.vmware.com/blogs/froboy/2008/01/18/set-service-console-memory-updated#comments-1558</guid>
      <dc:date>2007-10-09T20:27:37Z</dc:date>
    </item>
    <item>
      <title>RE:&amp;nbsp;Set Service Console Memory (Updated)</title>
      <link>http://communities.vmware.com/blogs/froboy/2008/01/18/set-service-console-memory-updated#comments-1557</link>
      <description>Thanks, your reply is much appreciated.  Can you point me in the direction of where this is documented?</description>
      <pubDate>Tue, 09 Oct 2007 20:18:10 GMT</pubDate>
      <author>j.d.vmware</author>
      <guid>http://communities.vmware.com/blogs/froboy/2008/01/18/set-service-console-memory-updated#comments-1557</guid>
      <dc:date>2007-10-09T20:18:10Z</dc:date>
    </item>
    <item>
      <title>RE:&amp;nbsp;Set Service Console Memory (Updated)</title>
      <link>http://communities.vmware.com/blogs/froboy/2008/01/18/set-service-console-memory-updated#comments-1556</link>
      <description>The max is 800 MB. (Odd number I thought it would have been 1024 or something.) For the amount of scripts and apps that we were running VMWare suggested that we at minimum increased our SC memory to 512.  If we were still having performance issues to increase it to 800.  512 did the trick.</description>
      <pubDate>Tue, 09 Oct 2007 20:14:51 GMT</pubDate>
      <author>froboy</author>
      <guid>http://communities.vmware.com/blogs/froboy/2008/01/18/set-service-console-memory-updated#comments-1556</guid>
      <dc:date>2007-10-09T20:14:51Z</dc:date>
    </item>
    <item>
      <title>RE:&amp;nbsp;Set Service Console Memory (Updated)</title>
      <link>http://communities.vmware.com/blogs/froboy/2008/01/18/set-service-console-memory-updated#comments-1555</link>
      <description>Where is anything on the service console memory documented?  I've been looking through all the docs and can't find anyting.  Is the max suggested 512?</description>
      <pubDate>Tue, 09 Oct 2007 19:39:30 GMT</pubDate>
      <author>j.d.vmware</author>
      <guid>http://communities.vmware.com/blogs/froboy/2008/01/18/set-service-console-memory-updated#comments-1555</guid>
      <dc:date>2007-10-09T19:39:30Z</dc:date>
    </item>
  </channel>
</rss>

