<?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: Best Practices for ESX Host Partitions</title>
	<atom:link href="http://vmetc.com/2008/02/12/best-practices-for-esx-host-partitions/feed/" rel="self" type="application/rss+xml" />
	<link>http://vmetc.com/2008/02/12/best-practices-for-esx-host-partitions/</link>
	<description>Go Green with Virtualization. Go UGLY Green with vmetc.com.</description>
	<lastBuildDate>Tue, 17 Apr 2012 03:50:42 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: rbrambley</title>
		<link>http://vmetc.com/2008/02/12/best-practices-for-esx-host-partitions/comment-page-2/#comment-4260</link>
		<dc:creator>rbrambley</dc:creator>
		<pubDate>Fri, 26 Mar 2010 17:45:48 +0000</pubDate>
		<guid isPermaLink="false">http://vmetc.com/2008/02/12/best-practices-for-esx-host-partitions/#comment-4260</guid>
		<description>Brent,&lt;br&gt;&lt;br&gt;You should be able to edit the default and change it to primary, but&lt;br&gt;if not then yes, remove and re add it.</description>
		<content:encoded><![CDATA[<p>Brent,</p>
<p>You should be able to edit the default and change it to primary, but<br />if not then yes, remove and re add it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bent</title>
		<link>http://vmetc.com/2008/02/12/best-practices-for-esx-host-partitions/comment-page-2/#comment-4259</link>
		<dc:creator>Bent</dc:creator>
		<pubDate>Fri, 26 Mar 2010 17:16:50 +0000</pubDate>
		<guid isPermaLink="false">http://vmetc.com/2008/02/12/best-practices-for-esx-host-partitions/#comment-4259</guid>
		<description>In the recommended scheme you describe that the swap partition should be a primary partition.  During the installation, the default however makes it an extended partition.  Does this mean I should delete the extended one and create a primary one instead?</description>
		<content:encoded><![CDATA[<p>In the recommended scheme you describe that the swap partition should be a primary partition.  During the installation, the default however makes it an extended partition.  Does this mean I should delete the extended one and create a primary one instead?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Vps Hosting</title>
		<link>http://vmetc.com/2008/02/12/best-practices-for-esx-host-partitions/comment-page-2/#comment-4042</link>
		<dc:creator>Vps Hosting</dc:creator>
		<pubDate>Tue, 02 Feb 2010 12:45:25 +0000</pubDate>
		<guid isPermaLink="false">http://vmetc.com/2008/02/12/best-practices-for-esx-host-partitions/#comment-4042</guid>
		<description>Thanks for sharing this step by step tutorial.. i really appreciate your effort.</description>
		<content:encoded><![CDATA[<p>Thanks for sharing this step by step tutorial.. i really appreciate your effort.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Best Practices for vSphere (ESX 4) Service Console Partitions &#124; VM /ETC</title>
		<link>http://vmetc.com/2008/02/12/best-practices-for-esx-host-partitions/comment-page-2/#comment-2767</link>
		<dc:creator>Best Practices for vSphere (ESX 4) Service Console Partitions &#124; VM /ETC</dc:creator>
		<pubDate>Wed, 22 Jul 2009 13:19:23 +0000</pubDate>
		<guid isPermaLink="false">http://vmetc.com/2008/02/12/best-practices-for-esx-host-partitions/#comment-2767</guid>
		<description>[...] of my popular posts on VM /ETC has been Best Practices for ESX Host Partitions. Now with vSphere, VMware has changed the recommended ESX 4 Service Console partitioning slightly. [...]</description>
		<content:encoded><![CDATA[<p>[...] of my popular posts on VM /ETC has been Best Practices for ESX Host Partitions. Now with vSphere, VMware has changed the recommended ESX 4 Service Console partitioning slightly. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ccostan</title>
		<link>http://vmetc.com/2008/02/12/best-practices-for-esx-host-partitions/comment-page-2/#comment-3786</link>
		<dc:creator>ccostan</dc:creator>
		<pubDate>Mon, 18 May 2009 18:10:22 +0000</pubDate>
		<guid isPermaLink="false">http://vmetc.com/2008/02/12/best-practices-for-esx-host-partitions/#comment-3786</guid>
		<description>Rich, &lt;br&gt;&lt;br&gt;I know you took most of these values from the Plan and Design but I still feel they are too small.  Most systems I work on these days are at LEAST 76GB local storage.  The current recommendations use about 15GB.  I&#039;d comfortably double most of them if SAN connected.  Once the client has SAN space, they rarely (if ever) use any local VMFS space.  &lt;br&gt;&lt;br&gt;Good topic though.. It&#039;ll be interesting to see if vSphere recommendations change anything.&lt;br&gt;&lt;br&gt;CARLO.</description>
		<content:encoded><![CDATA[<p>Rich, </p>
<p>I know you took most of these values from the Plan and Design but I still feel they are too small.  Most systems I work on these days are at LEAST 76GB local storage.  The current recommendations use about 15GB.  I&#39;d comfortably double most of them if SAN connected.  Once the client has SAN space, they rarely (if ever) use any local VMFS space.  </p>
<p>Good topic though.. It&#39;ll be interesting to see if vSphere recommendations change anything.</p>
<p>CARLO.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ccostan</title>
		<link>http://vmetc.com/2008/02/12/best-practices-for-esx-host-partitions/comment-page-2/#comment-2504</link>
		<dc:creator>ccostan</dc:creator>
		<pubDate>Mon, 18 May 2009 12:10:22 +0000</pubDate>
		<guid isPermaLink="false">http://vmetc.com/2008/02/12/best-practices-for-esx-host-partitions/#comment-2504</guid>
		<description>Rich, &lt;br&gt;&lt;br&gt;I know you took most of these values from the Plan and Design but I still feel they are too small.  Most systems I work on these days are at LEAST 76GB local storage.  The current recommendations use about 15GB.  I&#039;d comfortably double most of them if SAN connected.  Once the client has SAN space, they rarely (if ever) use any local VMFS space.  &lt;br&gt;&lt;br&gt;Good topic though.. It&#039;ll be interesting to see if vSphere recommendations change anything.&lt;br&gt;&lt;br&gt;CARLO.</description>
		<content:encoded><![CDATA[<p>Rich, </p>
<p>I know you took most of these values from the Plan and Design but I still feel they are too small.  Most systems I work on these days are at LEAST 76GB local storage.  The current recommendations use about 15GB.  I&#39;d comfortably double most of them if SAN connected.  Once the client has SAN space, they rarely (if ever) use any local VMFS space.  </p>
<p>Good topic though.. It&#39;ll be interesting to see if vSphere recommendations change anything.</p>
<p>CARLO.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: roger</title>
		<link>http://vmetc.com/2008/02/12/best-practices-for-esx-host-partitions/comment-page-2/#comment-2467</link>
		<dc:creator>roger</dc:creator>
		<pubDate>Tue, 12 May 2009 17:32:48 +0000</pubDate>
		<guid isPermaLink="false">http://vmetc.com/2008/02/12/best-practices-for-esx-host-partitions/#comment-2467</guid>
		<description>Its worth it if you want 0 down time during maintenance upgrades, firmware updates, and or hardware issues.  we couldnt live without HA or Vmotion.</description>
		<content:encoded><![CDATA[<p>Its worth it if you want 0 down time during maintenance upgrades, firmware updates, and or hardware issues.  we couldnt live without HA or Vmotion.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Welcome to vSphere-land! &#187; ESX Links</title>
		<link>http://vmetc.com/2008/02/12/best-practices-for-esx-host-partitions/comment-page-2/#comment-2447</link>
		<dc:creator>Welcome to vSphere-land! &#187; ESX Links</dc:creator>
		<pubDate>Thu, 07 May 2009 04:02:16 +0000</pubDate>
		<guid isPermaLink="false">http://vmetc.com/2008/02/12/best-practices-for-esx-host-partitions/#comment-2447</guid>
		<description>[...] disk space on an ESX host In-depth ESX Server Service Console Partitioning and Provisioning Best Practices for ESX Host Partitions Partitioning local storage on a ESX host VMware Infrastructure 3.5 Review Guide Using Linux shell [...]</description>
		<content:encoded><![CDATA[<p>[...] disk space on an ESX host In-depth ESX Server Service Console Partitioning and Provisioning Best Practices for ESX Host Partitions Partitioning local storage on a ESX host VMware Infrastructure 3.5 Review Guide Using Linux shell [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

