Windows Server TechCenter > Windows Server Forums > Hyper-V > Had to reinstall Windows Server, now I can't start VM's
Ask a questionAsk a question
 

AnswerHad to reinstall Windows Server, now I can't start VM's

  • Thursday, October 08, 2009 9:24 PMsrvradmin Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    Due to a problem with the host server, I had to re-install Windows Server 2008.  The Virtual Machines that were created on the original box were on a different partition and are still intact, but they were NOT exported from the original Server install.  How can I mount the VHD's on the newly reinstalled server?  If I try to import, I get a message saying "You can import a virtual machine only if you used Hyper-V to create and export it."

    I also tried to create a new VM, but pointed it to the existing VHD file, and it then appeared in the Hyper-V Manager, but when I try to start it, it said "Boot failure, reboot and select proper boot device"

Answers

  • Friday, October 09, 2009 3:28 AMVincent HuMSFT, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer

    Hi,

     

    Do you have any other VHDs come from Windows Server2008? Please make a copy of them and then use the existing VHDs to create VMs to test whether you get the same issue.

     

    Generally speaking, the VHDs come from Windows Server 2008 can work properly in Windows Server 2008 R2.

     

    By the way, according to the description, we find it seems to be system crash issue and we need to analyze the crash dump file to narrow down the root cause of the issue. Unfortunately, it is not effective for us to debug the crash dump file here in the forum. Therefore, I would like to suggest that you contact Microsoft Customer Service and Support (CSS) via telephone so that a dedicated Support Professional can assist with your request.

     

    To obtain the phone numbers for specific technology request please take a look at the web site listed below:

     

    http://support.microsoft.com/default.aspx?scid=fh;EN-US;OfferProPhone#faq607

     

     

    Hope the issue will be resolved soon.

     

    Best Regards,

    Vincent Hu

     

All Replies

  • Thursday, October 08, 2009 9:46 PMJoseph Noga Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    Check the BIOS boot order on the Guest VM to make sure hard disk at the top of the list.  It might be looking at the CD Rom for the boot option.


    Joseph Noga MCITP, MCSE, MCSA, MCTS CCNA,CCDA,CCVP Managing Consultant VSD Technologies
  • Thursday, October 08, 2009 10:10 PMBrianEhMVP, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Did your VMs have any sort of snapshot history?

    Since you reinstalled Server 2008 - did you apply SP2 or apply the Hyper-V specific patches?

    Brian Ehlert (hopefully you have found this useful)
  • Thursday, October 08, 2009 10:31 PMsrvradmin Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    I checked the boot order and set it to the hard disk, same thing...

    No, they didn't have a snapshot history.

    When I reinstalled, I went from 2008 x64 RTM to 2008 R2.  All patches were applied prior to the rebuild.  All patches applied after the rebuild.

    After a lot of playing around with different things, I started to get an ide/atapi permissions error.  After clearing that up, I got one of the VM's to boot.  Unfortunately, I didn't learn, and I tried to run the Integration Services Setup Disk before exporting or taking a snapshot, and now it is just blue screening with a Stop:  0x0000007B (0x803A0BB0, 0XC0000034, 0X00000000, 0x00000000)
  • Friday, October 09, 2009 3:28 AMVincent HuMSFT, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer

    Hi,

     

    Do you have any other VHDs come from Windows Server2008? Please make a copy of them and then use the existing VHDs to create VMs to test whether you get the same issue.

     

    Generally speaking, the VHDs come from Windows Server 2008 can work properly in Windows Server 2008 R2.

     

    By the way, according to the description, we find it seems to be system crash issue and we need to analyze the crash dump file to narrow down the root cause of the issue. Unfortunately, it is not effective for us to debug the crash dump file here in the forum. Therefore, I would like to suggest that you contact Microsoft Customer Service and Support (CSS) via telephone so that a dedicated Support Professional can assist with your request.

     

    To obtain the phone numbers for specific technology request please take a look at the web site listed below:

     

    http://support.microsoft.com/default.aspx?scid=fh;EN-US;OfferProPhone#faq607

     

     

    Hope the issue will be resolved soon.

     

    Best Regards,

    Vincent Hu