Bug#557169: kernel-package: standard build makes unbootable image

Arthur Marsh arthur.marsh at internode.on.net
Fri Nov 20 02:02:57 UTC 2009



Manoj Srivastava wrote, on 2009-11-20 11:50:
> reassign 557169 grub-pc
> severity 557169 normal
> thanks
> 
> Hi,
> On Thu, Nov 19 2009, Arthur Marsh wrote:
> 
>> Hi, I tried building again using:
>>
>> CONCURRENCY_LEVEL=32 DEB_HOST_ARCH=i386 MAKEFLAGS="CC=gcc-4.4" \ 
>> make-kpkg --initrd --config menuconfig linux-image

Sorry, I posted the wrong command line. The line I used was:

CONCURRENCY_LEVEL=32 MAKEFLAGS="CC=gcc-4.4" make-kpkg --initrd \
  --config menuconfig kernel-image

I was not trying to build any kind of xen image - config options were as 
in the attached file, very similar to the regular Debian AMD64 kernel 
with tuning for athlon64, pre-emptable kernel, and asynch scsi scanning 
disabled.

> 
>         So. You are on a  amd64 machine, and you are building a 32bit
>  kernel, for some reason. Is it because it is a Dom0 hypervisor?
> 
>> then installed the package and ran update-grub.
> 
>> It created entries like the following:
>>
>> menuentry "Debian GNU/Linux, with Linux 2.6.31" {
>>         insmod ext2
>>         set root=(hd0,1)
>>         search --no-floppy --fs-uuid --set 39706f53-7c27-4310-b22a-36c7b042d1a1
>>         linux   /boot/vmlinux-2.6.31 root=UUID=39706f53-7c27-4310-b22a-36c7b042d
>> 1a1 ro
>>         initrd  /boot/initrd.img-2.6.31
>> }
>> menuentry "Debian GNU/Linux, with Linux 2.6.31 (recovery mode)" {
>>         insmod ext2
>>         set root=(hd0,1)
>>         search --no-floppy --fs-uuid --set 39706f53-7c27-4310-b22a-36c7b042d1a1
>>         linux   /boot/vmlinux-2.6.31 root=UUID=39706f53-7c27-4310-b22a-36c7b042d
>> 1a1 ro single
>>         initrd  /boot/initrd.img-2.6.31
>> }
>>
>> This failed to boot.
> 
>         Well, yes, since grub2 has no support for  Xen images at all.
>  Legacy grub looks for the Xen bits in the corresponding config file,
>  and does the right thing. grub2 does not yet have this support.
> 
>> The files in my /boot directory from this install were:
>>
>> -rw-r--r--  1 root root  8299074 Nov 20 10:43 initrd.img-2.6.31
>> -rw-r--r--  1 root root 14578328 Nov 20 10:07 vmlinux-2.6.31
>> -rw-r--r--  1 root root 14578328 Nov 20 10:07 vmlinuz-2.6.31
>> -rw-r--r--  1 root root  1622458 Nov 20 10:07 System.map-2.6.31
>> -rw-r--r--  1 root root   101993 Nov 20 09:39 config-2.6.31
> 
>         The only reason there is a vmlinux is because this is a Xen0
>  image.  You need to either add support yourself for boot loading it, or
>  you need to find a compatible bootloader.
> 
>         manoj
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: config
URL: <http://lists.alioth.debian.org/pipermail/pkg-grub-devel/attachments/20091120/47021a5e/attachment.asc>


More information about the Pkg-grub-devel mailing list