Sign in
 
Home2012Previous VersionsLibraryForumsGallery
System Center TechCenter >
> 
> 
Problems converting physical machine

Answered Problems converting physical machine

  • Thursday, October 11, 2007 10:21 AM
     
     
    Sign In to Vote
    0

    Hi,

     

    I'm having problems doing P2V.

     

    The process runs okay and converts to a virtual machine without any issues. However, when trying to start the server after the conversion the server hangs during startup. I have tried to startup in debugging mode as well as in safe mode, but no luck.

     

    The only thing that seems to help is doing a repair install with the Windows 2003 CD.

     

    The hardware that I'm trying to virtualize is based on HP Proliant series, e.g. DL380, DL360 etc.

     

    Any suggestions?

     

    /Henrik

     

All Replies

  • Saturday, October 13, 2007 7:19 PM
     
     
    Sign In to Vote
    0

    Hi all,

     

    We have just the same problem with DL380 P2V conversion.

    Safe Mode promt shows hanging on acpitabl.dat loading.

    Has anybody any ideas or workarounds?

     

    Best Regards,

    Eugene.

     

     
  • Tuesday, October 16, 2007 2:08 PM
     
     
    Sign In to Vote
    0

     

    FYI, I had a VM that hung on acpitabl.dat during safe-mode boot as well and it was because I was trying (experimentaly!) to swap out the single processor acpi hal.dll with the multi-processor one in order to see if dual core CPUs would show up (I know that all documentation says you can't do that but I had time on my hands and was proving a concept for my boss and a customer).  Putting the correct (single processor) hal.dll back let the server boot properly again.
     
  • Friday, October 19, 2007 2:16 PM
     
     
    Sign In to Vote
    0
    I just had the same problem last week, but must've gotten lucky.  When the virtual server booted for the first time, the CPU would spike and hang around 98-100%.  Since it was doing something, I let it sit for about 15-20 minutes and it eventually loaded the OS (in safe mode).  After logging it, it went through its normal routine of installing the new hardware, and I'm assuming it fixed itself by installing the new processor and appropriate .dlls.  Best of luck to you!

     

     
  • Monday, October 22, 2007 10:27 PM
     
     Answered
    Sign In to Vote
    0

     

    what is the OS version, incl the latest SP, on the source machine?

    what is the file system on the source machine's boot & system volumes?

    can you post the output of 'filever /v %WinDir%\system32\hal.dll' from  the source machine?

    also, can you check the configuration of the resulting VM. What bus (ide\scsi) are the boot & system vhds assigned to?