none
Hypervisor not running error in AMD processor PC

    Frage

  • I have windows 2008 R2 server running on HP Pavilion HPE H8-1210 with AMD FX-6100 processor (six core).  I checked AMD website, and it was confirmed that FX-6100 processor supports virtualization.

    I have enabled both Virtualization and DPE options from BIOS.
    I also have set the "nx" option to be "AlwaysOn" from BCD, and the hypervisor start option has been set to "Auto".

    I even re-installed Hyper-V role, which was successfully installed, but I still cannot start the virtual machine, because I'm getting the error message: "The virtual machine could not be started because the hypervisor is not running."
    Any idea what may be wrong?

    Mittwoch, 1. Februar 2012 15:42

Antworten

Alle Antworten

  • You should not have to change any options in the BCD.

    Once Virtualization and Data Execution Prevention are enabled you need to cold boot the machine.  DEP is not enabled until the machine is cold booted.

    Also, double check the language on the DPE dialog, some BIOS it needs to be on and others it needs to be off due ot the phrasing of the BIOS setting.

    And, be absolutely sure that your hardware supports VT.  Just becuase the motherboard and chipset support it does not mean that the particualr flavor of the chipset that you have does.

    Many vendors cheapen classes of hardware that is below 'workstation' class with chipsets that do not support virutalization, though the chipset family might.  There are lots of flavors.

    Use the Securable tool to test your hardware.

     


    Brian Ehlert (hopefully you have found this useful) http://ITProctology.blogspot.com
    Learn. Apply. Repeat.
    Disclaimer: Backup, test your backup, try new things. Attempting change is of your own free will.
    Mittwoch, 1. Februar 2012 16:06
    Moderator
  • Hi,

     

    Please try to run the following tool to check the compatibility of your computer.

     

    http://www.grc.com/securable.htm

    Note: Please run this tool before you enable Hyper-V role.

     

    Important Note: This response contains a reference to a third party World Wide Web site. Microsoft is providing this information as a convenience to you. Microsoft does not control these sites and has not tested any software or information found on these sites; therefore, Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. There are inherent dangers in the use of any software found on the Internet, and Microsoft cautions you to make sure that you completely understand the risk before retrieving any software from the Internet.

     

     

    Best Regards,

    Vincent Hu

     

     

    Donnerstag, 2. Februar 2012 06:52
    Moderator
  • Thanks for your suggestion. 

    I used the Securable tool (http://www.grc.com/securable.htm) and tested my hardware, and it says that my 64bit machine does support both DPE and Virtualization.  I also tried "disabling" those two settings from BIOS, hoping that it may do completely opposite function, but that did not work either.  I now re-enabled both funtion from BIOS, powered off and on, and tested again, but it is still not working.  Am I missing some driver or software?    

    Donnerstag, 2. Februar 2012 15:55
  • I uninstalled the Hyper-V role, and tested it, and the Securable tool indicated that my machine is okay for both DPE and Virtualization.  Sigh.

    Donnerstag, 2. Februar 2012 16:03
  • Securable just focuses on the main features.

    CPU-Z tells you all:  http://www.cpuid.com/softwares/cpu-z.html

    Including the family and the fine details that you can fully check for your model.

    Also, check the CPU manufacturers site for the details of the processor and see if there are nay flavors of the processor that are missing virtualization.  A case where it might be in the BIOS but not in the chipset.

    Also, check for BIOS updates.  Frequently a BIOS update will fix strange problems like this.

     


    Brian Ehlert (hopefully you have found this useful) http://ITProctology.blogspot.com
    Learn. Apply. Repeat.
    Disclaimer: Backup, test your backup, try new things. Attempting change is of your own free will.
    Donnerstag, 2. Februar 2012 17:40
    Moderator
  • I believe you need a hotfix for a bulldozer based CPU.

    http://support.microsoft.com/kb/2568088

     

    • Als Antwort vorgeschlagen FZB Freitag, 3. Februar 2012 19:52
    • Als Antwort markiert Jae An Samstag, 4. Februar 2012 17:31
    Donnerstag, 2. Februar 2012 18:11
  • Thanks for the note. 

    This one really looks like the one that I need, but when I followed the link to request for the hotfix, I get HTTP 404 Not Found error.  :(

     

    Freitag, 3. Februar 2012 19:28
  • The link at the top to request the hotfix works for me (I just tried it). 

    Are you already logged in with LiveID?

     


    Brian Ehlert (hopefully you have found this useful) http://ITProctology.blogspot.com
    Learn. Apply. Repeat.
    Disclaimer: Backup, test your backup, try new things. Attempting change is of your own free will.
    • Als Antwort markiert Jae An Samstag, 4. Februar 2012 17:31
    Freitag, 3. Februar 2012 19:41
    Moderator
  • http://support.microsoft.com/hotfix/KBHotfix.aspx?kbnum=2568088&kbln=en-us

    this is the link that should open when requesting the hotifx, does that one work for you or also gives you 404?

    • Als Antwort markiert Jae An Samstag, 4. Februar 2012 17:31
    Freitag, 3. Februar 2012 19:53
  • There was a link to download hot fix, and that's where I was getting the HTTP 404 error.

    However, this time I just followed the hot fix instruction (workaround case 2), and it fixed my problem!!!

    Thank you so much everyone!!!

     

    Samstag, 4. Februar 2012 17:31
  • The patch works but i'm confussed. What donkey thought it would be a good idea to release an updated CPU that doesn't work on Hyper V?

    I've just spent 30 minutes swaping out my Phenom x4 for a fx 6100 and within 5 minutes of use I need a patch.

    10/10 Microsoft for bringing out this patch.

    10/10 Google Search for bringing me to this page.

    0/10 AMD for not bothering to run Hyper V before you sold me your dud processor.

    Donnerstag, 3. Mai 2012 03:14