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

[Xen-devel] Re: dom0 boot failure with 256G

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] Re: dom0 boot failure with 256G
From: mukesh rathor <mukesh.rathor@xxxxxxxxxx>
Date: Thu, 5 Jun 2008 18:01:48 +0000 (UTC)
Delivery-date: Thu, 05 Jun 2008 11:10:27 -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>
References: <48474A61.3050903@xxxxxxxxxx> <DD74FBB8EE28D441903D56487861CD9D2FC9B866@xxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Loom/3.14 (http://gmane.org/)
Ian Pratt <Ian.Pratt <at> eu.citrix.com> writes:

> 
> >     I've been intensely debugging a dom0 crash right at boot in
> >     pagetable_init() with 256G. We are running 64bit hyp with 32bit
> > dom0.
> >     This on xen 3.1.3, which seems to have fixes from changeset 16548.
> 
> 256GB is more than a 32b dom0 can handle. Presumably it works if you set
> dom0_mem= to something smaller?
> 
> We should probably make the clipping of dom0 memory to something like
> 64GB automatic.
> 
> Ian
> 
>  
..........

My apologies, I forgot to mention dom0_mem is set to : dom0_mem=569M

(XEN) Command line: console=com2,ttyS0 com2=115200,8n1 earlykdb dom0_mem=569M
mem=256G

Things are fine with mem=128G. I've not tried 192G or other number. I just
started debugging.....

I'll try with :
>    d->arch.physaddr_bitsize =
> >            fls((1UL << 32) - HYPERVISOR_COMPAT_VIRT_START(d)) - 1
> >              + (PAGE_SIZE - 2);
> >    which is set to 0x1019, totally baffling me. I'd expect it to be 32,
> >    36, or 64????????

>PAGE_SIZE should be PAGE_SHIFT. If you fix that then you may discover ...

thanks
mukesh




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