Yeah the idea is you write to VCPU_params when the VM is halted (or at creation) and they take effect when booted. Any subsequent changes to this (after booted) won't take effect until reboot, so we have the VCPU_params_live field to dynamically change this (and report it).|
On 12 Jul 2007, at 10:59, Saurabh Garg wrote:
Does it mean that it can be set only when the vm is running ? During creation time, it is possible to set cap and weight in the VCPU_params field, so if I set the cpumap values also, will this be effective ?
I guess if I'm not able to set it during the creation time, once the VM is created, I'll set it before starting the vm... will that work...
Tom Wilkie wrote:
If you look at the VCPU_params(_live) field of the VM class you can put a key "cpumap_$" ($ = vcpu num) with the value as a comma seperated list of physical CPUs.
On 12 Jul 2007, at 08:35, Saurabh Garg wrote:
With the 3.1 Xen API(s), is it possible to set the vcpu to pcpu(physical cpu) mapping configuration.
xen-api mailing list