<?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: partitioning your esx</title>
	<atom:link href="http://www.yellow-bricks.com/2008/10/23/partitioning-your-esx/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.yellow-bricks.com/2008/10/23/partitioning-your-esx/</link>
	<description>Building blocks for virtualization...</description>
	<lastBuildDate>Fri, 19 Mar 2010 17:57:34 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>By: Sid Smith</title>
		<link>http://www.yellow-bricks.com/2008/10/23/partitioning-your-esx/comment-page-1/#comment-4048</link>
		<dc:creator>Sid Smith</dc:creator>
		<pubDate>Thu, 16 Jul 2009 20:23:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.yellow-bricks.com/?p=709#comment-4048</guid>
		<description>The only caveat with deploying multiple VMFS partitions is you need to perform a scripted installation in order to achieve this....as far as I can see.  However I think all installations should be scripted anyway.....</description>
		<content:encoded><![CDATA[<p>The only caveat with deploying multiple VMFS partitions is you need to perform a scripted installation in order to achieve this&#8230;.as far as I can see.  However I think all installations should be scripted anyway&#8230;..</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Duncan</title>
		<link>http://www.yellow-bricks.com/2008/10/23/partitioning-your-esx/comment-page-1/#comment-4047</link>
		<dc:creator>Duncan</dc:creator>
		<pubDate>Thu, 16 Jul 2009 20:17:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.yellow-bricks.com/?p=709#comment-4047</guid>
		<description>I totally agree, I would actually always have two seperate partitions just in case you ever need it for testing or whatever.</description>
		<content:encoded><![CDATA[<p>I totally agree, I would actually always have two seperate partitions just in case you ever need it for testing or whatever.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sid Smith</title>
		<link>http://www.yellow-bricks.com/2008/10/23/partitioning-your-esx/comment-page-1/#comment-4046</link>
		<dc:creator>Sid Smith</dc:creator>
		<pubDate>Thu, 16 Jul 2009 17:52:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.yellow-bricks.com/?p=709#comment-4046</guid>
		<description>What about environments that are moving to vSphere and are utilizing the local VMFS for VMs or vSWP files.  In this case I would recommend having two separate VMFS partitions on the local storage.  One for the Service Console vmdk, and one for everything else be it vSWP or VM&#039;s.  Any thoughts on that?</description>
		<content:encoded><![CDATA[<p>What about environments that are moving to vSphere and are utilizing the local VMFS for VMs or vSWP files.  In this case I would recommend having two separate VMFS partitions on the local storage.  One for the Service Console vmdk, and one for everything else be it vSWP or VM&#8217;s.  Any thoughts on that?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Duncan</title>
		<link>http://www.yellow-bricks.com/2008/10/23/partitioning-your-esx/comment-page-1/#comment-3627</link>
		<dc:creator>Duncan</dc:creator>
		<pubDate>Thu, 28 May 2009 06:07:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.yellow-bricks.com/?p=709#comment-3627</guid>
		<description>If you are running 3.5 and doing boot from SAN. No there&#039;s no point indeed.

but if you are running 4.0 the Service Console is a VMDK so you will need VMFS to boot it from.</description>
		<content:encoded><![CDATA[<p>If you are running 3.5 and doing boot from SAN. No there&#8217;s no point indeed.</p>
<p>but if you are running 4.0 the Service Console is a VMDK so you will need VMFS to boot it from.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: dogcanterbury</title>
		<link>http://www.yellow-bricks.com/2008/10/23/partitioning-your-esx/comment-page-1/#comment-3626</link>
		<dc:creator>dogcanterbury</dc:creator>
		<pubDate>Wed, 27 May 2009 20:51:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.yellow-bricks.com/?p=709#comment-3626</guid>
		<description>IMHO I think if the infrastructure is shared storage, there is no point creating a vmfs partition. think not?</description>
		<content:encoded><![CDATA[<p>IMHO I think if the infrastructure is shared storage, there is no point creating a vmfs partition. think not?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: teaphe</title>
		<link>http://www.yellow-bricks.com/2008/10/23/partitioning-your-esx/comment-page-1/#comment-2911</link>
		<dc:creator>teaphe</dc:creator>
		<pubDate>Tue, 24 Mar 2009 04:11:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.yellow-bricks.com/?p=709#comment-2911</guid>
		<description>how do I create the vmkcore and vmfs partition during the installation of ESX or in VC? co&#039;z I can&#039;t find a vmfs and vmkcore file system during the installation of ESX. 

THanks.</description>
		<content:encoded><![CDATA[<p>how do I create the vmkcore and vmfs partition during the installation of ESX or in VC? co&#8217;z I can&#8217;t find a vmfs and vmkcore file system during the installation of ESX. </p>
<p>THanks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: George</title>
		<link>http://www.yellow-bricks.com/2008/10/23/partitioning-your-esx/comment-page-1/#comment-1785</link>
		<dc:creator>George</dc:creator>
		<pubDate>Fri, 21 Nov 2008 09:48:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.yellow-bricks.com/?p=709#comment-1785</guid>
		<description>Got it. Thanks Duncan. By the way, your site rocks!!</description>
		<content:encoded><![CDATA[<p>Got it. Thanks Duncan. By the way, your site rocks!!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Duncan Epping</title>
		<link>http://www.yellow-bricks.com/2008/10/23/partitioning-your-esx/comment-page-1/#comment-1784</link>
		<dc:creator>Duncan Epping</dc:creator>
		<pubDate>Fri, 21 Nov 2008 09:26:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.yellow-bricks.com/?p=709#comment-1784</guid>
		<description>George,

the vmkcore partition is used to  store the core dumps generated by the vmkernel. the /var/core directory is used to store the coredumps generated by the service console, which is red hat.</description>
		<content:encoded><![CDATA[<p>George,</p>
<p>the vmkcore partition is used to  store the core dumps generated by the vmkernel. the /var/core directory is used to store the coredumps generated by the service console, which is red hat.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: George</title>
		<link>http://www.yellow-bricks.com/2008/10/23/partitioning-your-esx/comment-page-1/#comment-1783</link>
		<dc:creator>George</dc:creator>
		<pubDate>Fri, 21 Nov 2008 09:02:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.yellow-bricks.com/?p=709#comment-1783</guid>
		<description>But the official documentation says:

vmkcore – A vmkcore partition is required to store core dumps for
troubleshooting. VMware does not support ESX Server host configurations
without a vmkcore partition

Install Guide , page 91

I&#039;m getting confused...</description>
		<content:encoded><![CDATA[<p>But the official documentation says:</p>
<p>vmkcore – A vmkcore partition is required to store core dumps for<br />
troubleshooting. VMware does not support ESX Server host configurations<br />
without a vmkcore partition</p>
<p>Install Guide , page 91</p>
<p>I&#8217;m getting confused&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: George</title>
		<link>http://www.yellow-bricks.com/2008/10/23/partitioning-your-esx/comment-page-1/#comment-1570</link>
		<dc:creator>George</dc:creator>
		<pubDate>Thu, 06 Nov 2008 14:32:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.yellow-bricks.com/?p=709#comment-1570</guid>
		<description>Then , that trainer in the VI3 I&amp;C had no clue about ESX...  Thanks!</description>
		<content:encoded><![CDATA[<p>Then , that trainer in the VI3 I&amp;C had no clue about ESX&#8230;  Thanks!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
