On 10/07/2011 06:03 AM, Marek Goldmann wrote: > Sean, > > You need to edit /boot/grub/menu.lst file after you upgrade the kernel, /boot/grub/grub.conf is not used on EC2 at all (pvgrub). > > --Marek > > On 5 paź 2011, at 03:04, sean darcy wrote: >> >> 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 >> If I install kernel-2.6.40-6, edit menu.lst to point to the new kernel, and then reboot, I can not ssh into the instance. The Management Console show this instance running, but it's unreachable. Same thing if I create a new ami image. Odd. sean _______________________________________________ cloud mailing list cloud@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/cloud
