HP BL680c XenServer Administrator's Guide 4.1.0 - Page 102

vm-install, 4.22.18. vm-memory-shadow-multiplier-set, 4.22.19. vm-migrate

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 102 highlights

Command line interface Note The older directory-based XVA format does not fully preserve all the VM attributes. In particular, imported VMs will not have any virtual network interfaces attached by default. If networking is required, create one using vif-create and vif-plug. If the metadata is [true], then a previously exported set of metadata can be imported without their associated disk blocks. Metadata-only import will fail if any VDIs cannot be found (named by SR and VDI.location) unless the --force option is specified, in which case the import will proceed regardless. If disks can be mirrored/moved out-of-band then metadata import/export represents a fast way of moving VMs between disjoint pools (e.g. as part of a disaster recovery plan). 5.4.22.17. vm-install vm-install new-name-label=name [ template-uuid=UUID of desired template | [template=UUID or name of desired template ]] [ sr-uuid=SR UUID | sr-name-label=name of SR ] Install a VM from a template. Specify the template name using either the template-uuid or template argument. Specify an SR other than the default SR using either the sr-uuid or sr-name-label argument. 5.4.22.18. vm-memory-shadow-multiplier-set vm-memory-shadow-multiplier-set [ vm-selector=vm selector value...] [multiplier=float memory multiplier ] Set the shadow memory multiplier for the specified VM. This is an advanced option which modifies the amount of shadow memory assigned to a hardware-assisted VM. In some specialized application workloads, such as the Citrix Presentation Server, extra shadow memory is required to achieve full performance. This memory is considered to be overhead, and is separate from the normal memory calculations for accounting memory to a VM. When this command is invoked, the amount of free XenServer Host memory will decrease according to the multiplier, and the HVM_shadow_multiplier field will be updated with the actual value which Xen has assigned to the VM. If there is not enough XenServer Host memory free, then an error will be returned. The VMs on which this operation should be performed are selected via the standard selection mechanism (see VM selectors above). 5.4.22.19. vm-migrate vm-migrate [[host-uuid=destination XenServer Host UUID ] | [host=name or UUID of destination XenServer Host ]] [ vm-selector=vm selector value...] [live=true | false ] Migrate the specified VMs between physical hosts. The host parameter can be either the name or the UUID of the XenServer Host. By default, the VM will be suspended, migrated, and resumed on the other host. The live parameter activates XenMotion and keeps the VM running while performing the migration, thus minimizing VM downtime to less than a second. In some circumstances such as extremely memory-heavy workloads in the VM, XenMotion automatically falls back into the default mode and suspends the VM for a brief period of time before completing the memory transfer. The VM or VMs on which this operation should be performed are selected via the standard selection mechanism (see VM selectors). Optional arguments can be any number of the VM parameters listed at the beginning of this section. 96

  • 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
96
Note
The older directory-based XVA format does not fully preserve all the VM attributes. In particular,
imported VMs will not have any virtual network interfaces attached by default. If networking is re-
quired, create one using
vif-create
and
vif-plug
.
If the
metadata
is [true], then a previously exported set of metadata can be imported without their
associated disk blocks. Metadata-only import will fail if any VDIs cannot be found (named by SR and
VDI.location
) unless the
--force
option is specified, in which case the import will proceed regardless.
If disks can be mirrored/moved out-of-band then metadata import/export represents a fast way of moving
VMs between disjoint pools (e.g. as part of a disaster recovery plan).
5.4.22.17. vm-install
vm-install
new-name-label=
name
[ template-uuid=
UUID of desired template
| [template=
UUID
or name of desired template
]] [ sr-uuid=
SR UUID
| sr-name-label=
name of SR
]
Install a VM from a template. Specify the template name using either the
template-uuid
or
template
argument. Specify an SR other than the default SR using either the
sr-uuid
or
sr-name-label
argument.
5.4.22.18. vm-memory-shadow-multiplier-set
vm-memory-shadow-multiplier-set
[
vm-selector
=
vm selector value
...] [multiplier=
float
memory multiplier
]
Set the shadow memory multiplier for the specified VM.
This is an advanced option which modifies the amount of
shadow memory
assigned to a hardware-assist-
ed VM. In some specialized application workloads, such as the Citrix Presentation Server, extra shadow
memory is required to achieve full performance.
This memory is considered to be overhead, and is separate from the normal memory calculations for ac-
counting memory to a VM. When this command is invoked, the amount of free XenServer Host memory
will decrease according to the multiplier, and the
HVM_shadow_multiplier
field will be updated with the
actual value which Xen has assigned to the VM. If there is not enough XenServer Host memory free, then
an error will be returned.
The VMs on which this operation should be performed are selected via the standard selection mechanism
(see VM selectors above).
5.4.22.19. vm-migrate
vm-migrate
[[host-uuid=
destination XenServer Host UUID
] | [host=
name or UUID of des-
tination XenServer Host
]] [
vm-selector
=
vm selector value
...] [live=
true | false
]
Migrate the specified VMs between physical hosts. The
host
parameter can be either the name or the
UUID of the XenServer Host.
By default, the VM will be suspended, migrated, and resumed on the other host. The
live
parameter acti-
vates XenMotion and keeps the VM running while performing the migration, thus minimizing VM downtime
to less than a second. In some circumstances such as extremely memory-heavy workloads in the VM, Xen-
Motion automatically falls back into the default mode and suspends the VM for a brief period of time before
completing the memory transfer.
The VM or VMs on which this operation should be performed are selected via the standard selection mech-
anism (see VM selectors). Optional arguments can be any number of the VM parameters listed at the be-
ginning of this section.