I just uploaded to canonical-testing-us:
aki-80a84be9 ubuntu-kernel-2.6.31-300.3-ec2-i386.manifest.xml
aki-8aa84be3 ubuntu-kernel-2.6.31-300.3-ec2-x86_64.manifest.xml
ari-90a84bf9 ubuntu-ramdisk-2.6.31-300.3-ec2-i386.manifest.xml
ari-8ea84be7 ubuntu-ramdisk-2.6.31-300.3-ec2-x86_64.manifest.xml
I then booted the i386 build karmic-i386-20090926.1 (ami-28a34041) with:
run-instances ami-28a34041 --kernel aki-80a84be9 --ramdisk ari-90a84bf9
The happy result is we have console output again, including the ssh keys.
So, with linux-image-2.6.31-300-ec2 at version 2.6.31-300.3,
a.) this should be fixed in beta
b.) There is no ec2-init task required
I just uploaded to canonical- testing- us: kernel- 2.6.31- 300.3-ec2- i386.manifest. xml kernel- 2.6.31- 300.3-ec2- x86_64. manifest. xml ramdisk- 2.6.31- 300.3-ec2- i386.manifest. xml ramdisk- 2.6.31- 300.3-ec2- x86_64. manifest. xml
aki-80a84be9 ubuntu-
aki-8aa84be3 ubuntu-
ari-90a84bf9 ubuntu-
ari-8ea84be7 ubuntu-
I then booted the i386 build karmic- i386-20090926. 1 (ami-28a34041) with:
run-instances ami-28a34041 --kernel aki-80a84be9 --ramdisk ari-90a84bf9
The happy result is we have console output again, including the ssh keys.
So, with linux-image- 2.6.31- 300-ec2 at version 2.6.31-300.3,
a.) this should be fixed in beta
b.) There is no ec2-init task required