From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Yuyang Du" Subject: Re: Re: PV kernel boot parameter maxcpus has noeffect? Date: Wed, 28 Apr 2010 18:18:01 +0800 Message-ID: <201004281817587658434@gmail.com> Reply-To: duyuyang@gmail.com Mime-Version: 1.0 Content-Type: text/plain; charset="gb2312" Content-Transfer-Encoding: 7bit Return-path: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Jan Beulich , "pasik@iki.fi" Cc: "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org >However, given that the bringing up of secondary CPUs happens from common (even arch-independent) code, the whole issue >seems a little suspicious - namely what indication he uses to see that there are more than 4 vCPU-s in use by Dom0. I was not clear, and using maxcpus boot parameter in dom0 kernel is not what I want. I wanted to let xen see only one socket and schedule only that socket (4 cores), so giving dom0 kernel boot parameter does not help. So I was wrong about that. What I am looking for is to tell xen to schedule only a portion of the available physical processors to whatever VMs, is there any method? I checked the BIOS options, and there is no way to disable a processor. Thanks, Shawn