HP Virtual Connect Enterprise Manager Software - Manual (Page 7)

Suggested action......................................................................................................58
Unrecoverable sector-read errors on the source server hard drive are not supported and fail
a Windows P2P or P2V migration...................................................................................58
Cause.....................................................................................................................58
Suggested action......................................................................................................58
Source Agent fails to launch when source server reboots in migration agent mode.................58
Suggested action......................................................................................................58
Error during data copy of Linux migration.........................................................................58
Cause.....................................................................................................................59
Suggested action......................................................................................................59
SAN-connected destination server displays blue screen......................................................59
Suggested action......................................................................................................59
Out of memory error occurs on the application station during migration...............................59
Suggested action......................................................................................................59
Destination server boots with an invalid IP address............................................................59
Cause.....................................................................................................................59
Suggested action......................................................................................................59
Windows server migration Source Agent or PINT remote deployment fails with Agent is already
deployed or not required error........................................................................................59
Suggested action......................................................................................................60
Windows server migration Source Agent or PINT remote deployment is intermittent and
deployment fails with General failure occurred error..........................................................60
Suggested action......................................................................................................60
Post-migration ...................................................................................................................60
Migration does not start after confirmation. The event log continuously displays Operation
Migration waiting for connection to source.......................................................................60
Suggested action......................................................................................................60
Destination server mouse and keyboard do not work after a Windows migration...................60
Suggested action......................................................................................................60
USB Mouse or Keyboard Drivers Not Loaded After a X2P Windows Migration......................61
Cause.....................................................................................................................61
Suggested action......................................................................................................61
Mouse does not work on the destination server's iLO after a Linux X2P migration...................62
Suggested action......................................................................................................62
Mouse does not work on the destination ESX virtual machine after a V2V migration...............62
Suggested action......................................................................................................62
Drive letters are not the same in the migrated virtual machine guest after migration................62
Suggested action......................................................................................................62
Drives do not appear on the migrated operating system.....................................................63
Suggested action......................................................................................................63
Mouse and keyboard do not work after migrating a Microsoft Hyper-V virtual machine to a
ProLiant server..............................................................................................................63
Suggested action......................................................................................................63
Static IP address cannot be assigned on the destination server after migration.......................63
Suggested action......................................................................................................63
Virtual machine hosts Integrated Components do not install on the destination virtual machine
following migration........................................................................................................63
Suggested action......................................................................................................63
Exclamation point (!) appears on the NIC adapter in Device Manager on the migrated virtual
machine......................................................................................................................63
Suggested action......................................................................................................64
Network adapter in the destination ESX virtual machine is not initialized after a V2V
migration.....................................................................................................................64
Suggested action......................................................................................................64
The destination virtual machine fail to boot after X2V migration...........................................64
Contents 7