Re: Yaboot stripped image Was: [XenPPC] Cannot boot from local disk

[Jimi Xenidis <jimix@xxxxxxxxxxxxxx>]

On Oct 6, 2006, at 11:05 AM, Kiyokuni Kawachiya wrote:

> > > It probably is, which image do you copy for yaboot to use?
> I usually copied xen/xen to /boot/xen-3.0-unstable, and specified  
> it in
> yaboot.conf.
>
> > > can you try:
> > >   $ objcopy -S xen/xen-syms xen/xen.yaboot
> > > and have yaboot load xen.yaboot
> I tried, but the situation is same.
>
>
>
> One thing I noticed is that "objdump -h" result is very different  
> between
> the bootable and non-bootable xen images.
>
> (Bootable xen/xen)
> wsjs4 XenPPC.watson.ok/xen-ppc> objdump -h xen/xen
>
> xen/xen:     file format elf32-powerpc
>
> Sections:
> Idx Name          Size      VMA       LMA       File off  Algn
>   0 .text         00000040  00400000  00400000  00000078  2**3
>                   CONTENTS, ALLOC, LOAD, CODE
>
> (Non-bootable xen/xen)
> wsjs4 XenPPC.xensource/xen-ppc> objdump -h xen/xen
>
> xen/xen:     file format elf32-powerpc
>
> Sections:
> Idx Name          Size      VMA       LMA       File off  Algn
>   0 .text         00031a10  00400000  00400000  00000100  2**7
>                   CONTENTS, ALLOC, LOAD, CODE
yeah even weirder is:
$ objdump -p xen

xen:     file format elf32-powerpc

Program Header:
   LOAD off    0x00000000 vaddr 0x003fff00 paddr 0x003fff00 align 2**8
        filesz 0x000ab0d8 memsz 0x000bebc8 flags rwx

I sent a patch in a previous mail, could you try that?
-JX

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