I made an effort to get a Fedora 19 image running in EC2 this week, and in
the end, I undid a couple of the recent changes to make it work for me.
Here's a brief overview of what I did:
1) appliance-creator was giving me an error when the "part" line of the
kickstart had no "ondisk" option, so I added "--ondisk xvda". This
shouldn't be needed, but it helped in my case.
2) I also commented out the "Zeroing out empty space" postinstall stuff,
because it drastically increases the image build time for not much benefit,
3) To build the image, I ran "appliance-creator --name f19-x86_64
4) I compressed the image for transport to ec2: tar -cSzf f19.tgz
5) I launched an F18 instance and attached a new 10 GB volume to it
6) I copied the tarball (which was only about 240 MB) to the instance and
extracted with "tar xSzf f19.tgz" to preserve sparseness.
7) I tried dumping the whole disk onto the volume, but I had issues with
that, so in the end I just dumped the filesystem into the volume instead:
losetup -f --show f19-x86_64/f19-x86_64-xvda.raw
kpartx -a /dev/loop0
dd if=/dev/mapper/loop0p1 bs=1M of=/dev/xvdf
8) Because I was using the filesystem instead of the whole disk, I had to
change "(hd0,0)" to "(hd0)" in grub.conf
After some failed boot attempts, I did a couple of other things:
9) I removed the "splashimage" line from grub.conf, because it's certainly
not useful and could be harmful
10) I copied /boot/grub/grub.conf to /boot/grub/menu.lst, because I don't
know whether pvgrub in EC2 reliably reads both files (it's supposed to).
And finally, I mounted the volume, took a snapshot, and registered with:
euca-register -s snap-95070fcf --kernel aki-825ea7eb -d "Fedora 19 Alpha"
-n "fedora19-20130515.2" --architecture x86_64
I'm sure I did some extra steps here, and that this is not exactly how Matt
and Dennis intend for images to be deployed, but absent any detailed
instructions from them, I hope this will prove to be a useful starting
point for people. Matt and Dennis, feel free to tell us about everything
I've done wrong here. :-)
On Mon, May 13, 2013 at 2:57 PM, Krishna Raman <kraman(a)gmail.com> wrote:
On May 10, 2013, at 2:48 PM, Ricardo Arguello <ricardo.arguello(a)gmail.com>
On Fri, May 10, 2013 at 3:17 PM, Ricardo Arguello <
> You can build them yourself:
Using these commands:
# appliance-creator --name f19-x86_64 --config=fedora-19-x86_64-ec2.ks
# qemu-img convert -f raw -c -O qcow2 f19-x86_64-sda.raw
Thanks for the steps but I am still lost.
What do I do once I have the qcow2 image? Can you point me to the location
docs on Fedora site which will help me get started on ec2?
I only see a mention of BoxGrinder which doesnt seem to support anything
On Fri, May 10, 2013 at 12:36 PM, Juerg Haefliger <juergh(a)gmail.com>wrote:
> On Fri, May 10, 2013 at 5:22 PM, Krishna Raman <kraman(a)gmail.com> wrote:
> > Can I get a hold of the test image?
> I'd be interested too.
> > -kr
> > On May 10, 2013 8:20 AM, "Matthew Miller"
> >> On Thu, May 09, 2013 at 04:18:45PM -0700, Krishna Raman wrote:
> >> > Wondering if there is a Fedora 19 AMI available on EC2 US-East-1?
> >> > I would like to start building and testing OpenShift Origin on there
> >> > possible.
> >> There were some testing ones but we didn't announce an official one,
> >> we do plan to do for the beta.
> >> --
> >> Matthew Miller ☁☁☁ Fedora Cloud Architect ☁☁☁
> >> <mattdm(a)fedoraproject.org>
> >> _______________________________________________
> >> cloud mailing list
> >> cloud(a)lists.fedoraproject.org
> >> https://admin.fedoraproject.org/mailman/listinfo/cloud
> > _______________________________________________
> > cloud mailing list
> > cloud(a)lists.fedoraproject.org
> > https://admin.fedoraproject.org/mailman/listinfo/cloud
> cloud mailing list
cloud mailing list
cloud mailing list