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

Re: [Xen-devel] New kernel won't boot

To: Ian Pratt <Ian.Pratt@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] New kernel won't boot
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Wed, 05 Nov 2003 09:17:41 +0000
Cc: "Gregory Newby" <newby@xxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 05 Nov 2003 09:18:49 +0000
Envelope-to: steven.hand@xxxxxxxxxxxx
In-reply-to: Your message of "Tue, 04 Nov 2003 23:54:56 GMT." <E1AHB0j-0007wv-00@xxxxxxxxxxxxxxxxxxxx>
List-archive: <http://sourceforge.net/mailarchive/forum.php?forum=xen-devel>
List-help: <mailto:xen-devel-request@lists.sourceforge.net?subject=help>
List-id: List for Xen developers <xen-devel.lists.sourceforge.net>
List-post: <mailto:xen-devel@lists.sourceforge.net>
List-subscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=subscribe>
List-unsubscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=unsubscribe>
Sender: xen-devel-admin@xxxxxxxxxxxxxxxxxxxxx
> > When I use the image.gz and xenolinux.gz from the CD
> > (copied to my /boot), the exact same outcome happens
> >  -- a reboot after "DOM0: Guest OS virtual load address is c0000000"
> > 
> > However, I *can* boot directly from the CD with no problem.  I
> > didn't experiment much, and never tried to get networking
> > running, but it seemed like all the hardware was recognized.
> 
> Hmm, this is important. 
> 
> Please could you try booting with dom0_mem=100000 
> I wander if there's something odd about the memory layout of
> your machine.
> 
> What version of GRUB are you using? Could you install the one
> from the CD?  I'm wandering whether it's failing to load the
> module into memory correctly.

Actually that's very interesting. Xen currently assumes that physical
memory is contiguous (ie. there are no memory holes above 1MB).

This is because it was hassle to implement the proper checking that is
required, and I wouldn't be able to bug-test it because I have no
access to a machine with a memory hole. Also, I suspect that our
Xenoboot CD (our flexible alternative to GRUB) would need upgrading to
supply the required 'e820 memory-areas list'.

Can you send us the output from 'dmesg' for a normal Linux (not
Xenolinux!) running on the problem machine? Actually all we need are
the lines:
 BIOS-provided physical RAM map:
  BIOS-e820: ...
  BIOS-e820: ...
   ...

 Cheers,
 Keir


-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive?  Does it
help you create better code?   SHARE THE LOVE, and help us help
YOU!  Click Here: http://sourceforge.net/donate/
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel