<?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: How to create an ebs image from an existing ec2 instance</title>
	<atom:link href="http://aws-musings.com/how-to-create-an-ebs-image-from-an-existing-ec2-instance/feed/" rel="self" type="application/rss+xml" />
	<link>http://aws-musings.com/how-to-create-an-ebs-image-from-an-existing-ec2-instance/</link>
	<description>Cloud computing, EC2, RDS, SQS, S3, Java...</description>
	<lastBuildDate>Mon, 06 Dec 2010 13:41:55 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Alex</title>
		<link>http://aws-musings.com/how-to-create-an-ebs-image-from-an-existing-ec2-instance/comment-page-1/#comment-21</link>
		<dc:creator>Alex</dc:creator>
		<pubDate>Tue, 12 Jan 2010 00:27:47 +0000</pubDate>
		<guid isPermaLink="false">http://aws-musings.com/?p=63#comment-21</guid>
		<description>Just wanted to point you guys here:
http://developer.amazonwebservices.com/connect/thread.jspa?threadID=39358&amp;start=15&amp;tstart=0
If you combine both these instructions, it results in a cleaner setup.  Ie. use rsync instead of dd.  This also allows you to potentially use another FS instead of ext3.  I&#039;m tryng it out with XFS right now, as I need that FS.  I don&#039;t know why Amazon is so fixated in ext3.  It snapshots like crap.</description>
		<content:encoded><![CDATA[<p>Just wanted to point you guys here:<br />
<a href="http://developer.amazonwebservices.com/connect/thread.jspa?threadID=39358&#038;start=15&#038;tstart=0" rel="nofollow">http://developer.amazonwebservices.com/connect/thread.jspa?threadID=39358&#038;start=15&#038;tstart=0</a></p>
<p>If you combine both these instructions, it results in a cleaner setup.  Ie. use rsync instead of dd.  This also allows you to potentially use another FS instead of ext3.  I&#8217;m tryng it out with XFS right now, as I need that FS.  I don&#8217;t know why Amazon is so fixated in ext3.  It snapshots like crap.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Klaas Eikelboom</title>
		<link>http://aws-musings.com/how-to-create-an-ebs-image-from-an-existing-ec2-instance/comment-page-1/#comment-20</link>
		<dc:creator>Klaas Eikelboom</dc:creator>
		<pubDate>Mon, 11 Jan 2010 12:42:40 +0000</pubDate>
		<guid isPermaLink="false">http://aws-musings.com/?p=63#comment-20</guid>
		<description>I needed to use the -kernel and -ramdisk parameters to get it working. Same problem as Coert, without I could not connect to the ami.  I copied them from the source ami. My assumption is that the parameters must be the same, so default works for most cases but not for every case.
Thanks for the blog post. It saved me a lot of time.</description>
		<content:encoded><![CDATA[<p>I needed to use the -kernel and -ramdisk parameters to get it working. Same problem as Coert, without I could not connect to the ami.  I copied them from the source ami. My assumption is that the parameters must be the same, so default works for most cases but not for every case.<br />
Thanks for the blog post. It saved me a lot of time.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: admin</title>
		<link>http://aws-musings.com/how-to-create-an-ebs-image-from-an-existing-ec2-instance/comment-page-1/#comment-11</link>
		<dc:creator>admin</dc:creator>
		<pubDate>Thu, 31 Dec 2009 05:23:20 +0000</pubDate>
		<guid isPermaLink="false">http://aws-musings.com/?p=63#comment-11</guid>
		<description>You are right, mkfs is not necessary as dd is a block by block copy of the source disk.</description>
		<content:encoded><![CDATA[<p>You are right, mkfs is not necessary as dd is a block by block copy of the source disk.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dennis</title>
		<link>http://aws-musings.com/how-to-create-an-ebs-image-from-an-existing-ec2-instance/comment-page-1/#comment-10</link>
		<dc:creator>Dennis</dc:creator>
		<pubDate>Thu, 31 Dec 2009 04:12:36 +0000</pubDate>
		<guid isPermaLink="false">http://aws-musings.com/?p=63#comment-10</guid>
		<description>Why would you mkfs on the block device in order to just dd over it? That step makes no sense</description>
		<content:encoded><![CDATA[<p>Why would you mkfs on the block device in order to just dd over it? That step makes no sense</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: admin</title>
		<link>http://aws-musings.com/how-to-create-an-ebs-image-from-an-existing-ec2-instance/comment-page-1/#comment-8</link>
		<dc:creator>admin</dc:creator>
		<pubDate>Tue, 29 Dec 2009 16:30:07 +0000</pubDate>
		<guid isPermaLink="false">http://aws-musings.com/?p=63#comment-8</guid>
		<description>I don&#039;t think the option -kernel and -ramdisk are required. I think they have default values. If you don&#039;t want to use the default value, then you should specify it.</description>
		<content:encoded><![CDATA[<p>I don&#8217;t think the option -kernel and -ramdisk are required. I think they have default values. If you don&#8217;t want to use the default value, then you should specify it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ecelis</title>
		<link>http://aws-musings.com/how-to-create-an-ebs-image-from-an-existing-ec2-instance/comment-page-1/#comment-7</link>
		<dc:creator>ecelis</dc:creator>
		<pubDate>Tue, 29 Dec 2009 11:13:26 +0000</pubDate>
		<guid isPermaLink="false">http://aws-musings.com/?p=63#comment-7</guid>
		<description>This is great, thank you.
BTW I didn&#039;t need to add -kernel and -ramdisk options to ec2reg, I created the EBS from a CentOS 5 i386 community contributed AMI.
And image type for i386 is x86_86 or i386, or you can leve this option out as i386 is the default.</description>
		<content:encoded><![CDATA[<p>This is great, thank you. </p>
<p>BTW I didn&#8217;t need to add -kernel and -ramdisk options to ec2reg, I created the EBS from a CentOS 5 i386 community contributed AMI.</p>
<p>And image type for i386 is x86_86 or i386, or you can leve this option out as i386 is the default.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: alvin</title>
		<link>http://aws-musings.com/how-to-create-an-ebs-image-from-an-existing-ec2-instance/comment-page-1/#comment-6</link>
		<dc:creator>alvin</dc:creator>
		<pubDate>Tue, 29 Dec 2009 11:00:40 +0000</pubDate>
		<guid isPermaLink="false">http://aws-musings.com/?p=63#comment-6</guid>
		<description>thanks for the writeup, just tried it out and it worked sweetly. How important are the -kernel and -ramdisk options mentioned by Coert?</description>
		<content:encoded><![CDATA[<p>thanks for the writeup, just tried it out and it worked sweetly. How important are the -kernel and -ramdisk options mentioned by Coert?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Coert</title>
		<link>http://aws-musings.com/how-to-create-an-ebs-image-from-an-existing-ec2-instance/comment-page-1/#comment-3</link>
		<dc:creator>Coert</dc:creator>
		<pubDate>Tue, 22 Dec 2009 16:52:13 +0000</pubDate>
		<guid isPermaLink="false">http://aws-musings.com/?p=63#comment-3</guid>
		<description>Thanks for the excellent explanation ! I just had to add the --kernel aki-####### and --ramdisk ari-####### parameters to the ec2reg command. Without them, the ami did start but was not accessible.</description>
		<content:encoded><![CDATA[<p>Thanks for the excellent explanation ! I just had to add the &#8211;kernel aki-####### and &#8211;ramdisk ari-####### parameters to the ec2reg command. Without them, the ami did start but was not accessible.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

