On Fri, Dec 15, 2006 at 05:01:10PM -0500, Subrahmanian, Raj wrote:
* Support for ResourcePoolConfigurationService on some pool
types, e.g. ProcessorPool.This functionality will support for example
removing PCPUs from the pool and dedicate to management domain, thus
restricting set of PCPUs available for consumption by VMs. Does xen
support
this? Can we mask PCPUs such that they are not available to VMs?
At the present time, we cannot remove physical processors from the
scheduling for VMs cleanly. We will need to modify the scheduler and
create a new xm command for that.
There is a way around it. Every time we need some PCPUs taken out, we
will need to create a dummy VM and pin those PCPUs that we want taken
out of the scheduling to it. And destroy that VM when we want to put
them back in the mix. It's not very clean.
I think that you've had some answers here from Emmanuel, but just so
it's clear -- there is no need to modify the scheduler to do this. The
scheduler supports the concept of a per-VCPU set giving all the PCPUs on
which that VCPU may run. Recent tools bugs aside, this should suffice
to remove a PCPU from a pool -- you iterate over each VM on the host
and each VCPU in the VM, and then if that VCPU is not meant to be consuming
resource from the pool in question, remove the PCPU from the VCPU's set.
Cheers,
Ewan.
19 messages in com.xensource.lists.xen-cimRe: [Xen-cim] Requirements and priori...
.gif, .gif, .gif