Revision ccf5dcf5 doc/design-cpu-pinning.rst

b/doc/design-cpu-pinning.rst
48 48

  
49 49
  # Pin vCPU 0 to any CPU, vCPU 1 to CPUs 1, 3, 4 or 5, and CPU 2 to
50 50
  # CPU 0
51
  gnt-instance modify -H cpu_mask=all:1\\,3-4:0 my-inst
51
  gnt-instance modify -H cpu_mask=all:1\\,3-5:0 my-inst
52 52

  
53 53
  # Pin entire VM to CPU 0
54 54
  gnt-instance modify -H cpu_mask=0 my-inst
......
56 56
  # Turn off CPU pinning (default setting)
57 57
  gnt-instance modify -H cpu_mask=all my-inst
58 58

  
59
Assuming an instance has 2 vCPUs, the following commands will fail::
59
Assuming an instance has 3 vCPUs, the following commands will fail::
60 60

  
61 61
  # not enough mappings
62
  gnt-instance modify -H cpu_mask=0 my-inst
62
  gnt-instance modify -H cpu_mask=0:1 my-inst
63 63

  
64 64
  # too many
65
  gnt-instance modify -H cpu_mask=2:1:1 my-inst
65
  gnt-instance modify -H cpu_mask=2:1:1:all my-inst
66 66

  
67 67
Validation
68 68
----------
......
102 102

  
103 103
In case of emergency, to force failover to ignore mismatching CPU
104 104
information, the following switch can be used:
105
``gnt-instance failover --ignore-cpu-mismatch my-inst``.
106
This command will try to fail the instance with the current cpu mask,
105
``gnt-instance failover --fix-cpu-mismatch my-inst``.
106
This command will try to failover the instance with the current cpu mask,
107 107
but if that fails, it will change the mask to be "all".
108 108

  
109 109
Migration
......
127 127
------------------
128 128

  
129 129
The pinning information is kept for each instance's hypervisor
130
params section of the configuration file as
131
``cpu_mask: [ [ a ], [ b, c ], [ d ] ]``
130
params section of the configuration file as the original string.
132 131

  
133 132
Xen
134 133
---

Also available in: Unified diff