Thank you fro the tip about using kernel-server-3.4.24-1.
After switching to this kernel, and rebuilding initrd, with the command:
mkinitrd-mkinitrd --with=xen-blkfront --with=xennet --with=xen-netfront initrd-3.4.24-server-2.mga2.img 3.4.24-server-2.mga2
It worked on Amazon EC2 and I have a nice Amanzon EC2 Mageia2 box. I'll create a clean AMI for others to use in the next few weeks! I released a Mandriva 2011 public AMI about a year ago.
It went much better than my attempt with 3.3.8-server-2.mga2, which complained about the compression format.
I see in the change log, you have switched it back to gzip.
Searching for the gzip signature, using
od -A d -t x1 vmlinuz-3.3.8-server-2.mga2 | grep '1f 8b 08 00' does not find it, for 3.3.8, but searching for the xz sig, using
od -A d -t x1 vmlinuz-3.3.8-server-2.mga2 | grep -i 'fd 37 7a 58 5a 00', return a match.
I found what is a little bit of a trap for people... funny now I think about it.
the output from running file vmlinuz*
vmlinuz-3.4.24-server-2.mga2:
Linux kernel x86 boot executable bzImage, version 3.4.24-server-2.mga2
(
iurt@ecosse.mageia.org) #1 SMP Tue Dec 18, RO-rootFS, swap_dev 0x3,
Normal VGA
vmlinuz-3.3.8-server-2.mga2: Linux kernel x86 boot
executable bzImage, version 3.3.8-server-2.mga2 (
iurt@jonund.mageia.org)
#1 SMP Mon Jul 30 , RO-rootFS, swap_dev 0x2, Normal VGA
It is easy to assume that bzImage mean's bzip.. but it does not.. it means big zimage. the actual compression type is not displayed using the file command.
I wonder if a patch to the file command to also output the compression type for kernel images, might be a good idea?
Regards
Glen Ogilvie