Re: [Xen-devel] problem w/ mbootpack

[Tim Deegan <Tim.Deegan@xxxxxxxxxxxx>]

On Sun, Mar 27, 2005 at 05:32:29PM +0200, Roee Sadeh wrote:
> I'm trying to load a xen0 linux using PXE boot (pxelinux).
> For this I'm trying to use mbootpack to pack xen and the xen0 images together.
> My problem is that mbootpack exits w/ error and the output file is 4096 bytes 
> in size.
>  
> My cmdline is:
> mbootpack -o bzImage -m ./vmlinuz-2.6.11-xen0 ./xen-syms

Can you try:

- un-gzipping the dom0 kernel before packing it?  mbootpack doesn't
  (yet) have transparent unzipping of its input files.

- Using 'xen' instead of 'xen-syms' (again, unzipping it first)?  

What's happening is that xen-syms wants to be loaded *very* high in
memory, and mbootpack expects to be loading it at around 1MB.  The error
message is mbootpack trying to seek to nearly 4GB into the output file.

It's not a very helpful error message; I've put "sane error messages for
insane load addresses" down on the todo-list, just after ".gz support". :)

xen-syms:                     Crazy load address  vvvvvvvvvv
Program Header:                                   ||||||||||
    LOAD off    0x00000080 vaddr 0xfc500000 paddr 0xfc500000 align 2**6
         filesz 0x0003ef3c memsz 0x00074928 flags rwx


xen:                        Correct load address  vvvvvvvvvv
Program Header:                                   ||||||||||
    LOAD off    0x00000080 vaddr 0x00100000 paddr 0x00100000 align 2**6
         filesz 0x0003ef3c memsz 0x00075000 flags rwx


Tim.

-- 
Tim Deegan                           (My opinions, not the University's)
Systems Research Group
University of Cambridge Computer Laboratory

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