Recent AWS Customer Success Stories & Videos

More AWS Customer Success Stories...

« Enhanced CloudFront Logs, Now With Query Strings | Main | What's New in AWS Security: Vulnerability Reporting and Penetration Testing »


TrackBack URL for this entry:

Listed below are links to weblogs that reference Use Your Own Kernel with Amazon EC2:


Feed You can follow this conversation by subscribing to the comment feed for this post.


I'd like to note that the Official Ubuntu Images for 10.10 will use this functionality.
Our daily builds [1] will soon begin registering with the pv-grub aki by default. For now, starting with 20100417.1 you can simply launch with the appropriate --kernel to get boot with grub.

For example:
ec2-run-instances --kernel aki-407d9529 ami-dc957eb5 --key mykey

That is for us-east-1 i386 grub loader, and ebs/ubuntu-maverick-daily-i386-server-20100714.1 .
To use other arch/regions you'll need to specify the appropriate aki.


I forgot to add a link for '1' above:

Miguel Landaeta

This is also working with upcoming Debian 6.0 and it should be working with current Debian stable 5.0. You just have to:

* Indicate in /boot/grub/menu.lst root=/dev/xvda1 as the root device of the instance.
* Bundle your image with linux-image-2.6-686-bigmem and grub-legacy packages installed.


Since opensolaris is competely dead Amazon really should provide a solution to run FreeBSD systems. This shouldn't be that hard to work on !

Zeno Davatz

What about running JFS on /root is that possible? It seems that if you run ext3 on /root then you very quickly run out of inodes. I guess this is a ext3 problem. So I would love to know how to put a JFS on /root - boot can have an ext2, 3 or 4 no problem. But root should really get a JFS.


A lot of ppl out there are trying to make FreeBSD run on EC2 (I thought that Amazon valued customer input, on that one we've been waiting for 2 years now to run FreeBSD on EC2, a move from the team on this subject would really be appreciated...).

But it fails ; you can check this article (I'm not the author), a the end he describes fails attempts using FreeBSD on EC2


We have been successful in booting a custom patched kernel (cluster filesystem patches)for centos 5.5. PVgrub based kernels are damn useful !!
Here is the link talking about the steps we followed:



1. I have installed slackware14.0 (64bit) in my local machine.

2. I have created the 10 gb image space in slackware machine using below command.
(dd if=/dev/zero of=slack14.img bs=1M count=10075). and mount the image in slack14.img.
mount -o loop slack14.img /mnt/slack1464.

3. I have format the image (slack14.img)

4. I have installed the custom package through ruby script. The custom package for
installed without any error.

After that While login the mounting image (/mnt/slack1464).

root@slack1464bit:~# chroot /mnt/slack1464
chroot: failed to run command ‘/bin/bash’: No such file or directory

earlier I have created the .img image in (slackware13.1 & 13.37) without any error.

But I am getting the error in Slackware14.0 64bit only.

Thanks for advance.


The comments to this entry are closed.

Featured Events

The AWS Report

Brought to You By

Jeff Barr (@jeffbarr):

Jinesh Varia (@jinman):

Email Subscription

Enter your email address:

Delivered by FeedBurner

April 2014

Sun Mon Tue Wed Thu Fri Sat
    1 2 3 4 5
6 7 8 9 10 11 12
13 14 15 16 17 18 19
20 21 22 23 24 25 26
27 28 29 30