Scott, what would you think about this. This isn't really a backport but
would seem to do what I was thinking about inside a Xen domU. That
should get verified against a cloud-init deployment somewhere else
(which uses grub-legacy-ec2, if this exists). The one part that could
affect other places
Stefan,
Is there a reason to do this differently than in raring?
Basically, in raring we just added something like this:
+ *-generic)
+ # Starting with 12.10, -virtual was merged into -generic
+ dpkg --compare-versions ${ver_flavor%-generic} ge 3.4.0-3 return
0;;
to
Yeah, the problem, I realised, is that in Lucid we got the linux-ec2
packages installed right now. The plan is to change the dependency of
the meta-package to change from linux-image-*-ec2 to linux-
image-*-virtual (which is a generic-pae or server in fact). The problem
is that ec2 kernels have a
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1176159
Title:
[Lucid] Backport generic detection of Xen kernels for EC2
To manage notifications about this
** Changed in: cloud-init (Ubuntu)
Status: New = Triaged
** Changed in: cloud-init (Ubuntu)
Importance: Undecided = Medium
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
Ah, I probably confused that with the mechanism used to find dom0 usable
kernel. In the end this does not need to be overly clever at all. I
suppose it should be enough just to sort kernels by version and name.
Preferring the ec2 kernel name if there are multiple kernels with the
same version.
Stefan,
Sorry for being so delinquent in seeing this.
Ubuntu's update-grub-legacy-ec2, which is provided by grub-legacy-ec2, a
binary package created from cloud-init does not consider config of the kernel
at all.
The logic only considers kernel name and version.
we can surely patch
