Sign in
Microsoft.com
 
Windows Server TechCenter
 
 
 
Windows Server TechCenter > Windows Server Forums > Hyper-V > P2V fails at install VM components
Ask a questionAsk a question
Search Forums:
 

AnswerP2V fails at install VM components

  • Saturday, October 17, 2009 2:17 PMJonathon Moore87 Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote

    Hi all,

    I'm trying to use SCVMM to do a P2V for one of our servers, it fails every time at "install VM components"
    after coping the disks with BITS SCVMM starts the VM to install the components, begins installing them and then at some point this causes the VM to blue screen. Once this has happened if I try to start the VM again I always get the same Blue Screen with error 0x0000007b.

    I've virtualised a couple of servers already and had no problems but now always get the same issue, even when I try to do a P2V on a different source server.
    the only think I can think of is that the first servers I virtualised had sata drives and the ones I've tried since have SAS.

    The physical servers that I can't get to virtualise are all dell 2950 machines with SAS drives.

    Surely there must be a way to virtualise a server when the source uses SAS drives?

    for added information these are the errors that are left over in SCVMM once everything has gone wrong;

    Warning (13223)

    An error occurred while Virtual Guest Services were being installed on virtual machine SRV05 residing on host hvh02.uk.jh-austin.co.uk.

    Recommended Action

    See Help for the Virtual Guest Services installer, resolve any issues preventing the installation from succeeding, and then try the operation again.


    Warning (458)

    The Virtual Machine Manager agent could not be removed from SRV05.

    Recommended Action

    Uninstall the Virtual Machine Manager agent using Add or Remove Programs on SRV05.

    Warning (416)

    Agent installation timed out while waiting on service VMMInstallDetector on SRV05.

    Recommended Action

    Ensure that the Windows Installer service is running on SRV05 and try the operation again.

     

Answers

All Replies