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-users

[Xen-users] Xen RAM detection/visibility

To: <xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-users] Xen RAM detection/visibility
From: "Fabian Aichele" <faichele@xxxxxxxxxxxxxxxxxxxxxxxx>
Date: Fri, 9 Sep 2005 13:02:54 +0200
Delivery-date: Fri, 09 Sep 2005 11:01:17 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
Importance: Normal
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
I've got a problem getting Xen's dom0 to correctly discover and use all
installed physical RAM.
I have tried two different x86 machines, one Pentium III with 256MB RAM and
one AMD Athlon XP with 512MB.

The Pentium machine's dom0 kernel correctly reports 256 MB of RAM supplied
with "[...] dom0_mem=131072 mem=262144k [...]" as kernel command line
parameters.
In contrast, the Athlon XP dom0 kernel only boots correctly when I omit
"mem=524288k" on the kernel command line, and it only reports what I provide
as "dom0_mem" as available physical RAM; strangely, "xm info" correctly
reports 512MB of RAM, whereas the dom0 kernel itself only reports the
dom0_mem amount.
When I provide "mem=524288k" as kernel command line parameter, the dom0
kernel starts booting until the
"Scrubbing free RAM/Scrubbing Dom0 RAM..." messages, then it reboots without
any further console output.

I'm using the same Xen binary (version 2.0.6, debian testing packages) and
kernel versions (2.6.11.12-xen0/xenU) on both machines; the dom0 kernels are
compiled with the same configuration options (except for the chosen CPU
type), and I can't figure out why one machine works correctly, while the
other one refuses to correctly detect all available RAM. I'd be grateful for
any hints/suggestions.

Regards,
Fabian Aichele



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

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-users] Xen RAM detection/visibility, Fabian Aichele <=