Xen 
 
Home About Xen.org Xen Xen Summit Wiki Mailing List Bug Tracker Xen Downloads
 
   
 

xen-devel

RE: [Xen-devel] problem w/ mbootpack

To: "Tim Deegan" <Tim.Deegan@xxxxxxxxxxxx>
Subject: RE: [Xen-devel] problem w/ mbootpack
From: "Roee Sadeh" <roees@xxxxxxxxxxxx>
Date: Tue, 29 Mar 2005 17:47:12 +0200
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 29 Mar 2005 15:47:28 +0000
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcU0PMAyamXStahQTSSUsh2Zv1iXJQAOR/sA
Thread-topic: [Xen-devel] problem w/ mbootpack
Thanks Tim, it helped.
I created the "unified" xen+linux-xen0 image but when I pxe load it the machine 
hangs.

What I see is that that the pxe loader (I'm using pxelinux) finds my unified 
image and loads it successfully.
Then a printout is given saying "mbootpack v0.2 (alpha)" and that's it.
The machine hangs and reboots after approx. 15 seconds.
I don't get any of the printouts that xen usually produces while booting.

Any ideas?

Thanks,

Ro'ee

-----Original Message-----
From: Tim Deegan [mailto:Tim.Deegan@xxxxxxxxxxxx] 
Sent: Tuesday, March 29, 2005 10:53
To: Roee Sadeh
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-devel] problem w/ mbootpack

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

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