From mboxrd@z Thu Jan  1 00:00:00 1970
From: Anthony Wright <anthony@overnetdata.com>
Subject: Re: dmidecode doesn't work under xen 4.1.1 on certain
	hardware
Date: Wed, 28 Sep 2011 17:07:07 +0100
Message-ID: <4E83462B.9080002@overnetdata.com>
References: <4E7C6BDC.8070005@overnetdata.com>
	<20110923133200.GC19579@phenom.oracle.com>
	<4E7C9C8B.2010108@overnetdata.com>
	<20110926141322.GD4102@phenom.oracle.com>
	<4E8090D4.2090009@overnetdata.com>
	<20110926193732.GA10007@phenom.oracle.com>
	<4E82E429.2080600@overnetdata.com>
	<20110928132815.GE10270@phenom.oracle.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <20110928132815.GE10270@phenom.oracle.com>
List-Unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
List-Id: xen-devel@lists.xenproject.org

On 28/09/2011 14:28, Konrad Rzeszutek Wilk wrote:
>>>> (XEN) WARNING: Only the first 16 GB of the physical memory map can be accessed by Xen in 32-bit mode.
>>> That bites ^^^^
>>>> (XEN) Truncating RAM from 17825792kB to 16777216kB
>> Does this mean that 32 bit Xen can only use a maximum of 16GB of RAM?
>>
>> If so, is there a way to use 32 bit Xen tools with a 64 bit Xen hypervisor?
> Yes. I've been doing that without any trouble.
I tried to get this so work some time ago and failed. Do I need a 64 bit
Dom0 kernel with a 64 bit xen hypervisor or can I get away with a 32 bit
Dom0 kernel?
>> The patch works perfectly. I've attached a copy of the kernel log with
>> 'debug loglevel=8'
> Yeeey! Great. Thanks for testing it. We are re-doing that whole E820 parsing
> for the next version of Linux (3.2) so will integrate the "essence" of that
> patch.
>
> Would you be up for testing a different variant of that patch just to make
> sure?
Not a problem, ship me the patch when you're ready. I'm running 3.0.4 at
the moment and would prefer to stick with 3.0.x for now, so hope that
won't be a problem.