* Re: Re: PV kernel boot parameter maxcpus has noeffect?
@ 2010-04-28 10:18 Yuyang Du
2010-04-28 10:27 ` Jan Beulich
0 siblings, 1 reply; 2+ messages in thread
From: Yuyang Du @ 2010-04-28 10:18 UTC (permalink / raw)
To: Jan Beulich, pasik@iki.fi; +Cc: xen-devel@lists.xensource.com
>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
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2010-04-28 10:27 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2010-04-28 10:18 Re: PV kernel boot parameter maxcpus has noeffect? Yuyang Du
2010-04-28 10:27 ` Jan Beulich
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.