Knowledge Base

The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides
 
Search the VMware Knowledge Base (KB)   View by Article ID
 

Injecting SCSI controller device drivers into Windows when it fails to boot after converting it with VMware Converter (1005208)

Symptoms

  • Conversion fails between 97% and 99%.
  • The virtual machine is created on the destination.
  • The virtual machine which was created fails to start after conversion.
  • Windows boots to a blue screen error:

    • STOP 0x7B INACCESSIBLE_BOOT_DEVICE
    • STOP 0x0000007B INACCESSIBLE_BOOT_DEVICE

Purpose

This article provides instructions on copying the appropriate disk controller driver from a working virtual machine onto a physical or virtual machine prior to conversion to resolve a STOP 0x7B failure when using VMware Converter, or if the SCSI adapter has been changed.

This issue can occur when the appropriate drivers cannot be located by Windows on boot, and must be manually copied to resolve.

Resolution

All Windows Versions (vmscsi only)

To copy the appropriate disk controller driver from a working virtual machine with a Windows guest operating system:
  1. Power on the source for the conversion. The source can be physical or virtual.
  2. Download the VMware SCSI Disk Controller driver diskette at:

    http://download3.vmware.com/software/vmscsi-1.2.0.4.flp

  3. If the source is virtual, attach the driver diskette to the virtual machine's virtual floppy drive.
  4. If the source is physical, use any of these methods to copy the files from the diskette image:

    • Extract the disk image into files and copy them to the source.
    • Attach the diskette to a virtual machine and copy the files from the virtual diskette drive to the physical source.
    • Write the contents of the image onto a floppy diskette and insert the diskette into the physical source.

      Note: Image extraction software is required to use this method.

  5. Access the floppy diskette or files on the source from My Computer.
  6. Right-click vmscsi.inf and click Install. The VMware SCSI drivers are installed.
  7. Restart the source to complete installation.
  8. Perform another conversion with VMware Converter.

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)

Note: This is not a VMware issue. Complete this workaround.

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.

Windows XP / 2000 / NT (buslogic and vmscsi)

To copy the appropriate disk controller driver from a working virtual machine with a Windows XP/2000/NT guest operating system:
  1. Power on the source for the conversion. The source can be physical or virtual.
  2. Power on a working virtual machine running a matching version of Windows.
  3. Copy the Buslogic disk controller device driver file located at %systemroot%\system32\drivers\buslogic.sys to the source for the conversion.
  4. Copy the VMware SCSI disk controller device driver file (if present) located at %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\BusLogic
    • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\
      pci#ven_104b&dev_1040
    • 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.


Additional Information

Tags

boot-vm-fails  cannot-boot-vm  conversion-converter  unable-to-boot-vm

See Also

This Article Replaces

1008827

Update History

04/27/2011 - Updated title, added explanation to why this may occur.

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Feedback

  • 92 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.
What can we do to improve this information? (4000 or fewer characters)
  • 92 Ratings
Actions
KB: