Hyper-V RC1 Hypervisor Failed to Start

There is a known problem in Hyper-V RC1 in which after you upgrade a perfectly working RC0 server the Hypervisor will not start.

You will see the following error in the event log:

imageSource: Hyper-V Hypervisor

Event ID: 48

“Hyper-V launch failed; Processor 0×4 does not provide the features necessary to run Hyper-V (leaf 0×80000008, register 0×0: features needed 0×24, features supported 0×26).”

Hyper-V RC1 apparently has issues with my processors which are Intel Quad Core Xeon 2.33Ghz E5345.  This server did have an additional processor added after it was purchased.  Both processors are E5345, but Dell OpenManage Server Administrator is reporting one processor as Model 15 Stepping 7 and the other one as Model 15 Stepping 11.

John Howard, Microsoft Senior Program Manager on the Hyper-V Team reported on his blog the following:

“Yes, we are aware of a bug in RC1 which affects the Hypervisor from launching correctly on a small number machines. The class of machine is where there is more than one physical socket containing processors, and the processors are reporting mismatching capabilities. However, that fix will not be available until a future release.”

There is a temporary solution that will allow Hypervisor to start after a reboot.   

  1. Open MSCONFIG
  2. Select the Boot tab and click Advanced Options.
  3. Select the Number of Processors check box and set the number of processors to 4.
  4. Click OK twice.
  5. Click Restart.

The bad news is that I’m losing the benefit of one of my processors, but at least Hyper-V is functional.  I’ll have to remember to set the processors back after Hyper-V RTM has come out.

Share:
  • Digg
  • Facebook
  • Google Bookmarks
  • Twitter
  • LinkedIn
  • Live
  • MySpace
Posted on May 30, 2008 at 2:12 pm by Drew · Permalink
In: Uncategorized · Tagged with: , , ,

3 Responses

Subscribe to comments via RSS

  1. Written by Jeremym87
    on June 5, 2008 at 7:30 am
    Permalink

    Server core does not have msconfig, how can i try your fix on a Core box?

  2. Written by Drew
    on June 5, 2008 at 1:36 pm
    Permalink

    Good question, I don’t know. Trying to manage a server core box I felt like I had a straight jacket on.. I gave up on Core for now.

  3. Written by eric
    on July 1, 2008 at 10:48 am
    Permalink

    Edit your boot.ini file. Google for “processors boot.ini”. Msconfig just edits this file for you.

Subscribe to comments via RSS

Leave a Reply