Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

A System Center Virtual Machine Manager 2008 P2V hangs at 70% - The new VM boots to a STOP:0x7B


Symptoms

Attempting a System Center Virtual Machine Manager 2008 (SCVMM) Physical to Virtual conversion (P2V) fails with Error (1730) at 70%.  More specifically, the P2V conversion seems to hang at 70% in the VMM console.
 
Another Symptom that might be noticed would be that the P2V job has Completed w/ Info.
Warning (13210)
Timeout occurred while waiting for VM integration services to be installed on virtual machine <name> residing on host <host>

Recommended Action
Ensure that the version of the VM integration services binaries matches the version of the guest operating system in the virtual machine and then try again.

 
If you open the Hyper-v console on the host where the VM is being placed, you'll notice that the VM is in a reboot loop. If you connect to the VM, the reboot loop is actually a ST0P: 0x0000007b bugcheck.

↑ Back to the top


Cause

This problem can occur if a certain registry setting has been changed from the default value on the P2V Source machine used in the conversion.

↑ Back to the top


Resolution

The resolution is to return the default value to the following registry key:
 
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Wdf01000\Group] = Base
 
Change the value above from "Base" to "WdfLoadGroup" on the P2V Source machine used in the conversion.

↑ Back to the top


More Information

We have seen several cases of this problem where in each case the server was originally built using the Dell OpenManage CD.

↑ Back to the top


Keywords: vkball, kb

↑ Back to the top

Article Info
Article ID : 2007086
Revision : 1
Created on : 1/8/2017
Published on : 3/21/2011
Exists online : False
Views : 118