<?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: The VMware ESXi 4 64MB Hypervisor Challenge</title>
	<atom:link href="http://www.vcritical.com/2009/08/the-vmware-esxi-4-64mb-hypervisor-challenge/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.vcritical.com/2009/08/the-vmware-esxi-4-64mb-hypervisor-challenge/</link>
	<description>Informed Virtualization Criticism</description>
	<lastBuildDate>Wed, 24 Apr 2013 06:27:36 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
	<item>
		<title>By: juan</title>
		<link>http://www.vcritical.com/2009/08/the-vmware-esxi-4-64mb-hypervisor-challenge/#comment-10855</link>
		<dc:creator>juan</dc:creator>
		<pubDate>Tue, 18 May 2010 08:21:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.vcritical.com/?p=1468#comment-10855</guid>
		<description><![CDATA[Hello

Here is another way to do it:
I use the fantastic boot loader grub4dos and boot ESXi with this entry:

title Vmware ESXi4
find --set-root /grldr
kernel /ESX4/vmkboot.gz
module /ESX4/vmk.gz
module /ESX4/sys.vgz
module /ESX4/cim.vgz
module /ESX4/oem.tgz
module /ESX4/license.tgz
module /ESX4/mod.tgz

It boot from a pendrive with NTFS filesystem.
You only need to install grub4dos on the pendrive 
and take these files from the ESXi dd image.
This way you can boot ESXi, Windows, Linux, etc. from ONE pendrive.
Greetings!]]></description>
		<content:encoded><![CDATA[<p>Hello</p>
<p>Here is another way to do it:<br />
I use the fantastic boot loader grub4dos and boot ESXi with this entry:</p>
<p>title Vmware ESXi4<br />
find &#8211;set-root /grldr<br />
kernel /ESX4/vmkboot.gz<br />
module /ESX4/vmk.gz<br />
module /ESX4/sys.vgz<br />
module /ESX4/cim.vgz<br />
module /ESX4/oem.tgz<br />
module /ESX4/license.tgz<br />
module /ESX4/mod.tgz</p>
<p>It boot from a pendrive with NTFS filesystem.<br />
You only need to install grub4dos on the pendrive<br />
and take these files from the ESXi dd image.<br />
This way you can boot ESXi, Windows, Linux, etc. from ONE pendrive.<br />
Greetings!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eric Gray</title>
		<link>http://www.vcritical.com/2009/08/the-vmware-esxi-4-64mb-hypervisor-challenge/#comment-10800</link>
		<dc:creator>Eric Gray</dc:creator>
		<pubDate>Fri, 16 Apr 2010 14:09:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.vcritical.com/?p=1468#comment-10800</guid>
		<description><![CDATA[Patrick,

Please keep in mind that this is just a proof-of-concept and not intended for real-world use.  The point was to demonstrate that ESXi is very small despite the &quot;huge&quot; 1GB flash requirement.  Given the difficulty in even finding a sub-1GB USB flash device these days, there is not much value in getting it to run on 64MB.

When I put together the prototype, I stopped when I hit on a repeatable formula that works.  I&#039;m sure there are ways to optimize, feel free to tinker around and post your findings if you come up with a cool solution.

Thanks for reading VCritical.

Eric]]></description>
		<content:encoded><![CDATA[<p>Patrick,</p>
<p>Please keep in mind that this is just a proof-of-concept and not intended for real-world use.  The point was to demonstrate that ESXi is very small despite the &#8220;huge&#8221; 1GB flash requirement.  Given the difficulty in even finding a sub-1GB USB flash device these days, there is not much value in getting it to run on 64MB.</p>
<p>When I put together the prototype, I stopped when I hit on a repeatable formula that works.  I&#8217;m sure there are ways to optimize, feel free to tinker around and post your findings if you come up with a cool solution.</p>
<p>Thanks for reading VCritical.</p>
<p>Eric</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: patrick</title>
		<link>http://www.vcritical.com/2009/08/the-vmware-esxi-4-64mb-hypervisor-challenge/#comment-10799</link>
		<dc:creator>patrick</dc:creator>
		<pubDate>Fri, 16 Apr 2010 12:09:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.vcritical.com/?p=1468#comment-10799</guid>
		<description><![CDATA[can it use the same way to copy the file to sd*4?
mount -o loop,offset=$((32*512)) VMware-VMvisor-big-175625-x86_64.dd tmp/]]></description>
		<content:encoded><![CDATA[<p>can it use the same way to copy the file to sd*4?<br />
mount -o loop,offset=$((32*512)) VMware-VMvisor-big-175625-x86_64.dd tmp/</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: patrick</title>
		<link>http://www.vcritical.com/2009/08/the-vmware-esxi-4-64mb-hypervisor-challenge/#comment-10796</link>
		<dc:creator>patrick</dc:creator>
		<pubDate>Fri, 16 Apr 2010 12:01:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.vcritical.com/?p=1468#comment-10796</guid>
		<description><![CDATA[the sd*4 seems large the 1.5M and the data inside it seems less than 512K?
dd if=VMware-VMvisor-big-175625-x86_64.dd of=esxi-boot-part skip=32 count=3000 should not contain all the sd*4? It is work? 
if the data is less than 500K, can I use dd if=VMware-VMvisor-big-175625-x86_64.dd of=esxi-boot-part skip=32 count=1000 ?
has you test the VMware-VMvisor-Installer-4.0.0.Update01-208167.x86_64.iso, is it can store in a 64M disk?]]></description>
		<content:encoded><![CDATA[<p>the sd*4 seems large the 1.5M and the data inside it seems less than 512K?<br />
dd if=VMware-VMvisor-big-175625-x86_64.dd of=esxi-boot-part skip=32 count=3000 should not contain all the sd*4? It is work?<br />
if the data is less than 500K, can I use dd if=VMware-VMvisor-big-175625-x86_64.dd of=esxi-boot-part skip=32 count=1000 ?<br />
has you test the VMware-VMvisor-Installer-4.0.0.Update01-208167.x86_64.iso, is it can store in a 64M disk?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eric Gray</title>
		<link>http://www.vcritical.com/2009/08/the-vmware-esxi-4-64mb-hypervisor-challenge/#comment-10757</link>
		<dc:creator>Eric Gray</dc:creator>
		<pubDate>Wed, 14 Apr 2010 16:00:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.vcritical.com/?p=1468#comment-10757</guid>
		<description><![CDATA[Patrick, you could use a 1GB USB as an intermediate source as you suggest.  That&#039;s initially how I approached this, but figured it would be easier to not require two different USB sticks.

Eric]]></description>
		<content:encoded><![CDATA[<p>Patrick, you could use a 1GB USB as an intermediate source as you suggest.  That&#8217;s initially how I approached this, but figured it would be easier to not require two different USB sticks.</p>
<p>Eric</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: patrick</title>
		<link>http://www.vcritical.com/2009/08/the-vmware-esxi-4-64mb-hypervisor-challenge/#comment-10754</link>
		<dc:creator>patrick</dc:creator>
		<pubDate>Tue, 13 Apr 2010 10:09:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.vcritical.com/?p=1468#comment-10754</guid>
		<description><![CDATA[can it install on a usb flash, then use dd to backup the sda4 and sda5, 

and then use this 2 patition backup file to restore to a 64MB flash with your fdisk script?]]></description>
		<content:encoded><![CDATA[<p>can it install on a usb flash, then use dd to backup the sda4 and sda5, </p>
<p>and then use this 2 patition backup file to restore to a 64MB flash with your fdisk script?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: VAroon</title>
		<link>http://www.vcritical.com/2009/08/the-vmware-esxi-4-64mb-hypervisor-challenge/#comment-9612</link>
		<dc:creator>VAroon</dc:creator>
		<pubDate>Thu, 28 Jan 2010 15:02:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.vcritical.com/?p=1468#comment-9612</guid>
		<description><![CDATA[Can this work on a normal laptop for testing purposes.But with no CPU AMD-V]]></description>
		<content:encoded><![CDATA[<p>Can this work on a normal laptop for testing purposes.But with no CPU AMD-V</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mark Richards</title>
		<link>http://www.vcritical.com/2009/08/the-vmware-esxi-4-64mb-hypervisor-challenge/#comment-9566</link>
		<dc:creator>Mark Richards</dc:creator>
		<pubDate>Fri, 22 Jan 2010 07:40:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.vcritical.com/?p=1468#comment-9566</guid>
		<description><![CDATA[I understand it&#039;s meant as a demo but a demo that doesn&#039;t really work isn&#039;t nearly as impressive as one that doe. In my case I have lots of 256 MB USB keys I&#039;d like to give to people to get them to try esxi- but it&#039;s a lot less useful if the config doesn&#039;t get saved.

I&#039;m not really sure why it wouldn&#039;t save the config- everything is definitely there- esxi boots- vm&#039;s run- etc. It just seems like the memory filesystem isn&#039;t being written out to disk.

I actually had a 256MB key so I went a little further with my test: I set up a partition for VMWare tools and installed those to the key (I left out Vsphere client as I can download and install the latest version from vmware&#039;s site easily enough and at 111MB it would have taken up too much room). The tools worked fine and let me install to the vm&#039;s I tested.

I&#039;d still like to figure out the save issue if anyone has any ideas.]]></description>
		<content:encoded><![CDATA[<p>I understand it&#8217;s meant as a demo but a demo that doesn&#8217;t really work isn&#8217;t nearly as impressive as one that doe. In my case I have lots of 256 MB USB keys I&#8217;d like to give to people to get them to try esxi- but it&#8217;s a lot less useful if the config doesn&#8217;t get saved.</p>
<p>I&#8217;m not really sure why it wouldn&#8217;t save the config- everything is definitely there- esxi boots- vm&#8217;s run- etc. It just seems like the memory filesystem isn&#8217;t being written out to disk.</p>
<p>I actually had a 256MB key so I went a little further with my test: I set up a partition for VMWare tools and installed those to the key (I left out Vsphere client as I can download and install the latest version from vmware&#8217;s site easily enough and at 111MB it would have taken up too much room). The tools worked fine and let me install to the vm&#8217;s I tested.</p>
<p>I&#8217;d still like to figure out the save issue if anyone has any ideas.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kevin Brooksby</title>
		<link>http://www.vcritical.com/2009/08/the-vmware-esxi-4-64mb-hypervisor-challenge/#comment-9565</link>
		<dc:creator>Kevin Brooksby</dc:creator>
		<pubDate>Fri, 22 Jan 2010 07:08:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.vcritical.com/?p=1468#comment-9565</guid>
		<description><![CDATA[Nice work Eric. Great post. Used this method (a la a bit modified to extract the VMware-VMvisor.dd.bz2 on a Linux box) and I also used a 128 MB flash stick I had laying around.  I must admit this is very cool to prove the core thin hypervisor is indeed a very small footprint and I appreciate your explanations in your two-part articles explaining the use of the other partitions.  Doesn&#039;t seem to load as quick (but this may be because it is a 1.x USB device and not 2.x complaint like most of my 1-2 GB ESXi usb sticks I test with)  but all functionality is there minus of course tools/vSphere client (web interface give a cute blank page as I assume it is missing tomcat portlet)/etc.  Booted up a xppro VM that I recently installed the openssh for windows package on for test I was doing for a friend (I know it seems so bastardized) and yanked the 128MB ESXi u1 stick and to my immediate surprise my ssh session into that xppro box stayed running as did the VM.  Must have been because the ESXi hypervisor is loaded into memory.  Powered off my laptop running ESXi that joins my two way cluster and approx 45 seconds later HA fired the VM back up on esx2 node.  Very cool indeed!  Also noted the settings do not stick but that is no surprise with this stripped/slim ESXi install. 

Keep up the good work!]]></description>
		<content:encoded><![CDATA[<p>Nice work Eric. Great post. Used this method (a la a bit modified to extract the VMware-VMvisor.dd.bz2 on a Linux box) and I also used a 128 MB flash stick I had laying around.  I must admit this is very cool to prove the core thin hypervisor is indeed a very small footprint and I appreciate your explanations in your two-part articles explaining the use of the other partitions.  Doesn&#8217;t seem to load as quick (but this may be because it is a 1.x USB device and not 2.x complaint like most of my 1-2 GB ESXi usb sticks I test with)  but all functionality is there minus of course tools/vSphere client (web interface give a cute blank page as I assume it is missing tomcat portlet)/etc.  Booted up a xppro VM that I recently installed the openssh for windows package on for test I was doing for a friend (I know it seems so bastardized) and yanked the 128MB ESXi u1 stick and to my immediate surprise my ssh session into that xppro box stayed running as did the VM.  Must have been because the ESXi hypervisor is loaded into memory.  Powered off my laptop running ESXi that joins my two way cluster and approx 45 seconds later HA fired the VM back up on esx2 node.  Very cool indeed!  Also noted the settings do not stick but that is no surprise with this stripped/slim ESXi install. </p>
<p>Keep up the good work!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eric Gray</title>
		<link>http://www.vcritical.com/2009/08/the-vmware-esxi-4-64mb-hypervisor-challenge/#comment-9557</link>
		<dc:creator>Eric Gray</dc:creator>
		<pubDate>Fri, 22 Jan 2010 00:29:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.vcritical.com/?p=1468#comment-9557</guid>
		<description><![CDATA[This is an exercise to show that the core functionality of ESXi is fully contained in 64MB and not 1GB as some have claimed.]]></description>
		<content:encoded><![CDATA[<p>This is an exercise to show that the core functionality of ESXi is fully contained in 64MB and not 1GB as some have claimed.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
