none
p2v fails during "'Make operating system virtualizable" phase

    Question

  • Hi,

    Here is my situation, I'm doing a P2V conversion and the process fails during "'Make operating system virtualizable" phase.

    I am running SCVMM 2008 R2 SP1, converting a physical machine with Windows Server 2003 R2 64 bits on a different Hyper-V host as the VMM Server that has running Windows Server 2008.

    What I realized is that the VHD were created but the VM was not configured (if I open settings dialogue the IDE controllers are empty with no drives). So i cut the process and I tried to add the VHD to the VM Settings but when I try to start the machine it reported an error saying that another process was using the file (is like the VHD was mounted by a process). So then I restarted a service called "Hyper-V Image something..." and then I could start the machine, but then a BSOD happens with error number 0x0000007B.

    I read that in some case if the source machine was using scsi drives (my case) but the target vm machine use IDE drives, that BSOD happens but I knew that SCVMM have to take care about that.

    I found several issues in internet about similar behavior, but in order to understand and to find a clue, what are the exact steps involved in the P2V process?

    What i really know is that SCVMM host machine, physical source machine and the target hyper-v host machine do not have all software updates. But could it be something that was fixed by an update? and wiche update is involved?

    thanks

    Tuesday, September 06, 2011 3:08 PM

Answers

  • Try this:

    http://support.microsoft.com/default.aspx?scid=kb;en-us;2007086

    Also, search your registries for "UpperFilters" and "LowerFilters" prior to P2V in case you have references still lingering. You can usually track down culprits of post P2V STOP 0x7B's this way.


    Steve Thomas, SSEE, Microsoft
    App-V/MED-V/SCVMM/SCCM/AppCompat
    http://madvirtualizer.wordpress.com/
    The App-V Team blog: http://blogs.technet.com/appv/
    The MED-V Team Blog: http://blogs.technet.com/medv
    The SCVMM Team blog: http://blogs.technet.com/scvmm/

    “This posting is provided "AS IS" with no warranties, and confers no rights. User assumes all risks.”
    Thursday, September 08, 2011 4:15 PM
    Moderator

All replies

  • Any idea?


    Cristian L Ruiz
    Wednesday, September 07, 2011 11:54 PM
  • Try this:

    http://support.microsoft.com/default.aspx?scid=kb;en-us;2007086

    Also, search your registries for "UpperFilters" and "LowerFilters" prior to P2V in case you have references still lingering. You can usually track down culprits of post P2V STOP 0x7B's this way.


    Steve Thomas, SSEE, Microsoft
    App-V/MED-V/SCVMM/SCCM/AppCompat
    http://madvirtualizer.wordpress.com/
    The App-V Team blog: http://blogs.technet.com/appv/
    The MED-V Team Blog: http://blogs.technet.com/medv
    The SCVMM Team blog: http://blogs.technet.com/scvmm/

    “This posting is provided "AS IS" with no warranties, and confers no rights. User assumes all risks.”
    Thursday, September 08, 2011 4:15 PM
    Moderator
  • Thanks Steve,

    I have read that microsoft article but is not that case because there said something about a registry value but is correct in the source machine.

    What I going to try is to tell the customer to update the three servers, the source and the target machine, and the one that have the VMM server and console.

    If the procedure fails again, Im going to try a repair (update) with the Windows 2003 CD Installation media.

    But someone have any other idea?


    Cristian L Ruiz
    Monday, September 12, 2011 8:28 PM
  • What processors do you have?
    Thursday, October 11, 2012 11:20 PM