boxgrinder vs. AMC "create image"

[sean darcy]

On 10/04/2011 03:56 PM, Max Spevack wrote:
> On Tue, 4 Oct 2011, sean darcy wrote:
>
>> I see on the AWS Management Console an instance action "create image".
>> Would this be a coward's way out?
>
> It certainly seems that way.
>
> Try it:
>
> Launch an AMI.
>
> Modify the instance in some way -- add packages using yum, enable it as
> a webserver, etc.
>
> Go through that create image workflow in the console.  It will give you
> a private AMI ID for a new AMI that you own.
>
> Then launch more of that instance, and see if it is in the same state as
> the original.
>
> I haven't tried it, but it seems like that is the way it will work.
>
> --Max

Not quite OT, but I've yum upgrade'd the F15 ami. That installed 
kernel-PAE-2.6.40.4-5.fc15.i686. Rebooted - still 
2.6.38.8-32.fc15.i686.PAE. Then fixed grub to boot 2.6.40. Reboot. Still 
2.6.38.

cat /boot/grub/grub.conf
default=0
fallback=1
timeout=5
splashimage=(hd0,0)/boot/grub/splash.xpm.gz
hiddenmenu

title Fedora-15 (2.6.40.4-5.fc15.i686.PAE)
         root (hd0,0)
         kernel /boot/vmlinuz-2.6.40.4-5.fc15.i686.PAE ro 
root=LABEL=79d3d2d4
         initrd /boot/initramfs-2.6.40.4-5.fc15.i686.PAE.img

title Fedora-15 (2.6.38.8-32.fc15.i686.PAE)
         root (hd0,0)
         kernel /boot/vmlinuz-2.6.38.8-32.fc15.i686.PAE ro 
root=LABEL=79d3d2d4
         initrd /boot/initramfs-2.6.38.8-32.fc15.i686.PAE.img


Does aws actually reboot the instance? If not, how do you (can you) 
upgrade the kernel? If aws does really reboot, what am I doing wrong?

sean