Solved

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

Posted on 2014-01-20
2
2,295 Views
Last Modified: 2014-11-12
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
Comment
Question by:lenn0x
2 Comments
 
LVL 2

Accepted Solution

by:
Johan Ohlsson earned 500 total points
ID: 39796530
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
 
LVL 1

Author Comment

by:lenn0x
ID: 39810096
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

Do You Know the 4 Main Threat Actor Types?

Do you know the main threat actor types? Most attackers fall into one of four categories, each with their own favored tactics, techniques, and procedures.

Join & Write a Comment

It Is not possible to enable LLDP in vSwitch(at least is not supported by VMware), so in this article we will enable this, and also go trough how to enabled CDP and how to get this information in vSwitches and also in vDS.
In this article, I will show you HOW TO: Perform a Physical to Virtual (P2V) Conversion the easy way from a computer backup (image).
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles from a Windows Server 2008 domain controller to a Windows Server 2012 domain controlle…
This tutorial will walk an individual through the process of installing of Data Protection Manager on a server running Windows Server 2012 R2, including the prerequisites. Microsoft .Net 3.5 is required. To install this feature, go to Server Manager…

762 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

Need Help in Real-Time?

Connect with top rated Experts

20 Experts available now in Live!

Get 1:1 Help Now