Article number
000002884
Affected Versions
All
Source Hypervisor
AWS
Target Hypervisor
VMware

Problem with AWS Native VMs BSOD When Recovering to vCenter

Viewed 298 times

Summary

An administrator upon performing recovery of a Windows VM that was born in AWS to vCenter is booting into a BSOD.

Root Cause

This issue can occur when the appropriate drivers cannot be located by Windows on boot.

Symptoms

Native born AWS Windows VM fails to boot and results in a BSOD

Solution

Windows 2008 and Windows 7 (LSI SAS)

Windows 2008 and Windows 7 have the LSI SAS driver installed by default, but they require a registry key to activate it:

  1. Confirm that the target machine has lsi_sas.sys present in the C:\Windows\System32\Drivers directory. This should be included by default during the installation of Windows. If it is missing, copy it from a working virtual machine.

  2. Power on a working Windows 2008 or Windows 7 virtual machine.

  3. Click Start > Run, type regedit, and press Enter.

  4. Navigate to and export this registry key (right-click Export):

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LSI_SAS

  5. Import the registry keys from step 4 into the source system to be converted.

    Note: Before making any registry modifications, ensure that you have a current and valid backup of the registry and the virtual machine. For more information on backing up and restoring the registry, see the Microsoft article 136393.

  6. Restart the source system to complete installation. This requires downtime for the source system.

  7. Perform another conversion with VMware Converter.

 

Windows 2003 (lsilogic and vmscsi)

To copy the appropriate disk controller driver from a working virtual machine with Windows 2003 installed:

  1. Power on the source for the conversion. The source can be physical or virtual.

  2. Power on a working virtual machine running Windows 2003.

  3. Copy the LSI Logic disk controller driver file located at %systemroot%\system32\drivers\symmpi.sys to the source for the conversion.

  4. Copy the VMware SCSI disk controller device driver file (if present) located in %systemroot%\system32\drivers\vmscsi.sys to the source for the conversion.

  5. Click Start > Run, type regedit, and press Enter.

  6. Browse to and export these registry keys:

    • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\symmpi

    • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\
      pci#ven_1000&dev_0030

    • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\vmscsi


    Note: The vmscsi service registry key may not exist if VMware Tools is not installed on the virtual machine.

  7. Import the registry keys from step 6 into the conversion source.

    Note: Before making any registry modifications, ensure that you have a current and valid backup of the registry and the virtual machine. For more information on backing up and restoring the registry, see the Microsoft article 136393.

  8. Restart the source to complete installation.

  9. Perform another conversion with VMware Converter.