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] issues getting more than 16M ram to be used without oops

To: "Brian Wolfe" <brianw@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] issues getting more than 16M ram to be used without oopsing. 1.2 and 1.3-unstable
From: Ian Pratt <Ian.Pratt@xxxxxxxxxxxx>
Date: Sun, 04 Apr 2004 09:34:17 +0100
Cc: Xen-devel@xxxxxxxxxxxxxxxxxxxxx, Ian.Pratt@xxxxxxxxxxxx
Delivery-date: Sun, 04 Apr 2004 09:36:12 +0100
Envelope-to: steven.hand@xxxxxxxxxxxx
In-reply-to: Your message of "Sat, 03 Apr 2004 15:53:51 MDT." <36009.216.166.50.35.1081029231.squirrel@xxxxxxxxxxxxx>
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
> First off, I'd like to say that Xen looks very promising.
> 
> I have been trying to get xen to run on my machine for the last 4 days
> with only marginal sucess.
> 
> I think I am having a hardware compatibility issue. I have tried the
> pre-compiled 1.2 tarball, and the nightly build tarball. Neither will work
> if I attempt to use more than 16MB of ram  (dom0_mem=16384 works,
> dom0_mem=16385 crashes)

I think its best to try and understand this before looking at the
crashes when starting new domains.

Running memtest is a good idea because your stock Debian boot
isn't actually exercising all of memory as its a non HIGHMEM
kernel on a 1GB machine, hence the top 100MB or so never gets
used. 

Also, it would be useful to see the full output of Xen/dom0
booting. The memory detection happens early on, and its just
possible that the BIOS table parsing is failing (The Debian linux
kernel grumbles about pages being reserved twice). 

Ian


-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel