HP ProLiant DL185 HP Insight Server Migration Software for ProLiant User Guide - Page 79

P2V post-migration tasks, and booted the virtual machine

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

Page 79 highlights

P2V post-migration tasks After you complete a P2V migration, perform one of the following based on your hypervisor type, and then perform the tasks in the seven steps that follow on the migrated virtual machine guest: • Agent-less hypervisor-If you performed a migration to an agent-less hypervisor where you manually booted the virtual machine using the SMP VM Boot CD, you must disconnect the SMP VM Boot CD, and then manually reboot the virtual machine. • Agent-based hypervisor-If you performed a migration to an agent-based hypervisor: 1. Access the destination virtual machine host remote console and manually shut down the virtual machine. 2. Perform a network configuration for the migrated virtual machine guest. To do so, access the destination virtual machine host remote console to configure the network connections for the migrated virtual machine guest. 3. For Windows 2000 Server migrations to HP integrated VMware ESXi 3.5, if you manually created and booted the virtual machine, then the virtual machine controller type must be changed to a BusLogic controller before powering up the virtual machine. 4. (Optional) Add a CD-ROM component to the destination virtual machine. The CD-ROM might be required to install additional Integrated Components. 5. Power up the migrated virtual machine guest. After the virtual machine reboots, for agent-less and agent-based hypervisors you must perform the following steps on the destination virtual machine guest. Physical-to-virtual (P2V) migrations 79

  • 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
P2V post-migration tasks
After you complete a P2V migration, perform one of the following based on your hypervisor type, and then
perform the tasks in the seven steps that follow on the migrated virtual machine guest:
•
Agent-less hypervisor—If you performed a migration to an agent-less hypervisor where you manually
booted the virtual machine using the SMP VM Boot CD, you must disconnect the SMP VM Boot CD,
and then manually reboot the virtual machine.
•
Agent-based hypervisor—If you performed a migration to an agent-based hypervisor:
Access the destination virtual machine host remote console and manually shut down the virtual
machine.
1.
2.
Perform a network configuration for the migrated virtual machine guest. To do so, access the
destination virtual machine host remote console to configure the network connections for the
migrated virtual machine guest.
3.
For Windows 2000 Server migrations to HP integrated VMware ESXi 3.5, if you manually created
and booted the virtual machine, then the virtual machine controller type must be changed to a
BusLogic controller before powering up the virtual machine.
4.
(Optional) Add a CD-ROM component to the destination virtual machine. The CD-ROM might be
required to install additional Integrated Components.
5.
Power up the migrated virtual machine guest.
After the virtual machine reboots, for agent-less and agent-based hypervisors you must perform the following
steps on the destination virtual machine guest.
Physical-to-virtual (P2V) migrations
79