Information and announcements from Program Managers, Product Managers, Developers and Testers in the Microsoft Virtualization team.
I prefer to spend my time talking about the great things we're doing with Hyper-V and Microsoft virtualization. We have a lot of very happy customers today with Hyper-V R1 and the upcoming R2 release delivers even more in terms of scalability, performance and new features like Live Migration and much, much more. Unfortunately, I need to take a moment to respond to some VMware FUD circulating the web.
Out on the web, there's an "anonymous" video purporting to show a Hyper-V crash. When I heard, I was surprised and immediately wanted to know more. I haven't heard of any such incidents with Hyper-V and the Hyper-V R1 release has been incredibly stable and reliable. So, what did I find?
The Video: No Facts Just FUD.
Not much. Where are the details? There are no facts provided. What Hyper-V build was this? The beta? What was the configuration being tested? Who posted this? Why didn't they contact Microsoft support? I mean there's literally no data other than a defamatory statement at the beginning of the video implying that Hyper-V had something to do with some downtime at TechNet/MSDN. The SQL team and Operations responded to this days ago. In short, Hyper-V had nothing to do with the outage.
So, why would someone create such a video? Let's dig a little deeper.
The poster, who doesn't appear on the video, doesn't state what company he works for or provide any context. Gee, I wonder where he works?
<drum roll please>
Introducing Scott Drummonds, VMware Product Marketing.
Gosh, I wonder why Scott didn't mention he works for VMware?
Very professional Scott.
No signs of desperation there at all.
Looks like I'll need to provide the facts here.
What I Do Know.
So, in terms of reliability, stability and support, not bad. (It's not like we released any patches resulting in days of downtime. HERE, HERE, HERE, HERE, HERE, & HERE)
Hmm. Still Want To Know More.
All said, I still wasn't satisfied. On the Hyper-V team, we run thousands of stress tests per week and the stress tests we run are far more invasive than the test in this video. So, I consulted our Hyper-V Supportability Program Manager and dug deeper. I wanted to know if we've had any Hyper-V crashes reported. Here's what I found out.
Of the 750,000 downloads, we've had 3 reports of crashes under stress and with the same error code as seen in the video bugcheck (0x00020001). The solution in all three cases was to upgrade the server BIOS which solved the problem. This can happen as hypervisors interact very closely with the hardware and BIOS updates generally include updated microcode for processors oftentimes to address errata.
In case you're wondering, VMware has had similar crashes with older BIOSes as well. Here.
Those are the facts. Now back to our regularly scheduled Hyper-V goodness.
TechEd Next Week!
Next week is TechEd in Los Angeles and a number of us from the virtualization team will be there in Los Angeles. We've got numerous sessions covering Hyper-V R2, Virtual Machine Manager and more. Hope to see you there!
Principal Group Program Manager
Windows Server, Hyper-V
P.S. It appears Keith Ward has seen through this veneer of FUD and blogged as well. HERE.
I’ve been watching an interesting “discussion” take place over the past few weeks via blogs, and honestly