From mboxrd@z Thu Jan  1 00:00:00 1970
From: Mukesh Rathor <mukesh.rathor@oracle.com>
Subject: max vcpus in dom0
Date: Mon, 26 Apr 2010 19:17:33 -0700
Message-ID: <20100426191733.39f8b8c2@mantra.us.oracle.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.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: "Xen-devel@lists.xensource.com" <Xen-devel@lists.xensource.com>
Cc: JBeulich@novell.com
List-Id: xen-devel@lists.xenproject.org

Hi,

Looking at a bug where dom0 is crashing coming up with more than 32
vcpus, the problem happens trying to initialize 32nd vcpu. I see
the shared info is limited to 32vcpus, implying we'd have a hard limit
of 32 vcpus in dom0, correct? 

For now, I can just fix our dom0 to not go above 32, and look at ways
of fixing it if there's a strong case for more than 32 vcpus in dom0.

thanks,
Mukesh