[ubuntu-cloud] testing 651370

[Scott Moser]

On Wed, 8 Dec 2010, Jonathan Marston wrote:

> hello,
>
> a bug that affects the ability to boot the maverick image on certain instance types has been fixed in natty and backported to maverick, but apparently the fix gets reverted unless somebody confirms it fixed.
>

Hi,
   I verified https://bugs.launchpad.net/ubuntu/+source/linux/+bug/651370
just now.

> i'd be happy to test whether the fix allows booting into ec2 for m2
> instance types, but I lack the ability to spin a new maverick image to
> test with.

I put comments in the bug on exactly how I did it.  It did not include
spinning a new maverick image.

Just fyi, (and for others information also on this list).

 * In Maverick, you can install your own kernel (or one from -proposed)
   into an EC2 instance and reboot into it.  While this is the expectation
   with operating systems in 2010 (or even 15 years prior), it was not
   really possible on the EC2 platform until the end of the 10.04 cycle.

   I've almost got this function backported to lucid.  Daily builds
   (http://uec-images.ubuntu.com/server/lucid/) are currently being built
   from -proposed and have the needed parts, but they're not perfect due
   to bug 623609 still existing in lucid.

 * You can start an instance in one type, modify it, stop it, and then
   start it in another type.  This is how I installed the kernel from
   -proposed on a t1.micro instance and then bumped the size up.