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.

Network adapter in the destination ESX virtual machine is not initialized after a V2V migration

The network adapter in the destination ESX virtual machine might not be initialized after a V2V migration.

Suggested action

1.Log on to the destination server by using the keyboard.

2.Navigate to Device Manager. To do so, right-click My Computer, and then select Manage.

3.Right-click VMware Accelerated AMD PCNet Adapter, and then select Uninstall. The VMware Accelerated AMD PCNet Adapter entry disappears from the list of devices.

4.Select Scan for hardware changes. A valid virtual network adapter appears in Device Manager.

5.Reboot the virtual machine.

Destination virtual machine fails to boot after X2V migration

The destination virtual machine might fail to boot and display the following error: Attempting to load a 64-bit application, however the CPU is not compatible with 64-bit mode or Status : 0xc0000225 The boot selection failed because a required device is missing.

Cause

For a 64-bit OS to load on a virtual machine, Intel-VT must be enabled on the destination virtual machine host.

Suggested action

Enable the Intel-VT option in the system BIOS of the destination virtual machine host and then reboot the virtual machine.

During editing of the settings of guest VMs created by server migration, an invalid OS ID warning appears

After you perform an X2V migration to an ESX Host by using the Automatic Boot feature of the server migration wizard and then change the settings of the migrated VM, the following warning message might appear:

The guest OS ID <guest name> is not valid.

Suggested action

Follow the suggestion provided in the warning message to resolve the issue.

Postmigration 69