Most people heard about this by now, Technet and MSDN are running on Hyper-V. As Microsoft states, an enterprise ready solution. Both Technet and MSDN crashed this week, or should we say Hyper-V just doesn’t cut it. Check this Youtube movie that clearly shows what happens when VMs are stressed:
A professional associate of mine shared screen captures of a variety of Hyper-V failures. My associate was evaluating the performance of a server running Hyper-V. The test was a workload derived from VMmark. When he repeatedly saw VMs blue-screening in Hyper-V during the test, he started capturing video of the events. Apparently the publicly available version of Hyper-V is unable to run VMs reliably. Is this why TechNet and MSDN went down on 4/30/09?
vSphere 4.0 Quick Start Guide
Assuming that is it because of Hyper-V that MSDN and technet crashed on the release of Windows 7 RC is I think going a bit too far. Who knows, It could be an issue with IIS or SQL server.
But, I would defenitvily aggree with the video that Hyper-V should be able too handle any workload without crashing if they call it “entreprise ready”.
I was hoping you were above FUD. This is pathetic.
This is reality…
The YouTube video was certainly interesting. I’ve been using Hyper-V in several production environments since it RTMd (internally even during RC), and never encountered any crashes like these (VSS-based backups are another story, though).
The problem is that the video lacks any sort of details. I’ve seen ESXi crashing several times on one of our test machines, which turned out to be faulty RAM (non-ECC).
Also, this is the first time i’ve read about Hyper-V being unstable, many other benchmarks i’ve read so far never stated anything like that.
If these VMmark problems can be replicated on another machine, then Microsoft seems to have their work cut out for them – if it can’t be reproduced on another machine, it’s just a hardware problem.
Regarding TechNet/MSDN: I’ve seen a lot of downtime there even before it was virtualized, especially during big releases. And the Windows 7 RC release was bigger than most other TechNet/MSDN launches i’ve seen so far. Most likely just a shoddy application/backend.
If it’s reality there’s no reason whatsoever he had to skip posting ANY pertinent information for other people to duplicate his issue. The fact is it ISN’T reality.
Hyper-V doesn’t just randomly crash on “consolidated workloads”. Anyone who has spent more than 5 minutes with the product can tell you that. I can make VM’s crash left and right on ESX if I set it up the right (wrong) way as well. Does that mean I should post up a video proclaiming ESX is only fit for crashing VM’s on a consolidated workload?
If you want to pick on MS, there’s plenty of legitimate reasons to do so.
They might release the info, I don’t know about that… again I’m just reposting this stuff. I didn’t make it up.
Clearly FUD. If it wasn’t, you would’ve mentioned the fact that this occurred during the tremendous demand generated by the release of Windows 7 RC on Technet and MSDN.
I guess any question of impartiality, along with your credibility, has just flown out of one of those crashing windows….
Here’s Microsoft’s statement to this issue:
http://blogs.technet.com/virtualization/archive/2009/05/09/hyper-v-winning-daily-vmware-fud-reaching-new-heights.aspx
Scott Drummond is a VMware guy – interesting.
And the issue seems to have to do with Intel or AMD errata – a BIOS update should provide newer CPU microcode.
Wow, really? I’m really impressed by mr Sherlock Holmes who discovered who posted the video. (The username and the following article might have revealed it I think: http://communities.vmware.com/blogs/drummonds/2009/05/06/video-on-hyperv-crashes )
@#10: Eh… So now that we seen through your obvious bias you resort to name calling?
I hadn’t heard of this site before but there’s absolutely no reason for me to return now, knowing that you’re anything but objective.
Name calling?
At least you’ve got a sense of humor… On the objectivity topic, there’s a new article coming up.
the fact that you even call attention to this video, and keep this blog post up without a retraction, is disturbing, and really diminishes your credibility.
Why would I retract it when I also added the details in the posts below:
http://www.yellow-bricks.com/2009/05/11/will-you-fight-or-will-you-run/
http://www.yellow-bricks.com/2009/05/15/fyi-setting-the-record-straight-on-the-hyper-v-video/