Parameter Name
Description
Type
configuration parameters for | read/write map parameter | |
| the selected VCPU policy. |
|
| You can tune a VCPU's |
|
| pinning with |
|
| xe |
|
| uuid=<vm_uuid> \ |
|
|
| |
| The selected VM will then run |
|
| on physical CPUs 1, 2, and 3 |
|
| only. |
|
| You can also tune the VCPU |
|
| priority (xen scheduling) |
|
| with the cap and weight |
|
| parameters; for example |
|
| xe |
|
| uuid=<template_uuid> \ |
|
|
| |
| xe |
|
| uuid=<template UUID> \ |
|
|
| |
| A VM with a weight of 512 will |
|
| get twice as much CPU as a |
|
| domain with a weight of 256 |
|
| on a contended XenServer |
|
| host. Legal weights range |
|
| from 1 to 65535 and the |
|
| default is 256. |
|
| The cap optionally fixes the |
|
| maximum amount of CPU a |
|
| VM will be able to consume, |
|
| even if the XenServer host |
|
| has idle CPU cycles. The cap |
|
| is expressed in percentage |
|
| of one physical CPU: 100 is |
|
| 1 physical CPU, 50 is half a |
|
| CPU, 400 is 4 CPUs, etc. The |
|
| default, 0, means there is no |
|
| upper cap. |
|
|
|
|
maximum number of virtual | read/write | |
| CPUs. |
|
|
|
|
boot number of virtual CPUs | read/write | |
|
|
|
197