HP Insight Control - Manual (Page 77)

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. 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 Insight Control 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
Physical-to-virtual (P2V) migrations for Linux
A P2V migration enables a source physical machine to be migrated to a virtual machine guest on a Microsoft
Hyper-V, or VMware virtual machine host.
Preparing for a P2V migration
The following sections list prerequisites for a P2V migration.
If you use a firewall, see the Configuring Insight Control with a firewall section in this guide.
Source physical machine prerequisites
•
Verify that a valid network connection exists between the source and destination server.
•
Verify that the source server must contain an active boot partition to be migrated.
•
Complete any pending reboots and software installations on the source machine before initiating a
migration to prevent interrupting the migration process.
•
Temporarily disable any antivirus software autoscans on the source machine to prevent interrupting the
migration process. Re-enable the antivirus software after the migration.
•
To verify that the disks are not corrupted, run a disk defragmenter on the source physical machine
before initiating a migration operation.
•
Verify that all hard drives on the source physical machine are correctly initialized (disk signature written).
•
Verify that all partitions on the source physical machine have a valid file system and are in a healthy
state.
•
Disable all applications and background services on the source machine. After the migrated machine
has synchronized with the new hardware and is assigned a unique network identity, appropriate
applications can be manually re-enabled and configured for the new environment.
•
Temporarily disable HP Management Agents on the source physical machine.
Physical-to-virtual (P2V) migrations for Linux 77