Red Hat Bugzilla – Bug 492331
kernel image from boot.img doesn't boot
Last modified: 2009-05-18 16:16:19 EDT
Description of problem:
For ia64 there's a boot.img file under images/ in the tree directory. This contains vmlinuz and initrd.img files and some others. Using them is a no go. System doesn't boot.
Version-Release number of selected component (if applicable):
Always on ia64
Steps to Reproduce:
1. Loopback mount boot.img and extract vmlinuz and initrd.img files
2. Place the files under /boot/efi/efi/redhat
3. Configure elilo.conf to use the new kernel and boot into that target
ELILO boot: anaconda_1
Uncompressing Linux... |
^^^ and it stays like that forever
System boots and install begins
- vmlinuz and initrd.img files from images/pxeboot/ work just fine
- vmlinuz files from pxeboot and boot.img differ. This is by design AFAIK.
- KATE is using boot.img for ia64 which causes all test cases against snap #2 to time out.
FYI. no change has been made to the scripts that generate the images for quite some time. I doubt that this issue is caused by anaconda changes.
This issue was probably caused by adding additional modules to the initrd.
Vmlinuz is slightly smaller than the one from pxeboot directory.
Files don't fit to the image:
Filesystem Size Used Avail Use% Mounted on
.../boot.img 24M 24M 8.0K 100% /mnt/tmp
I think bug #491982 is responsible for adding new modules. Could be wrong though.
This is almost certainly due to running out of space in boot.img, as it is statically sized in rhel4's scripts/mk-images.ia64 .
*** Bug 492254 has been marked as a duplicate of this bug. ***
Peter was right. I updated the mk-images scripts for ia64 and i386. The images should be OK if created with anaconda-runtime-10.1.1.102.
fix goes in anaconda, changing component
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.