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 And the output of mbootpack is: Loading ./xen-syms using ELF header. Placed kernel section (0xfc500000+0x83428) Loaded kernel from ./xen-syms Placed MBI and strings (0x9c68+0x398) Placed section (0xfc584000+0x1eb710), align=0x1000 Loaded module from ./vmlinuz-2.6.11-xen0 Kernel entry is 0xfc500000, MBI is 0x9c68. Wrote bzImage header: 512 + 2380 bytes. Wrote 1 low-memory sections. Fatal: error seeking in output file: Invalid argument could anyone please assist? thanks, Ro'ee
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-symsCan 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@lists.xensource.com http://lists.xensource.com/xen-devel
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@cl.cam.ac.uk] Sent: Tuesday, March 29, 2005 10:53 To: Roee Sadeh Cc: xen-devel@lists.xensource.com 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-symsCan 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@lists.xensource.com http://lists.xensource.com/xen-devel
On Tue, Mar 29, 2005 at 05:47:12PM +0200, Roee Sadeh wrote:> 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.Hmmm. I''d guess if it takes that long to reboot that Xen is running (briefly) but console messages are getting lost. Can you give me a few more deatils of you setup and I''ll see if I can reproduce the failure? - What version of Xen and xen-linux are you using? - What hardware are you using? - What command-line did you give at boot time? - Are you using a serial console? Cheers, Tim. -- Tim Deegan (My opinions, not the University''s) Systems Research Group University of Cambridge Computer Laboratory _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Just for the archive: this problem was resolved by Roee. (Xen wasn''t happy with its command line.) Tim. On Tue, Mar 29, 2005 at 04:00:16PM +0000, Tim Deegan wrote:> On Tue, Mar 29, 2005 at 05:47:12PM +0200, Roee Sadeh wrote: > > 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. > > Hmmm. I''d guess if it takes that long to reboot that Xen is running > (briefly) but console messages are getting lost. > > Can you give me a few more deatils of you setup and I''ll see if I can > reproduce the failure? > > - What version of Xen and xen-linux are you using? > - What hardware are you using? > - What command-line did you give at boot time? > - Are you using a serial console? > > Cheers, > > Tim. > > -- > Tim Deegan (My opinions, not the University''s) > Systems Research Group > University of Cambridge Computer Laboratory-- Tim Deegan (My opinions, not the University''s) Systems Research Group University of Cambridge Computer Laboratory _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel