Comment 0 for bug 607242

For maverick UEC images, there will be 2 "kernels" shipped
a.) linux kernel (as copied from inside image /boot)
b.) grub boot loader. This is so that a guest can service its own kernel ([1])

Due to a bug in kvm on 10.04 (bug 598649) we will not be able to boot grub images when the host is Lucid. However, on Maverick hosts, we will want to boot the grub kernel.

What this means is that in one way or another, we will need for the image store proxy to register the grub kernel when the host is maverick, and the linux kernel when the host is lucid (or earlier).

One possible work around with this is to populate the image store with 2 images and leave it up to the user to select the right one:
 - Ubuntu Maverick Image (for Maverick Hosts)
 - Ubuntu Maverick Image (for Lucid or older hosts)

--
[1] https://blueprints.launchpad.net/ubuntu/+spec/server-maverick-cloud-kernel-upgrades

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: python-image-store-proxy 1.0.4-0ubuntu2
ProcVersionSignature: User Name 2.6.32-305.9-ec2 2.6.32.11+drm33.2
Uname: Linux 2.6.32-305-ec2 i686
Architecture: i386
Date: Mon Jul 19 13:38:18 2010
Ec2AMI: ami-e8f31881
Ec2AMIManifest: ubuntu-images-testing-us/ubuntu-maverick-daily-i386-server-20100718.manifest.xml
Ec2AvailabilityZone: us-east-1c
Ec2InstanceType: m1.small
Ec2Kernel: aki-407d9529
Ec2Ramdisk: unavailable
PackageArchitecture: all
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: image-store-proxy