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: max vcpus in dom0

To: <Xen-devel@xxxxxxxxxxxxxxxxxxx>,<mukesh.rathor@xxxxxxxxxx>
Subject: [Xen-devel] Re: max vcpus in dom0
From: "Jan Beulich" <jbeulich@xxxxxxxxxx>
Date: Tue, 27 Apr 2010 09:23:19 +0100
Cc:
Delivery-date: Tue, 27 Apr 2010 01:24:35 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
>>> Mukesh Rathor  04/27/10 4:20 AM >>>
>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? 

That's the legacy limit, yes. Any attempt to go beyond 32 CPUs requires
the kernel to use the per-vCPU-info-placement hypercall prior to bringing
up those vCPU-s.

Jan


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

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