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/
Home Products Support Community News


[Xen-devel] Unable to start PAE Mini-OS from 0x0

To: <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] Unable to start PAE Mini-OS from 0x0
From: "Puthiyaparambil, Aravindh" <aravindh.puthiyaparambil@xxxxxxxxxx>
Date: Fri, 19 May 2006 17:35:16 -0400
Delivery-date: Fri, 19 May 2006 14:35:44 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
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: AcZ7jB5kHK0Pklm5QMOipZ36PfE9hA==
Thread-topic: Unable to start PAE Mini-OS from 0x0
I am trying to start PAE Mini-OS from 0x0 so that I can get access to
all 4GB. But it is failing in the builder (line 838 xc_linux_build.c)
when it tries to pin the L3 table with the following error below.
Further more, I am not able to bring up Mini-OS from any other address
other than 0xc0000000.

Is there a restriction on this in i386 PAE? Could someone please explain

Aravindh Puthiyaparambil 
Xen Development Team 
Unisys, Tredyffrin PA

(XEN) DOM0: (file=mm.c, line=734) PAE L3 3rd slot is empty
(XEN) DOM0: (file=mm.c, line=918) Failure in alloc_l3_table: entry 4
(XEN) DOM0: (file=mm.c, line=1567) Error while validating mfn bd93b (pfn
e0c4) for type 60000000: caf=80000002 taf=60000001
(XEN) DOM0: (file=mm.c, line=1839) Error while pinning mfn bd93b

Xen-devel mailing list

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