?
Solved

VMWare ESXi P2V conversion - SCSI drivers?

Posted on 2009-12-21
5
Medium Priority
?
3,534 Views
Last Modified: 2016-10-27
I have been fighting with a conversion of an NT4 physical server to an ESXi v3.5  VM for awhile now and I've gotten to a point where I've used Acronis TI to actually create a vmdk file that I can attach to a new VM with no disks assigned.

The problem occurs during boot when I get a BSoD and an INACCESSIBLE_BOOT_DEVICE stop error.  I found the following solution on VMWare's KB, but I want to make sure that making these registry changes won't cause my server to do anything crazy before I reconvert the machine (like not boot).  Any input on the effects of changing these registry settings would be much appreciated.

From http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1005208
***********************************************************************************************************
 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 in %systemroot%\system32\drivers\buslogic.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.
   6.
      Type regedit and press Enter.
   7.
      Browse to and export the following registry keys:

      HKEY_LOCAL_MACHINE\SYSTEM\CurrentSet001\Services\BusLogic

      HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\CriticalDeviceDatabase\pci#ven_104b&dev_1040

      HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\vmscsi

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

   8.
      Import the registry keys from step 6 on to the conversion source.
   9.
      Restart the source to complete installation.
  10.
      Perform another conversion with VMware Converter.
0
Comment
Question by:BenderBender
  • 2
  • 2
5 Comments
 
LVL 2

Expert Comment

by:e2p2
ID: 26101807
What you need to use is the VMWare Standalone Converter.

http://www.vmware.com/products/converter/get.html

With this you can convert the VMDK image and import it into ESX.  This may sound like an unnecessary step but one of the last options in the Advanced Options section is to "reconfigure destination virtual machine".  This will correct the inaccessible boot device error message.

Although I have not tried it with an NT4 server you may be able to use the Standalone Converter to convert the original server with out having to go through the intermediate step using the Acronis software.
0
 
LVL 1

Accepted Solution

by:
BenderBender earned 0 total points
ID: 26108277
I had tried using the Standalone converter to move the Physical NT4 server over to the ESXi host, but that failed every time.  I

I ended up performing a 'cold' cloning of the disk with Acronis after copying the above registry settings and installing the appropriate driver files.  I then used a separate install of VMWare Converter 4.0 to change that file into a VM on the host, which worked, but showed a failure when the converter tried to "Configure" the VM.

Luckily, the VM still booted up (I assume due to changing the registry and adding the Buslogic.sys file).  I was then able to install VMWare tools and now I am just looking to install a new network card, as that didn't install properly.
0
 
LVL 2

Expert Comment

by:e2p2
ID: 26108344
The NIC is virtual of course.  I would recommend starting with the E1000 NIC, since that should be the most compatible with NT4.
0
 
LVL 1

Author Comment

by:BenderBender
ID: 26108662
I actually used this article http://www.experts-exchange.com/Software/VMWare/Q_23954358.html to add an AMD ethernet adapter and it worked like a charm.
0
 
LVL 21

Expert Comment

by:za_mkh
ID: 26111341
The AMD Ethernet Adaptor is the only one that works with NT4 ... loading the VMTools in the OS then loads the correct VMWare aware NIC driver for NT4..
0
Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This is an update to some code that someone else posted on Experts Exchange. It is an alternate approach, I think a little easier to use, & makes sure that things like the Task Bar will update.
In this tutorial, we’re going to learn how to convert Youtube to mp3 for Free. We'll show you how easy it is to make an mp3 from your video clips so that you can enjoy them offline.
Get a first impression of how PRTG looks and learn how it works.   This video is a short introduction to PRTG, as an initial overview or as a quick start for new PRTG users.
How to fix incompatible JVM issue while installing Eclipse While installing Eclipse in windows, got one error like above and unable to proceed with the installation. This video describes how to successfully install Eclipse. How to solve incompa…

609 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question