From mboxrd@z Thu Jan  1 00:00:00 1970
From: Jeremy Fitzhardinge <jeremy@goop.org>
Subject: Re: PVops domain 0 crash on NUMA system only Node==1
	present (Was: Re: Bug#603632:
	linux-image-2.6.32-5-xen-amd64:	Linux	kernel
	2.6.32/xen/amd64 booting fine on bare metal,
	but not as dom0 with Xen 4.0.1 (Dell R410))
Date: Thu, 02 Dec 2010 16:12:54 -0800
Message-ID: <4CF83606.6050904@goop.org>
References: <20101115233253.11935.35707.reportbug@zerohal>	
	<1290513067.31507.7699.camel@zakaz.uk.xensource.com>	
	<1290538327.9844.26.camel@localhost.localdomain>	
	<1290550323.9844.85.camel@localhost.localdomain>	
	<1290550726.9844.90.camel@localhost.localdomain>
	<1291333639.25131.48.camel@zerohal>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <1291333639.25131.48.camel@zerohal>
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: Vincent Caron <vcaron@bearstech.com>
Cc: xen-devel <xen-devel@lists.xensource.com>, Keir Fraser <keir@xen.org>, Ian Campbell <Ian.Campbell@citrix.com>, Vincent CARON <zerodeux@zerodeux.net>, Cris Daniluk <cris.daniluk@gmail.com>, "603632@bugs.debian.org" <603632@bugs.debian.org>
List-Id: xen-devel@lists.xenproject.org

On 12/02/2010 03:47 PM, Vincent Caron wrote:
>   It just happens that your kernel above (2.6.32-27+numa1) boots fine
> under hypervisor _when_ passed 'numa=noacpi'. Yeah !
>
>   I then tried again with Debian Squeeze's latest 2.6.32-28, which
> crashes as -27 under hypervisor (and changelog show no xen or
> numa-related thingies). Then I added 'numa=noacpi', and it boots fine
> too. I got my 8 cores, networking, etc.
>
>   Enclosed is the dmesg for the latter, Debian, kernel.
>
>   Is the 'numa=noacpi' a "production acceptable" workaround ?

What about "numa=fake=1"?  I think that should force it to create a
single NUMA node.

IanC: it looks like passing a node id of "-1" is the correct way to say
"I don't care".

    J