HP BL680c XenServer Administrator's Guide 4.1.0 - Page 95

no upper cap.

Get HP BL680c - ProLiant - G5 PDF manuals and user guides
UPC - 884420396314
View all HP BL680c manuals
Add to My Manuals
Save this manual to your list of manuals

Page 95 highlights

Parameter Name suspend-VDI-uuid VCPUs-params VCPUs-max VCPUs-at-startup actions-after-crash Command line interface Description Type The VDI that a suspend image is stored on read only configuration parameters for the selected read/write map parameter VCPU policy. You can tune a VCPU's pinning with xe vm-param-set uuid= VCPUs-params:mask=1,2,3 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 vm-param-set uuid= \ VCPUs-params:weight=512 xe vm-param-set uuid= \ VCPUs-params:cap=100 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 CPUs. Boot number of virtual CPUs action to take if the VM crashes. For PV guests, valid parameters are: preserve (for analysis only), coredump_and_restart (record a coredump and reboot VM), coredump_and_destroy (record a coredump and leave VM halted), restart (no coredump and restart VM), and read/write read/write read/write 89

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
Command line interface
89
Parameter Name
Description
Type
suspend-VDI-uuid
The VDI that a suspend image is stored on
read only
VCPUs-params
configuration parameters for the selected
VCPU policy.
You can tune a VCPU's pinning with
xe vm-param-set uuid=<VM UUID> VCPUs-params:mask=1,2,3
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 vm-param-set uuid=<template UUID> \
VCPUs-params:weight=512
xe vm-param-set uuid=<template UUID> \
VCPUs-params:cap=100
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.
read/write map parameter
VCPUs-max
Maximum number of virtual CPUs.
read/write
VCPUs-at-startup
Boot number of virtual CPUs
read/write
actions-after-crash
action to take if the VM crashes. For PV
guests, valid parameters are: preserve
(for analysis only), coredump_and_restart
(record a coredump and reboot VM),
coredump_and_destroy (record a
coredump and leave VM halted), restart
(no coredump and restart VM), and
read/write