Четверг, 28.03.2024, 18:16
Приветствую Вас Гость | RSS
Мой сайт
Главная
Регистрация
Вход
Форма входа

Меню сайта

Категории раздела
Об ОС Windows [137]
В категории размещаются статьи, касающщиеся операционных систем от Microsoft.
Об ОС *Nix [198]
В данной категории собраны статьи об ОС семейства Unix/Linux/FreeBSD/...
Справочные материалы [351]
Справка по всему разделу.
Виртуализация и Облака [46]
Networks & Routing [86]
DataBases [22]

Наш опрос
Оцените мой сайт
Всего ответов: 209

Статистика

Онлайн всего: 1
Гостей: 1
Пользователей: 0

Главная » Статьи » Системное администрирование » Об ОС Windows

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

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:

  1. Mount the VHD to examine the contents
  2. Within the VHD, locate the SYSTEM registry and mount it with RegEdit (\windows\system32\config\system)
  3. 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
 
 
 
 
 
 
 
 
Comments

 
  •  

     

    Love it!  Thanks for sharing how to fix this Michael.

     

     
  •  

     

    this is nice however i have a question. should i not put them under  HKEY_LOCAL_MACHINE\System\ControlSet001\Services\atapi or leave out system? sorry for a dumb question. i was just wondering.thanks so much for your help.

     

     
  •  

    @sbalk - You are correct. I updated the post. Thanks!

     

     
  •  

    Thanks! Thanks! Thanks! It works!!!

     
  •  

    Thanks! Thanks! Thanks! It works!!!

     
  •  

    Mike, we are experiencing a similar issue with virtual hard disks that are created from existing Windows Vista machines. One .vhd came from a laptop and the other from a HP workstation, but both yield the same stop error when booting in Hyper-V on Windows 8.1. We tried the above registry fix for one .vhd disk however we received a Winload.exe error c000000e error on boot. Any thoughts on how to correct this for Windows Vista .vhd disks? Thanks, David Lloyd

     
  •  

    great help, thanks!

     
  •  

    Thanks a lot works great!!!!!

     
  •  

    I owe you a beer. Worked like a champ. Like some said before, this should absolutely be worked out by Microsoft by now.

     
  •  

    Thanks!

     
  •  

    You are a god among men, sir. Just make sure you modify your .reg file to match what you have on your system. I had to do it a couple times but once I actually paid attention, WHAMMY!

     
  •  

    This worked for me after i used Microsoft Windows Backup to image a physical HP Proliant DL360 G7 server and restore into Hyper-V 2012 R2 virtual and changed the reg key below:


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

    TO

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


    Thanks allot for doing this article, i saved heaps of time!



Источник: http://blogs.technet.com/b/michs/archive/2011/09/16/p2v-migration-issues-with-hyper-v-stop-0x0000007b.aspx
Категория: Об ОС Windows | Добавил: admin (24.03.2015)
Просмотров: 2396 | Теги: Migration, Windows Server, P2V, Error, BSoD 7b | Рейтинг: 0.0/0
Всего комментариев: 0
Имя *:
Email *:
Код *:
Поиск

Друзья сайта
  • Официальный блог
  • Сообщество uCoz
  • FAQ по системе
  • Инструкции для uCoz


  • Copyright MyCorp © 2024