<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: ESX 3.5.0 Update 5 Change in Serivce Console Memory</title>
	<atom:link href="http://www.boche.net/blog/index.php" rel="self" type="application/rss+xml" />
	<link>http://www.boche.net/blog/index.php/2009/12/30/esx-3-5-0-update-5-change-in-serivce-console-memory/</link>
	<description></description>
	<lastBuildDate>Thu, 09 Feb 2012 01:05:19 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Ken</title>
		<link>http://www.boche.net/blog/index.php/2009/12/30/esx-3-5-0-update-5-change-in-serivce-console-memory/comment-page-1/#comment-2013</link>
		<dc:creator>Ken</dc:creator>
		<pubDate>Wed, 09 Jun 2010 23:47:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.boche.net/blog/?p=1893#comment-2013</guid>
		<description>Alternatively you can issue a single vimsh cmd:

vimsh -n -e &quot;/hostsvc/memoryinfo 838860800&quot;

(Requires reboot)</description>
		<content:encoded><![CDATA[<p>Alternatively you can issue a single vimsh cmd:</p>
<p>vimsh -n -e &#8220;/hostsvc/memoryinfo 838860800&#8243;</p>
<p>(Requires reboot)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Arnim van Lieshout</title>
		<link>http://www.boche.net/blog/index.php/2009/12/30/esx-3-5-0-update-5-change-in-serivce-console-memory/comment-page-1/#comment-1423</link>
		<dc:creator>Arnim van Lieshout</dc:creator>
		<pubDate>Thu, 07 Jan 2010 20:45:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.boche.net/blog/?p=1893#comment-1423</guid>
		<description>Well spotted!

Making it future proof and working on both u4 and u5 builds, the sed syntax can be changed into this:
sed -i &#039;s/memSize = &quot;[0-9][0-9][0-9]&quot;/memSize = &quot;800&quot;/&#039; /etc/vmware/esx.conf</description>
		<content:encoded><![CDATA[<p>Well spotted!</p>
<p>Making it future proof and working on both u4 and u5 builds, the sed syntax can be changed into this:<br />
sed -i &#8216;s/memSize = &#8220;[0-9][0-9][0-9]&#8220;/memSize = &#8220;800&#8243;/&#8217; /etc/vmware/esx.conf</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jason</title>
		<link>http://www.boche.net/blog/index.php/2009/12/30/esx-3-5-0-update-5-change-in-serivce-console-memory/comment-page-1/#comment-1417</link>
		<dc:creator>jason</dc:creator>
		<pubDate>Wed, 06 Jan 2010 02:12:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.boche.net/blog/?p=1893#comment-1417</guid>
		<description>I agree that adding more explicitness to the search string will more easily depict what the script is doing to unfamiliar eyes plus it will protect future builds of ESX should additional matching strings be introduced which are not related to memory.  

That aside, future builds should be tested in a LAB or DEV environment.  The scripts work correctly with current builds of ESX and there are not additional matching strings which would taint either configuration file with unintended settings.  

Following are &quot;out-of-the-box&quot; conf files from ESX 3.5 Update 5.  Use the &quot;find&quot; function and you will see there are no additional string matches other than what we intend to change.
http://www.boche.net/dropbox/esx.conf
http://www.boche.net/dropbox/grub.conf

Thank you for the comments!</description>
		<content:encoded><![CDATA[<p>I agree that adding more explicitness to the search string will more easily depict what the script is doing to unfamiliar eyes plus it will protect future builds of ESX should additional matching strings be introduced which are not related to memory.  </p>
<p>That aside, future builds should be tested in a LAB or DEV environment.  The scripts work correctly with current builds of ESX and there are not additional matching strings which would taint either configuration file with unintended settings.  </p>
<p>Following are &#8220;out-of-the-box&#8221; conf files from ESX 3.5 Update 5.  Use the &#8220;find&#8221; function and you will see there are no additional string matches other than what we intend to change.<br />
<a href="http://www.boche.net/dropbox/esx.conf" rel="nofollow">http://www.boche.net/dropbox/esx.conf</a><br />
<a href="http://www.boche.net/dropbox/grub.conf" rel="nofollow">http://www.boche.net/dropbox/grub.conf</a></p>
<p>Thank you for the comments!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeremy Pries</title>
		<link>http://www.boche.net/blog/index.php/2009/12/30/esx-3-5-0-update-5-change-in-serivce-console-memory/comment-page-1/#comment-1414</link>
		<dc:creator>Jeremy Pries</dc:creator>
		<pubDate>Tue, 05 Jan 2010 22:55:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.boche.net/blog/?p=1893#comment-1414</guid>
		<description>I agree that the listed sed commands are dangerous.  You are changing any instance of 272 &amp; 500 to 800 in esx.conf.  There are hundreds of lines in esx.conf.  I think you should be doing a more thorough search.  

Like this.  sed -e &#039;s/boot\/memSize = \&quot;272\&quot;/boot\/memSize = \&quot;512\&quot;/g&#039;

and  sed -e &#039;s/uppermem 277504/uppermem 523264/g&#039; -e &#039;s/mem=272M/mem=512M/g&#039;

Or even better is to use vmware-vim-cmd.  I am still fully testing this, but it should work on both 3.5 and 4.0.  /usr/bin/vmware-vim-cmd /hostsvc/memoryinfo 838860800</description>
		<content:encoded><![CDATA[<p>I agree that the listed sed commands are dangerous.  You are changing any instance of 272 &amp; 500 to 800 in esx.conf.  There are hundreds of lines in esx.conf.  I think you should be doing a more thorough search.  </p>
<p>Like this.  sed -e &#8216;s/boot\/memSize = \&#8221;272\&#8221;/boot\/memSize = \&#8221;512\&#8221;/g&#8217;</p>
<p>and  sed -e &#8216;s/uppermem 277504/uppermem 523264/g&#8217; -e &#8216;s/mem=272M/mem=512M/g&#8217;</p>
<p>Or even better is to use vmware-vim-cmd.  I am still fully testing this, but it should work on both 3.5 and 4.0.  /usr/bin/vmware-vim-cmd /hostsvc/memoryinfo 838860800</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: matt</title>
		<link>http://www.boche.net/blog/index.php/2009/12/30/esx-3-5-0-update-5-change-in-serivce-console-memory/comment-page-1/#comment-1407</link>
		<dc:creator>matt</dc:creator>
		<pubDate>Sat, 02 Jan 2010 02:03:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.boche.net/blog/?p=1893#comment-1407</guid>
		<description>your sed scripts are dangerous. I don&#039;t have the file syntax handy, but I&#039;m pretty sure it&#039;s  &quot;keyword=value&quot; so your script must be written so that action is taken ONLY on the matching &quot;keyword=&quot; line. 

sed  &#039;/keyword=/ s/value1/value2&#039;</description>
		<content:encoded><![CDATA[<p>your sed scripts are dangerous. I don&#8217;t have the file syntax handy, but I&#8217;m pretty sure it&#8217;s  &#8220;keyword=value&#8221; so your script must be written so that action is taken ONLY on the matching &#8220;keyword=&#8221; line. </p>
<p>sed  &#8216;/keyword=/ s/value1/value2&#8242;</p>
]]></content:encoded>
	</item>
</channel>
</rss>

