RC1 Hypervisor Failed to Start
I have a Dell Poweredge 2950 with Dual Quad Cores, X5355 CPUs. I upgraded Hyper-V to RC1 from RC0. I followed the instructions of shutting down all the virtual machines and deleting any snapshots or saved states. Now, upon server boot none of the VMs will start and there is a Hyper-V event ID 48 from the Hyper-V Hypervisor as the source. The message reads:
"Hyper-V launch failed; Processor ID 0x4 does not provide the features necessary to run Hyper-V (leaf 0x80000008, register 0x0: features needed 0x24, features supported 0x26)."
Hyper-V ran fine with RC0. Any clues? BIOS is up to date as well.
Thanks,
Jason
Ответы
Folks, I talked with John and for me at least, we have a temporary solution.
Apparently RC1 has issues with multiple physical processors. As you know I am running a dual quad core system.
Using MSCONFIG, I selected the Boot tab, clicked on Advanced Options.
From there I selected the Number of Processors check box and set the number of processors down to 4.
Sure enough, following a reboot, all my Hyper-V Guests stared just fine.
Yes I'm aware I have knocked out one of my processors, but as this is a lab system its not the end of the world until release hits.
- Помечено в качестве ответаMike Sterling [MSFT]MSFT, Владелец30 мая 2008 г. 22:43
- Hi,
"No Execute / Execute Disable (xD) bit" enabled did the trick,
Thank you for hælping
/Patrick
PatrickHoogenboom- Предложено в качестве ответаDavid Shen - MSFTMSFT, Модератор10 июня 2008 г. 2:42
- Помечено в качестве ответаDavid Shen - MSFTMSFT, Модератор17 июня 2008 г. 6:26
- So Hyper-V was released today (RTM)!
http://www.microsoft.com/downloads/details.aspx?FamilyId=F3AB3D4B-63C8-4424-A738-BADED34D24ED&displaylang=en
AND!!!!!!!
(drum roll)
It works now!!!!!
Thanks you Microsoft for including this fix in the final release!!
:)
Mike Crowley: MCT, MCSE, MCTS, MCITP: Enterprise Messaging Administrator- Помечено в качестве ответаDavid Shen - MSFTMSFT, Модератор27 июня 2008 г. 7:08
Все ответы
Update:
I have since reinstalled Server 2008 RTM Enterprise x64, added Hyper-V role and installed the RC1 update. Same result. Hypervisor will not start. I reinstalled again, added Hyper-V and installed RC0. All is well, but this is troubling. I plan on using Hyper-V for a hosting environment.
Any thoughts? Anyone?
Thanks,
Jason
I'm checking with the dev team on this, and will reply back when I get an answer.
Mike,
I have had a similar issue:
Last night I rebuilt my XW9400 and prior to installing updates (included RC1) Hyper-V worked in it's beta form. Upon installing RC1 I am getting an error that states:
Hyper-V launch failed; Processor 0x2 does not provide the features necessary to run Hyper-V (leaf 0x80000001, register 0x1: features needed 0x34d, features supported 0x351).
I have verified that the hardware does support Hyper-V, and that the approprirate features are turned on in the BIOS. Has anyone else had this issue? Any help would be much appreciated.
Thanks,
Michael
- Hello!
I'm having simmilar problem as the other two previous posts so maybe my experience will help out to solve problem. I use "home" pc for Hyper-V specifications (Intel Core 2 Quad Q9300, Abit IP35 Pro, 8 GB RAM & etc.). I have hardware that supports virtualization which worked with pre RC & RC0 release of Hyper-V but when I install RC1 release i recieve error that hypervisor is not running. Tried to start service via command line but notting helps. And yes, I use final verison of Windows Server 2008 x64.
Thanks,
Ivor - Hello,
I have possible solution to our problem!
Fresh install Windows Server 2008 RTM or Final verison. DO NOT install Hyper-V role or RC updates before RC1! Instead download all the updates & patches from Windows Update, all but Hyper-V RC1. When installation finishes and after few restarts download RC1 from Windows Update. After installation add Hyper-V RC1 role and everything should work just fine.The most important issue is that you DO NOT install any other Hyper-V RC updates but RC1. Worked for me!
Good luck,
Ivor Didn't work for me. I installed the final version and then ran Windows update, I did NOT install RC1. After rebooting and getting everything configured I went and downloaded RC1 as an MSI and installed it.
No go. This was my test lab and rebuilding it is going to be a big hassle.
I don't understand what changed as RC0 was working GREAT.
I have been going back and forth with John Howard on his Hyper-V Blog (http://blogs.technet.com/jhoward/archive/2008/05/20/hyper-v-rc1-is-available-for-download.aspx) and he stated that there is a known bug 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.
I sent him my particular error code to see if it was the same issue - I am sure it is becasue the error code tells me the same thing - I had this problem in RC0 as well. Hopefully this gets fixed before RTM.
Well Microsoft blew it on this one. I have quad processor dual cores. The processors are MATCHED, directly from HP.
I'm just going to rebuild the system (yet again) and use VMWare Converter on my Hyper-V images and use VMware Server 2.0 Beta.
I've long been a proponent of Hyper-V, but this one bit me hard as I was trying to show the executives here the worthwhileness of migrating from VMware ESX 3.5 to Hyper-V to save costs. Now I'm stuck.
- I just have to remind you that this isnt final verison so you cant blaim Microsoft for errors. Try again but use the following instructions that I mentioned in my previous post. Freshly install the final or RTM verison of Windows Server 2008. Then, go to Windows Update and download all important updates (Hyper-V RC1 will be marked recomended, which you dont install at this time). After applying all the updates and a "few" restarts go again to Windows Update and install the Hyper-V RC1 update. The most important thing is that you DONT install any Hyper-V roles and any previous verisons of Hyper-V since the RC1 update will not work!
Looking forward hearing from you,
Ivor If anyone is seeing a specific Hypervisor launch error which is NOT Hyper-V launch failed; Processor ID 0x4 does not provide the features necessary to run Hyper-V (leaf 0x80000008, register 0x0: features needed 0x24, features supported 0x26, get in touch with me through the email link at the top of my blog (blogs.technet.com/jhoward).
We are very interested in investigating the issue further and need some information on the machines themselves. Any assistance is greatly appreciated.
(Note that the 0x24 vs 0x26 is an issue we know about. There is no resolution in RC1, but we should have the fix available in the next release).
Thanks!
John.
Senior Program Manager
Hyper-V Team
--------------------------------------------------------------------------------
This posting is provided "AS IS" with no warranties, and confers no rights.ivor,
I have no problems "blaiming" Microsoft. I know this is a beta. I'm disappointed because what was working flawlessly (enough for me to bring it up to the executives here) it simply broke in RC1. I'm disappointed because it was my way of getting out of the yearly maintenance with EMC and I was to give my demo on Hyper-V today.
i've been beta testing Microsoft software for years, as far back as Windows 95, so I'm quite aware of how things work while in beta, this isn't a beta anymore. Its RC1, which means its feature complete and everything should work properly. I have no issues with it other than what I have posted here.
As I mentioned in another thread you posted in, I did this on my own this morning, and it still does not work with the same errors. I've even rebuilt the box again following your exact instructions, only to get the same failure.
Bill F.
- John, I've emailed you with my details as requested. Fell free to contact me if any further information is required.
Folks, I talked with John and for me at least, we have a temporary solution.
Apparently RC1 has issues with multiple physical processors. As you know I am running a dual quad core system.
Using MSCONFIG, I selected the Boot tab, clicked on Advanced Options.
From there I selected the Number of Processors check box and set the number of processors down to 4.
Sure enough, following a reboot, all my Hyper-V Guests stared just fine.
Yes I'm aware I have knocked out one of my processors, but as this is a lab system its not the end of the world until release hits.
- Помечено в качестве ответаMike Sterling [MSFT]MSFT, Владелец30 мая 2008 г. 22:43
- I have a Dell PE 2900 and I used to have hyper-v running fine. I was using a Intel 5130 which is a dual core cpu. I then added a 2nd physical cpu, and upon reboot all of my network adapters had new names and none of the VMs would load. It gave me an error about not being able to connect to the service. After playing with it a bit, including removing the recently added CPU, I found the above mentioned update and applied it and it actually allowed me to connect to the VM service once again, but the VM's were hosed. I rebuilt the VMs and was back in business (using the old vhd files).
I have since wiped the entire system and reloaded the OS and enabled hyper-v. I now get the error:
Hyper-V launch failed; Processor ID 0x4 does not provide the features necessary to run Hyper-V (leaf 0x80000008, register 0x0: features needed 0x24, features supported 0x26).
I wonder if this is what my problem was earlier - why it corrupted my virtual machines and broke the service.
After finding this post, I tried setting my boot.ini file to 4 processors and that didn't allow me to start the VMs. Do I need to set it to "2" because that limits it to the one physical socket? I'll try that and post back. If this is the only work-around, I hope the fix comes soon. The entire purpose of the 2nd CPU purchase was to help with this virtual enviroment.
-----EDIT-----
The update I mentioned was not the same as the one above. the update I installed and got all those problems was http://support.microsoft.com/kb/949219
Mike Crowley: MCT, MCSE, MCTS, MCITP: Enterprise Messaging Administrator- ИзмененоMike Crowley 5 июня 2008 г. 4:08code block didn't look right
- ИзмененоMike Crowley 5 июня 2008 г. 4:32updated kb mistake
- Ok - that worked. Setting the processor option to reflect the max cores in the first physical core ONLY. In my case this was "2".
I just hope the fix isn't as disruptive as my earlier mentioned experience. I don't want to have to keep rebuilding my VM's.
(And yes, I realize this is still RC, so I'm not "complaining", just complaining")
Mike Crowley: MCT, MCSE, MCTS, MCITP: Enterprise Messaging Administrator - Hi,
I installed windows 2008 on our new IBM X3650 7979-C3G with 2 Quad core X5355 CPU.
I activated the Hyper-V and installed RC1.
Even when i use the solution above, "setting the processor option to only 4 processors", the error "failed to initialize" still happens.
/Patrick
PatrickHoogenboom Thanks for getting back to me Mr. Sterling! I look forward to the future update that will resolve this issue.
Patrick - Can you post your error text so that we can be sure it is in fact the exact same problem? The issue is very specific about the reporting capabilities of a 2nd CPU, setting the OS to only use the first CPU logically fixes this. If you're having problems after properly reducing your 8 cores to 4, there may be another issue.
Mike Crowley: MCT, MCSE, MCTS, MCITP: Enterprise Messaging Administrator- Hi,
"No Execute / Execute Disable (xD) bit" enabled did the trick,
Thank you for hælping
/Patrick
PatrickHoogenboom- Предложено в качестве ответаDavid Shen - MSFTMSFT, Модератор10 июня 2008 г. 2:42
- Помечено в качестве ответаDavid Shen - MSFTMSFT, Модератор17 июня 2008 г. 6:26
I am having similar issues, with the exception of some numbers being mixed up a bit. Notice that the error message below has the same description, with the exception of the "features needed" and features supported" are reversed. I don't know if this is as common as others have seen, or if this sheds some light on a bigger problem.
"Hyper-V launch failed; Processor 0x4 does not provide the features necessary to run Hyper-V (leaf 0x80000008, register 0x0: features needed 0x26, features supported 0x24)."
I get the typical "failed to launch" messages as well as the messages about my BIOS not being enabled, but things were working great with RC0. I started with the Beta, upgraded to RC0 successfully, and have lately attempted to upgrade to RC1 and that's when the problems started. I have tried creating new VM's with RC1 and get the same errors. I reinstalled Server 2008 and applied the stand-alone RC0 update and my VM's were working again. I shut down the VM's and applied RC1 and the problem returned.
I see that somebody suggested reinstalling Server 2008 and going directly to RC1 and bypass RC0. I will attempt that this week.
My Server:
Dell Precision Workstation 690
(2) Quad core E5335 Xeon
32GB DDR2 667 RAM
(1) SAS drive for host
(2) 250GB SATA (RAID 0)Hopefully this gives you some insight into my issues with RC1. I also have an HP xw8600 Workstation with (2) E5440 Xeons at work and it handles RC1 without any troubles. I have updated the BIOS in my Dell to the latest rev recently and still no change.
Please let me know if your have any questions or comments, I would like to know if there is a workaround or fix. I am a huge fan of Hyper-V so far. I'm always willing to do my part to make it even better!!
Cheers
- ИзмененоRob Dev 17 июня 2008 г. 2:48Typo
- Have a look at this posting in John Howard's Blog. Seems to cover your setup.
http://blogs.technet.com/jhoward/archive/2008/06/16/hyper-v-rc1-hyper-v-launch-failed-processor-0x4-does-not-provide-the-features-necessary-to-run-hyper-v-leaf-0x80000008-register-0x0-features-needed-0x26-features-supported-0x24.aspx
Bill - So Hyper-V was released today (RTM)!
http://www.microsoft.com/downloads/details.aspx?FamilyId=F3AB3D4B-63C8-4424-A738-BADED34D24ED&displaylang=en
AND!!!!!!!
(drum roll)
It works now!!!!!
Thanks you Microsoft for including this fix in the final release!!
:)
Mike Crowley: MCT, MCSE, MCTS, MCITP: Enterprise Messaging Administrator- Помечено в качестве ответаDavid Shen - MSFTMSFT, Модератор27 июня 2008 г. 7:08
- Wow! And before their August deadline! Very impressive... Going to update my machine now. Hopefully I'll be able to use my second CPU now and utilize all 8 cores.
- Just bought an HP ML 370 with dual quad core and 32 Gig of RAM and having the same exact issue. Did all of the windows updates and downloaded the RTM of hyper-v before adding the role. Prior to adding the hyper-v role, I changed the BIOS to turn on processor support for vitualization. Not sure what else to do, hyper-v will not start.
- "No Execute / Execute Disable (xD) bit" enabled did the trick for me also under cpu options in the bios setup on my x3650
