HP Xw460c HP Insight Control Environment User Guide - Page 100

Options, Identify Systems, HP SIM All Systems, Deploy, Virtual Machine, Move Type, ESX systems

Get HP Xw460c - ProLiant - Blade Workstation PDF manuals and user guides View all HP Xw460c manuals
Add to My Manuals
Save this manual to your list of manuals

Page 100 highlights

are listed. For para-virtualized guests, only destination hosts running the same kernel are listed. Note that hardware virtualization must be enabled in the BIOS for some virtual machine hosts. Only virtual machine guests created using simple file storage can be moved. You can move the virtual machines hosted on VMware ESX Server, VMware Server, HP integrated Citrix XenServer, Microsoft Virtual Server hosts, and Hyper-V using the following options: • Move-The virtual disk is copied to the host. You must stop the virtual machine for this move operation type. • SAN Move-The virtual disk is not copied to the target host. The target host accesses the virtual disks using storage area network (SAN) connectivity. You must stop the virtual machine for this move operation type. SAN Moves cannot be performed using Hyper-V, and Xen on RHEL or SLES. • Live Move-The powered-up virtual machine is moved using VMware VMotion Technology for VMware ESX systems, and using Citrix XenMotion Technology for Citrix XenServer virtual machines. (Not applicable for Hyper-V). • Quick Move-The Hyper-V virtual machine is moved using the Microsoft Quick Migration technology. (Not applicable for VMware ESX Server or HP integrated Citrix XenServer). When performing a Live move, if the CMS and VirtualCenter are in different networks, a delay might occur when the list of possible target hosts is created. NOTE: To minimize the occurrence of orphan managed systems, the name of the virtual machine in HP integrated Citrix XenServer must be the same as the host name of the virtual machine discovered in CMS. NOTE: Virtual Machine Management Pack supports Quick Move when a Hyper-V virtual machine is configured for high availability (HA) in a Hyper-V failover cluster. NOTE: Virtual Machine Management Pack supports SAN Move of virtual machines on a shared storage in resource pool environments for HP integrated Citrix XenServer. NOTE: If the error message Unknown to VMM appears when performing the move operation on a virtual machine, ensure that the virtual machine exists on the host. If the virtual machine has been deleted from the host, but the virtual machine node is still present in HP SIM, run the Identify Systems task on the virtual machine host from Options→Identify Systems in HP SIM. If the virtual machine was manually discovered in HP SIM using the IP address, then the virtual machine must be deleted from the HP SIM All Systems page. You must stop the Microsoft Virtual Server 2005 or VMware Server virtual machine guests before moving them. If the virtual machine is part of a VirtualCenter cluster, then a warning message appears. To move a virtual machine guest: 1. On the HP SIM All Systems page, select the virtual machine guest to be moved. 2. From the HP SIM toolbar, select Deploy→Virtual Machine→Move Virtual Machine. 3. Verify the source virtual machine, and then click Next. If a quick move is initiated, a message appears indications to power down the virtual machine and ensure it is HA enabled and part of the cluster before proceeding. 4. Select the target virtual machine host from the list of authorized licensed hosts, and then click Next. NOTE: For virtual machines using HP integrated VMware ESXi 3.5, you cannot set the target folder. The default name and path are used. If the selected virtual machine is associated with a VMware ESX Server and: • The virtual machine is currently running, a Live Move for VMware ESX Server using VMware VMotion Technology is performed. • The virtual machine is stopped, SAN Move or Move appears in the Move Type column. If the target host is in a SAN, a SAN Move can be performed. 100 Using HP Virtual Machine Management Pack

  • 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
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
are listed. For para-virtualized guests, only destination hosts running the same kernel are listed. Note that
hardware virtualization must be enabled in the BIOS for some virtual machine hosts.
Only virtual machine guests created using simple file storage can be moved.
You can move the virtual machines hosted on VMware ESX Server, VMware Server, HP integrated Citrix
XenServer, Microsoft Virtual Server hosts, and Hyper-V using the following options:
•
Move—The virtual disk is copied to the host. You must stop the virtual machine for this move operation
type.
•
SAN Move—The virtual disk is not copied to the target host. The target host accesses the virtual disks
using storage area network (SAN) connectivity. You must stop the virtual machine for this move operation
type. SAN Moves cannot be performed using Hyper-V, and Xen on RHEL or SLES.
•
Live Move—The powered-up virtual machine is moved using VMware VMotion Technology for VMware
ESX systems, and using Citrix XenMotion Technology for Citrix XenServer virtual machines. (Not
applicable for Hyper-V).
•
Quick Move—The Hyper-V virtual machine is moved using the Microsoft Quick Migration technology.
(Not applicable for VMware ESX Server or HP integrated Citrix XenServer).
When performing a Live move, if the CMS and VirtualCenter are in different networks, a delay might occur
when the list of possible target hosts is created.
NOTE:
To minimize the occurrence of orphan managed systems, the name of the virtual machine in
HP integrated Citrix XenServer must be the same as the host name of the virtual machine discovered in CMS.
NOTE:
Virtual Machine Management Pack supports Quick Move when a Hyper-V virtual machine is
configured for high availability (HA) in a Hyper-V failover cluster.
NOTE:
Virtual Machine Management Pack supports SAN Move of virtual machines on a shared storage
in resource pool environments for HP integrated Citrix XenServer.
NOTE:
If the error message
Unknown to VMM
appears when performing the move operation on a virtual
machine, ensure that the virtual machine exists on the host. If the virtual machine has been deleted from the
host, but the virtual machine node is still present in HP SIM, run the Identify Systems task on the virtual
machine host from
Options
→
Identify Systems
in HP SIM. If the virtual machine was manually discovered
in HP SIM using the IP address, then the virtual machine must be deleted from the
HP SIM All Systems
page.
You must stop the Microsoft Virtual Server 2005 or VMware Server virtual machine guests before moving
them. If the virtual machine is part of a VirtualCenter cluster, then a warning message appears.
To move a virtual machine guest:
1.
On the
HP SIM All Systems
page, select the virtual machine guest to be moved.
2.
From the HP SIM toolbar, select
Deploy
→
Virtual Machine
→
Move Virtual Machine.
3.
Verify the source virtual machine, and then click
Next
.
If a quick move is initiated, a message appears indications to power down the virtual machine and
ensure it is HA enabled and part of the cluster before proceeding.
4.
Select the target virtual machine host from the list of authorized licensed hosts, and then click
Next
.
NOTE:
For virtual machines using HP integrated VMware ESXi 3.5, you cannot set the target folder.
The default name and path are used.
If the selected virtual machine is associated with a VMware ESX Server and:
•
The virtual machine is currently running, a Live Move for VMware ESX Server using VMware
VMotion Technology is performed.
•
The virtual machine is stopped, SAN Move or Move appears in the
Move Type
column. If the
target host is in a SAN, a SAN Move can be performed.
100
Using HP Virtual Machine Management Pack