Suggested action – HP Insight Foundation Software for ProLiant User Manual

Page 68

Advertising
background image

Mouse and keyboard do not work after a Microsoft Hyper-V virtual machine is
migrated to a ProLiant server

Suggested action

If the mouse and keyboard do not work after you migrate a Microsoft Hyper-V virtual machine to
a ProLiant server, reboot the destination server.

If rebooting does not solve the issue, try the following:

Remove Microsoft Hyper-V Integration Tools on the source virtual machine before you perform
a migration.

Rerun the migration, but select Automatic PSP installation in the migration wizard so that the
PSP is installed automatically on the destination server after a migration.

Rerun the migration, but select Use DevCon in the migration wizard so that DevCon is installed
automatically on the ProLiant server at the end of the migration.

Static IP address cannot be assigned on the destination server after migration

Assigning a static IP address on the destination server might result in an error similar to the following:

The IP address xxx.xxx.xxx.xxx you have entered for this network adapter

is already assigned to another adapter.

This scenario can occur if the IP address is assigned to a network adapter on the source server.

Suggested action

For more information, see the following website:

http://support.microsoft.com/kb/269155/en-us

Virtual machine hosts Integrated Components that are not installed on the destination
virtual machine after migration

Suggested action

Try the following:

1.

Power down the destination virtual machine.

2.

Add a CD-ROM drive to the virtual machine.

3.

Power up the virtual machine, and then restart the installation of the Integrated Components.

Exclamation point (!) appears on the NIC adapter in Device Manager on the migrated
virtual machine

After a migration, the NIC adapter might not appear on the destination virtual machine. This might
happen during V2V migrations between VMware Server and VMware ESX servers. This might also
happen when a virtual machine is migrated from one Microsoft Hyper-V host to another Hyper-V
host.

You might be unable to assign the IP address to this device, which does not reappear on the
Network Connections page.

Suggested action

Manually remove the network adapter in Device Manager and trigger a Scan for Hardware
Changes. This action detects the NIC adapter and configures the drivers for it.

68

Troubleshooting

Advertising
This manual is related to the following products: