HP ProLiant ML350p HP Insight Server Migration Software for ProLiant User Guid - Page 80

Virtual-to-virtual (V2V) migrations, Preparing for a V2V migration

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

Page 80 highlights

1. Modify the system host name. 2. Perform one of the following: • For VMware products, install the VMware Tools in the virtual machine. • For Microsoft Virtual Server 2005, install Virtual Machine Additions in the virtual machine. • For HP integrated Citrix XenServer, install Xen Guest Tools in the virtual machine. • For Hyper-V, install Integration Tools in the virtual machine. 3. Check the network connections and re-establish network connectivity. If an IP address conflict occurs when setting the static IP address, see http://support.microsoft.com/kb/269155/ for more information. 4. View the Windows event log on the destination server and disable any services or drivers that might have failed. 5. If applicable, then reassign drive letters of dynamic disk partitions using the disk manager to correspond with the original state. The virtual machine guest automatically detects new hardware and installs the required drivers. 6. When prompted to reboot, click Yes to restart the virtual machine guest. The mouse and keyboard might not be immediately active on the migrated virtual machine guest. Wait until all required drivers are automatically installed by the guest operating system, and reboot the migrated virtual machine guest when prompted. 7. To activate a graphical boot process, remove the /bootlog and /sos options from the boot.ini file. These options are automatically inserted during the migration process so that the boot process is logged in detail for onscreen analysis. The active boot entry displayed during boot is highlighted and the original boot.ini entry appears as HP SMP Preserved: [name], where [name] is the operating system. Additionally, to retain the original boot parameters, copy all valid flags from the original entry and consider other appropriate boot flags as applicable, such as adding the /3GB flag only if the destination virtual machine is configured with sufficient RAM. Then delete the original (preserved) entry, which has been struck through in the following example. [boot loader] default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS timeout=30 [operating systems] multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windows Server 2003, Enterprise" /sos /bootlog /noexecute=optout /fastdetect multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="HP SMP Preserved: Windows Server 2003, Enterprise" /userva=3030 /3gb /noexecute=optout /fastdetect Virtual-to-virtual (V2V) migrations A virtual-to-virtual (V2V) migration enables migration of a Windows virtual machine guest between virtualization layers. Preparing for a V2V migration The following sections list prerequisites for a V2V migration. If you use a firewall, see the Configuring SMP with a firewall section in this guide. 80 Using SMP for server migration

  • 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
1.
Modify the system host name.
2.
Perform one of the following:
•
For VMware products, install the VMware Tools in the virtual machine.
•
For Microsoft Virtual Server 2005, install Virtual Machine Additions in the virtual machine.
•
For HP integrated Citrix XenServer, install Xen Guest Tools in the virtual machine.
•
For Hyper-V, install Integration Tools in the virtual machine.
3.
Check the network connections and re-establish network connectivity. If an IP address conflict occurs
when setting the static IP address, see
ht
tp://suppor
t
.mic
r
o
s
o
f
t
.com/kb/2
6
9
1
5
5/
for more information.
4.
View the Windows event log on the destination server and disable any services or drivers that might
have failed.
5.
If applicable, then reassign drive letters of dynamic disk partitions using the disk manager to correspond
with the original state. The virtual machine guest automatically detects new hardware and installs the
required drivers.
6.
When prompted to reboot, click
Yes
to restart the virtual machine guest.
The mouse and keyboard might not be immediately active on the migrated virtual machine guest. Wait
until all required drivers are automatically installed by the guest operating system, and reboot the
migrated virtual machine guest when prompted.
7.
To activate a graphical boot process, remove the /bootlog and /sos options from the
boot.ini
file.
These options are automatically inserted during the migration process so that the boot process is logged
in detail for onscreen analysis. The active boot entry displayed during boot is highlighted and the
original boot.ini entry appears as
HP SMP Preserved: [name]
, where [name] is the operating
system.
Additionally, to retain the original boot parameters, copy all valid flags from the original entry and
consider other appropriate boot flags as applicable, such as adding the /3GB flag only if the destination
virtual machine is configured with sufficient RAM.
Then delete the original (preserved) entry, which has been struck through in the following example.
[boot loader]
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
timeout=30
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS=
”
Windows Server 2003, Enterprise
”
/sos /bootlog
/noexecute=optout /fastdetect
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS=
”
HP SMP Preserved: Windows Server 2003, Enterprise
”
/userva=3030 /3gb /noexecute=optout /fastdetect
Virtual-to-virtual (V2V) migrations
A virtual-to-virtual (V2V) migration enables migration of a Windows virtual machine guest between
virtualization layers.
Preparing for a V2V migration
The following sections list prerequisites for a V2V migration.
If you use a firewall, see the
Configuring SMP with a firewall
section in this guide.
80
Using SMP for server migration