<?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: If VMware ESXi 4 is so small, why is it so big?</title>
	<atom:link href="http://www.vcritical.com/2009/08/if-vmware-esxi-4-is-so-small-why-is-it-so-big/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.vcritical.com/2009/08/if-vmware-esxi-4-is-so-small-why-is-it-so-big/</link>
	<description>Informed Virtualization Criticism</description>
	<lastBuildDate>Mon, 15 Mar 2010 09:29:07 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Why Should I Install ESXi instead of ESX? &#171; DeinosCloud</title>
		<link>http://www.vcritical.com/2009/08/if-vmware-esxi-4-is-so-small-why-is-it-so-big/#comment-9575</link>
		<dc:creator>Why Should I Install ESXi instead of ESX? &#171; DeinosCloud</dc:creator>
		<pubDate>Fri, 22 Jan 2010 13:01:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.vcritical.com/?p=1439#comment-9575</guid>
		<description>[...] too much. Thus if we could get rid of the COS, we end up with a smaller footprint, in this case just a bit less than 64MB instead of several [...]</description>
		<content:encoded><![CDATA[<p>[...] too much. Thus if we could get rid of the COS, we end up with a smaller footprint, in this case just a bit less than 64MB instead of several [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eric Gray</title>
		<link>http://www.vcritical.com/2009/08/if-vmware-esxi-4-is-so-small-why-is-it-so-big/#comment-9418</link>
		<dc:creator>Eric Gray</dc:creator>
		<pubDate>Thu, 07 Jan 2010 15:47:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.vcritical.com/?p=1439#comment-9418</guid>
		<description>Thanks, Simon. Glad you found it useful.

Eric</description>
		<content:encoded><![CDATA[<p>Thanks, Simon. Glad you found it useful.</p>
<p>Eric</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Simon Seagrave</title>
		<link>http://www.vcritical.com/2009/08/if-vmware-esxi-4-is-so-small-why-is-it-so-big/#comment-9415</link>
		<dc:creator>Simon Seagrave</dc:creator>
		<pubDate>Thu, 07 Jan 2010 00:41:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.vcritical.com/?p=1439#comment-9415</guid>
		<description>Wow, great article Eric - can&#039;t believe I haven&#039;t read it before now.  So many people I know get confused when they see the ESXi install consuming more than the actual hypervisor size of 32/60MB.

Keep up the good work.

Cheers,


Simon
www.techhead.co.uk</description>
		<content:encoded><![CDATA[<p>Wow, great article Eric &#8211; can&#8217;t believe I haven&#8217;t read it before now.  So many people I know get confused when they see the ESXi install consuming more than the actual hypervisor size of 32/60MB.</p>
<p>Keep up the good work.</p>
<p>Cheers,</p>
<p>Simon<br />
<a href="http://www.techhead.co.uk" rel="nofollow">http://www.techhead.co.uk</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Computer Troubleshooters &#124; VMWARE ESXi 4.0 Partitions on 1GB Flash drive or Hard Disk</title>
		<link>http://www.vcritical.com/2009/08/if-vmware-esxi-4-is-so-small-why-is-it-so-big/#comment-8136</link>
		<dc:creator>Computer Troubleshooters &#124; VMWARE ESXi 4.0 Partitions on 1GB Flash drive or Hard Disk</dc:creator>
		<pubDate>Fri, 02 Oct 2009 09:13:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.vcritical.com/?p=1439#comment-8136</guid>
		<description>[...] Take a look at this blog for details on what each partition contains:http://www.vcritical.com/2009/08/if-vmware-esxi-4-is-so-small-why-is-it-so-big/ [...]</description>
		<content:encoded><![CDATA[<p>[...] Take a look at this blog for details on what each partition contains:http://www.vcritical.com/2009/08/if-vmware-esxi-4-is-so-small-why-is-it-so-big/ [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: aharden</title>
		<link>http://www.vcritical.com/2009/08/if-vmware-esxi-4-is-so-small-why-is-it-so-big/#comment-7438</link>
		<dc:creator>aharden</dc:creator>
		<pubDate>Sat, 29 Aug 2009 12:18:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.vcritical.com/?p=1439#comment-7438</guid>
		<description>I would measure hypervisors&#039; storage footprints by comparing the amount of storage space they consume immediately after the default vendor-supported installation.  You spelled this out above for ESXi; I&#039;ll check the ESXi stick I have to confirm.  The ~1.5GB quote was from another blog article and it may have been more applicable to ESXi installed to a hard disk after an upgrade, which might retain more data from the previous install.  Because ESXi carves out 900MB to operate normally (based on your example), I consider that its storage footprint.  That is the number that should be compared against either the total space consumed by WS2008/Hyper-V installed files or, more accurately, against the default partitioning of the WS2008 Setup routine.</description>
		<content:encoded><![CDATA[<p>I would measure hypervisors&#8217; storage footprints by comparing the amount of storage space they consume immediately after the default vendor-supported installation.  You spelled this out above for ESXi; I&#8217;ll check the ESXi stick I have to confirm.  The ~1.5GB quote was from another blog article and it may have been more applicable to ESXi installed to a hard disk after an upgrade, which might retain more data from the previous install.  Because ESXi carves out 900MB to operate normally (based on your example), I consider that its storage footprint.  That is the number that should be compared against either the total space consumed by WS2008/Hyper-V installed files or, more accurately, against the default partitioning of the WS2008 Setup routine.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Twitter Trackbacks for VMware ESXi 4 disk footprint is 59MB &#124; VCritical [vcritical.com] on Topsy.com</title>
		<link>http://www.vcritical.com/2009/08/if-vmware-esxi-4-is-so-small-why-is-it-so-big/#comment-7435</link>
		<dc:creator>Twitter Trackbacks for VMware ESXi 4 disk footprint is 59MB &#124; VCritical [vcritical.com] on Topsy.com</dc:creator>
		<pubDate>Sat, 29 Aug 2009 03:04:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.vcritical.com/?p=1439#comment-7435</guid>
		<description>[...] VMware ESXi 4 disk footprint is 59MB &#124; VCritical  www.vcritical.com/2009/08/if-vmware-esxi-4-is-so-small-why-is-it-so-big &#8211; view page &#8211; cached  Although VMware ESXi 4 requires a 1GB flash device to install, the core hypervisor functionality is fully contained in less than 60MB. Most of the remaining space is for a downloadable vSphere Client or simply unused., Don&#039;t believe everything you read. &#8212; From the page [...]</description>
		<content:encoded><![CDATA[<p>[...] VMware ESXi 4 disk footprint is 59MB | VCritical  <a href="http://www.vcritical.com/2009/08/if-vmware-esxi-4-is-so-small-why-is-it-so-big" rel="nofollow">http://www.vcritical.com/2009/08/if-vmware-esxi-4-is-so-small-why-is-it-so-big</a> &ndash; view page &ndash; cached  Although VMware ESXi 4 requires a 1GB flash device to install, the core hypervisor functionality is fully contained in less than 60MB. Most of the remaining space is for a downloadable vSphere Client or simply unused., Don&#39;t believe everything you read. &mdash; From the page [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eric Gray</title>
		<link>http://www.vcritical.com/2009/08/if-vmware-esxi-4-is-so-small-why-is-it-so-big/#comment-7430</link>
		<dc:creator>Eric Gray</dc:creator>
		<pubDate>Fri, 28 Aug 2009 20:39:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.vcritical.com/?p=1439#comment-7430</guid>
		<description>Aharden, The installed size of ESXi is not 1.5GB.  Even if you count all of the guest OS tools and the downloadable vSphere Client, the size is still under 300MB.

What would be your recommendation on how to measure the footprint of a hypervisor?</description>
		<content:encoded><![CDATA[<p>Aharden, The installed size of ESXi is not 1.5GB.  Even if you count all of the guest OS tools and the downloadable vSphere Client, the size is still under 300MB.</p>
<p>What would be your recommendation on how to measure the footprint of a hypervisor?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: How to create and run VMware ESXi 4 on a 64MB USB flash drive &#124; VCritical</title>
		<link>http://www.vcritical.com/2009/08/if-vmware-esxi-4-is-so-small-why-is-it-so-big/#comment-7428</link>
		<dc:creator>How to create and run VMware ESXi 4 on a 64MB USB flash drive &#124; VCritical</dc:creator>
		<pubDate>Fri, 28 Aug 2009 19:29:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.vcritical.com/?p=1439#comment-7428</guid>
		<description>[...] PASS Syndication by Eric Gray &#124; No comments   In a previous article, I answered the question: If VMware ESXi 4 is so small, why is it so big? It&#8217;s quite clear now that the disk footprint of VMware ESXi 4 is less than 60MB.  But to [...]</description>
		<content:encoded><![CDATA[<p>[...] PASS Syndication by Eric Gray | No comments   In a previous article, I answered the question: If VMware ESXi 4 is so small, why is it so big? It&#8217;s quite clear now that the disk footprint of VMware ESXi 4 is less than 60MB.  But to [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: aharden</title>
		<link>http://www.vcritical.com/2009/08/if-vmware-esxi-4-is-so-small-why-is-it-so-big/#comment-7425</link>
		<dc:creator>aharden</dc:creator>
		<pubDate>Fri, 28 Aug 2009 15:09:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.vcritical.com/?p=1439#comment-7425</guid>
		<description>Eric, I think we&#039;re talking past one another.  The concentric circle picture on the &lt;a href=&quot;http://blogs.vmware.com/virtualreality/2009/08/our-position-on-hypervisor-footprints-patching-vulnerabilities-and-whatever-else-microsoft-wants-to-throw-into-a-blog-post.html&quot; rel=&quot;nofollow&quot;&gt;VMware blog post&lt;/a&gt; directly compares the ESXi hypervisor size (not the ESXi installed size of ~1.5GB) against the installed size of both Server Core and Full installs of WS2008 with Hyper-V.  It&#039;s not a fair comparison.

I feel I have to couch my response here - I&#039;m a Windows Server admin and huge VMware fan managing 20+ ESX hosts with no logical reason to switch gears to Hyper-V at this time.  MS and VMware are both guilty of inaccurate comparisons in this case.</description>
		<content:encoded><![CDATA[<p>Eric, I think we&#8217;re talking past one another.  The concentric circle picture on the <a href="http://blogs.vmware.com/virtualreality/2009/08/our-position-on-hypervisor-footprints-patching-vulnerabilities-and-whatever-else-microsoft-wants-to-throw-into-a-blog-post.html" rel="nofollow">VMware blog post</a> directly compares the ESXi hypervisor size (not the ESXi installed size of ~1.5GB) against the installed size of both Server Core and Full installs of WS2008 with Hyper-V.  It&#8217;s not a fair comparison.</p>
<p>I feel I have to couch my response here &#8211; I&#8217;m a Windows Server admin and huge VMware fan managing 20+ ESX hosts with no logical reason to switch gears to Hyper-V at this time.  MS and VMware are both guilty of inaccurate comparisons in this case.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: tonyr08</title>
		<link>http://www.vcritical.com/2009/08/if-vmware-esxi-4-is-so-small-why-is-it-so-big/#comment-7424</link>
		<dc:creator>tonyr08</dc:creator>
		<pubDate>Fri, 28 Aug 2009 14:29:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.vcritical.com/?p=1439#comment-7424</guid>
		<description>dang knew that about the licensing vmotion part, what I really meant to ask is does the in memory footprint stay the same wether vmotion is licensed or not? Or does another module load when it sees the valid license?</description>
		<content:encoded><![CDATA[<p>dang knew that about the licensing vmotion part, what I really meant to ask is does the in memory footprint stay the same wether vmotion is licensed or not? Or does another module load when it sees the valid license?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
