WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] xc_dom_probe_bzimage_kernel: kernel is not a bzImage

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] xc_dom_probe_bzimage_kernel: kernel is not a bzImage
From: Jed Smith <jed@xxxxxxxxxx>
Date: Tue, 12 Jan 2010 12:19:45 -0500
Cc: Christopher Aker <caker@xxxxxxxxxx>
Delivery-date: Wed, 13 Jan 2010 08:58:26 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Good afternoon,

We had a report from a customer that OpenSUSE's paravirt 2.6.31.8-0.1.1 boots
inconsistently under PV-Grub.  Here is one attempt:

> root (hd0)
>  Filesystem type is ext2fs, using whole disk
> kernel /boot/vmlinuz-xen root=/dev/xvdc resume=/dev/xvdb xencons=hvc0 
> kbdtype=u
> s text nofb selinux=0 edd=off splash=silent noshell showopts
> initrd /boot/initrd-xen
> 
> ERROR Invalid kernel: xc_dom_probe_bzimage_kernel: kernel is not a bzImage
> 
> xc_dom_bzimageloader.c:350: panic: xc_dom_probe_bzimage_kernel: kernel is not 
> a bzImage
> Map 135 (4a8c46, ...) at 0x22c82000 failed: -22.
> Do_exit called!
> base is 0xbcf2f8 caller is 0x457cf
> base is 0xbcf328 caller is 0x50536
> base is 0xbcfbf8 caller is 0x505f5
> base is 0xbcfc38 caller is 0x368ae
> base is 0xbcfc78 caller is 0x26447
> base is 0xbcfcb8 caller is 0x25981
> base is 0xbcfcf8 caller is 0x25f8e
> base is 0xbcfd68 caller is 0x29f27
> base is 0xbcfd98 caller is 0x261a3
> base is 0xbcfdd8 caller is 0x17c1b
> base is 0xbcfe38 caller is 0x3a78
> base is 0xbcfe58 caller is 0x8a3e
> base is 0xbcfe68 caller is 0xa389
> base is 0xbcfe88 caller is 0x101a9
> base is 0xbcfef8 caller is 0x107cb
> base is 0xbcff68 caller is 0x3f18
> base is 0xbcff88 caller is 0x46e2f
> base is 0xbcfff0 caller is 0x31ad

And here is another where a similar message appears but our user is able to go
back to the grub menu, boot the same entry again, and have it boot after
another error:

> root (hd0)
>  Filesystem type is ext2fs, using whole disk
> kernel /boot/vmlinuz-xen root=/dev/xvdc resume=/dev/xvdb xencons=hvc0 
> kbdtype=u
> s text nofb selinux=0 edd=off splash=silent noshell showopts
> initrd /boot/initrd-xen
> 
> ERROR Invalid kernel: xc_dom_probe_bzimage_kernel: kernel is not a bzImage
> 
> xc_dom_bzimageloader.c:350: panic: xc_dom_probe_bzimage_kernel: kernel is not 
> a bzImage
> pin_table(x) returned 4879168
> 
> Error 9: Unknown boot failure
> 
> Press any key to continue...

[Strike <Return>]

> GNU GRUB  version 0.97  (552960K lower / 0K upper memory)

[Strike <Return>]

> root (hd0)
>  Filesystem type is ext2fs, using whole disk
> kernel /boot/vmlinuz-xen root=/dev/xvdc resume=/dev/xvdb xencons=hvc0 
> kbdtype=u
> s text nofb selinux=0 edd=off splash=silent noshell showopts                  
>  
> initrd /boot/initrd-xen                                                       
>  
> 
> ERROR Invalid kernel: xc_dom_probe_bzimage_kernel: kernel is not a bzImage
> 
> xc_dom_bzimageloader.c:350: panic: xc_dom_probe_bzimage_kernel: kernel is not 
> a bzImage
> close blk: backend at /local/domain/0/backend/vbd/324/51712                   
>          
> close blk: backend at /local/domain/0/backend/vbd/324/51728                   
>          
> close blk: backend at /local/domain/0/backend/vbd/324/51744                   
>          
> close blk: backend at /local/domain/0/backend/vbd/324/51760                   
>          
> [    0.000000] Reserving virtual address space above 0xf5800000               
>          
> [    0.000000] Initializing cgroup subsys cpuset                              
>          
> [    0.000000] Initializing cgroup subsys cpu                                 
>          
> [    0.000000] Linux version 2.6.31.8-0.1-xen (geeko@buildhost) (gcc version 
> 4.4.1 [gcc-4_4-branch revision 150839] (SUSE Linux) ) #1 SMP 2009-12-15 
> 23:55:40 +0100


We're suspecting kernel compression here.  Any tips or debugging we can do?

It's odd that the behavior is intermittent.

Regards,

Jed Smith
Systems Administrator
Linode, LLC
+1 (609) 593-7103 x1209
jed@xxxxxxxxxx


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>