• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2713
  • Last Modified:

how p2v (Hyper-V) a server2003 with LSI MegaRaid Disks

Hi,

I have a Hyper-V 2012 Server and
I want to virtualize a Windows Server2003 that is installed on a LSI MegaRaid Raid-1. (no IDE or SATA drives)

I made a vhd from the Win2003 system and created a new machine in Hyper-V2012 using the vhd , but after booting it gives me a bluescreen (Stop ox0000007B)
Probably because there are no drivers for the Hyper-V IDE-Controller in the Server 2003 VHD.
I also changed the disktype from IDE to SCSI in Hyper-V, but that does not help.

My question is, what do I have to install in the running Server2003 machine so that it works in Hyper-V?

Regards

Lennox
0
lenn0x
Asked:
lenn0x
1 Solution
 
Johan OhlssonMS Production Server Engineer Commented:
Hello!

Here is an excerpt from Microsodt and I'll also send you the link for this problem. Hope this can help you with your problem.

P2V Migration Issues with Hyper-V: STOP: 0x0000007B


When converting a Windows XP / Windows 2003 machine with P2V utilities, a STOP: 0x0000007B may occur during boot in Hyper-V. (Pressing F8 during boot and selecting the option to "Disable automatic restart on system failure" will reveal the blue screen error code.) Typically this indicates the lack of a necessary driver required by Hyper-V virtual hardware (IDE channel).

To confirm the issue relates to this article, follow these steps:

Mount the VHD to examine the contents
Within the VHD, locate the SYSTEM registry and mount it with RegEdit (\windows\system32\config\system)
Check the file system and registry for these entries
Confirm Files Exist
windows\system32\drivers\intelide.sys
windows\system32\drivers\pciide.sys
windows\system32\drivers\atapi.sys
Confirm Registry Entries Exist
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\CriticalDeviceDatabase\pci#ven_8086&dev_7111
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\CriticalDeviceDatabase\pci#ven_8086&dev_7110&cc_0601
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\CriticalDeviceDatabase\primary_ide_channel
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\CriticalDeviceDatabase\secondary_ide_channel
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\IntelIde
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\PCIIde
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\atapi
Any missing items from step #3 can be remedied through the information given below. Hyper-V requires these critical devices and services to boot; a lack of this information in Windows will result in a 0x0000007B, or perpetually rebooting machine.

Required Registry Critical Boot Entries
pci#ven_8086&dev_7111

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\CriticalDeviceDatabase\pci#ven_8086&dev_7111]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="intelide"

pci#ven_8086&dev_7110&cc_0601

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\CriticalDeviceDatabase\pci#ven_8086&dev_7110&cc_0601]
"ClassGUID"="{4D36E97D-E325-11CE-BFC1-08002BE10318}"
"Service"="isapnp"

primary_ide_channel

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\CriticalDeviceDatabase\primary_ide_channel]
"Service"="atapi"
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
secondary_ide_channel

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\CriticalDeviceDatabase\secondary_ide_channel]
"Service"="atapi"
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"

Required Registry Service Entries
intelide.reg

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\IntelIde]
"ErrorControl"=dword:00000001
"Group"="System Bus Extender"
"Start"=dword:00000000
"Tag"=dword:00000004
"Type"=dword:00000001
pciide.reg

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\PCIIde]
"ErrorControl"=dword:00000001
"Group"="System Bus Extender"
"Start"=dword:00000000
"Tag"=dword:00000003
"Type"=dword:00000001
"ImagePath"=hex(2):73,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,44,00,\
 52,00,49,00,56,00,45,00,52,00,53,00,5c,00,70,00,63,00,69,00,69,00,64,00,65,\
 00,2e,00,73,00,79,00,73,00,00,00
"DisplayName"="Standard IDE/ESDI Hard Disk Controller"

atapi.reg

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\atapi]
"ErrorControl"=dword:00000001
"Group"="SCSI miniport"
"Start"=dword:00000000
"Tag"=dword:00000019
"Type"=dword:00000001
"DisplayName"="Standard IDE/ESDI Hard Disk Controller"
"ImagePath"=hex(2):73,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,44,00,\
 52,00,49,00,56,00,45,00,52,00,53,00,5c,00,61,00,74,00,61,00,70,00,69,00,2e,\
 00,73,00,79,00,73,00,00,00

Required Driver Files
windows\system32\drivers\intelide.sys
windows\system32\drivers\pciide.sys
windows\system32\drivers\atapi.sys
Any missing file may be available from a .CAB within \windows\Driver Cache\
The End

--Mike Schmidt

LINK: http://blogs.technet.com/b/michs/archive/2011/09/16/p2v-migration-issues-with-hyper-v-stop-0x0000007b.aspx
0
 
lenn0xAuthor Commented:
Thanks!!
First it did not help, but after I removed the "ImagePath"=hex(2).." entries from registry it worked perfectly.

Thanks again.
0

Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

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