If you’ve been following the VMware FUD fiasco, I just wanted to provide a quick update.
In the last post, we finally reached a point where VMware provided some basic information about their configuration and we immediately began working to reproduce the test. As I mentioned in the last blog, the Hyper-V team is fanatical about the stability of Hyper-V. If there’s an issue, we’re not going to hide. We will address the issue and provide a fix. Period. We are 100% customer focused and committed to world class support. We’ve still got some more work to do, but I told you that I’d provide an update in early June so I want to do just that.
On the testing front, I don’t want to deliver incomplete information, but I’ll give you this tidibt. We haven’t found any Hyper-V crashes and we have found problems with VMware’s tests.
The VMware Ask
Also in the last blog, we provided VMware the opportunity to resolve this matter and demonstrate partnership. Specifically,
To Bruce Herndon/VMware
In your blog you state that this issue “shows little sign of abating.” This statement implies that you’re interested in resolving this matter.
Finally, something we can agree on.
If you indeed want to resolve this matter, then:
- Take down the video.
- Send us a crashdump so we can take a look sooner rather than later. Send the crashdump to your Microsoft Technical Account Manager (TAM). If you need help, let us know and we’ll follow-up.
- Pledge this won’t happen again.
Unfortunately, VMware has done none of the above and remained silent. Since we’re going to spend a few more weeks testing, we’d like to again provide VMware the opportunity to take us up on this offer and demonstrate partnership.
Speaking of Partnership.
In the meantime, this seems like a great opportunity to mention a few of the things we’ve done to help our partners develop for both Windows and Hyper-V. I’ll cover that in my next blog.
Principal Group Program Manager
Windows Server, Hyper-V