Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 581
  • Last Modified:

Migrating a PowerEdge 2400 System to a Hyper-V virtual machine

We have an old Dell PowerEdge 2400 (Pentium 3 class) running Windows Small Business Server 2003. We are trying to virtualize this machine and run it with Hyper-V on a newer server, but are running into problems with getting the virtual machine started.

Converting the physical machine into a virtual machine seems to have worked easily, but the snag we're running in to involves boot discs and media controllers. The physical machine has all of its devices attached via SCSI, but Hyper-V only supports booting from IDE. I can mount the boot drive as IDE and Windows will begin to load, but it crashes with a blue screen every time. The BSOD shows an error code of 0x0000007b, which refers to an Inaccessible Boot Device.

We have already tried modifying the registry (loading an recovery disc and accessing the registry file) to enable IDE boot devices, but that does not work. We've also tried mounting the images on a SCSI controller, but Hyper-V does not support booting from SCSI. We've also tried using Virtual Box to mount the drives, it will not load the OS at all.

Any suggestions to help get this virtual machine running are welcome.
0
hvconsulting
Asked:
hvconsulting
  • 2
1 Solution
 
Schnell SolutionsSystems Infrastructure EngineerCommented:

Hello,

You are making it in the correct way when you configure the boot disk as IDE. It is not possible with SCSI drive

Some operating systems disk controllers are affected when you convert a physical machine to virtual because the hal mades a deep reference to this device. There are ways to solutions these problems, but personally I make it very often, and what is easier in most of the cases is make a new PARALLEL installation of the same version of Windows in the same disk. It will rebuild the HAL of your boot device, will install/replace the correct driver and will prepare the system too boot up. After having two windows installations, you can point via the boot.ini to the oritinal one and delete the new parallel windows folder and the boot.ini reference

If you don't want to use this way, you can do it with the normal process that begins starting up the virtual machine with the CD of windows server 2003, open the repair console and try the commands: fixboot, fixmbr and follow the processes described in the microsoft web site:

http://technet.microsoft.com/en-us/library/bb457122.aspx#EEAA


0
 
hvconsultingAuthor Commented:
Thank you for your answer. We will look into these solutions the next time we have someone on site and let you know how it works for us.
0
 
Schnell SolutionsSystems Infrastructure EngineerCommented:
Ok, let us know

You can use the simple repair steps. If it doesn't work jump to the large option that always work in this cases where the operating system can not start up because disk controller related problems (Temporal Parallel Install)

0

Featured Post

Visualize your virtual and backup environments

Create well-organized and polished visualizations of your virtual and backup environments when planning VMware vSphere, Microsoft Hyper-V or Veeam deployments. It helps you to gain better visibility and valuable business insights.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now