A Quick Note to VMware

To Whom It May Concern at VMware:

If I had to choose only one thing that I wanted VMware to be sure to do in the next few months, here is what it is: join the Microsoft Server Virtualization Validation Program and get VMware Infrastructure validated. No, I don’t want you to finish VI4. No, I don’t want you to concentrate on Continuous Availability. I want you to join SVVP.

Why? I can answer that question with only one word: support.

As fully expected now that Microsoft has a more robust virtualization solution, there has been a sudden about-face on the use of server virtualization in conjunction with their products. Consider this announcement regarding support for Exchange Server 2007 SP1 (quoting from this blog entry):

Microsoft now supports Exchange Server 2007 SP1 running Hyper-V or hypervisors validated under the Microsoft Server Virtualization Validation Program (SVVP).

I can hear you at VMware now: “We don’t need to validate our technology by signing up for some program run by Microsoft! Our hypervisor is the best! We have the best feature set! 100% of the Fortune 100 use our products—what do we need SVVP for?”

Relax, I understand where you’re coming from. But, honestly, let’s get real about this. VMware, do you want to remove the #1 obstacle to customers adopting your technology? That #1 obstacle is support, and whether you like it or not the introduction of the SVVP by Microsoft gives you a vehicle whereby you can remove that obstacle. A refusal to participate in the SVVP—even if you disagree with the program in principle—merely locks VMware out of many opportunities where Microsoft will be able to walk right in. That’s right! Your superior technology is going to lose out to technology that is just “good enough” simply because of support. Is that what you want?

So go sign up for SVVP now. If you don’t, you’re giving the competition a great big weapon to use against you. The power to remove that weapon is yours.

UPDATE: Looks like I waited a bit too long to chide VMware on their lack of inclusion in SVVP. In any case, I’m glad to see the news. Good job, VMware! (My thanks to Dave, who pointed this out to me.)

Tags: , , ,

  1. Justin Campbell’s avatar

    Your assuming that Microsoft will *let* VMware join the program

  2. slowe’s avatar

    Well, it’s kind of a moot point now, isn’t it? The official announcement that VMware has entered the SVVP is expected later today.

  3. Gabrie van Zanten’s avatar

    Hi
    When I was at VMworld 2008 Europe in Cannes this year, VMware already announced that they were talking to Microsoft about joining the program. In another session Microsoft it self said they would welcome VMware to the program.

    So I wasn’t afraid they wouldn’t join, just waiting WHEN they would join :-)

    Would be good news today if they have joined and have been validated.

    Gabrie

  4. slowe’s avatar

    Gabrie,

    Thanks for the info. When I was at Tech-Ed in June of this year, Microsoft made NO mention whatsoever–even in passing–of the fact that VMware had been working with them to join the SVVP. I guess they didn’t want to steal the thunder from their own virtualization solution…

  5. kevinj’s avatar

    http://blogs.technet.com/virtualization/archive/2008/08/19/Thoughts-on-today_2700_s-virtualization-licensing-and-support-news.aspx

    “For example, it was reported that VMware signed an agreement to participate in the Server Virtualization Validation Program. That much is true. However, it doesn’t mean that cooperative support is now in place. First, ESX Server must go through and pass the validation test. Once validated, they’ll be added to KB article 944987, where we list “support partners for non-Microsoft hardware virtualization software.” Today only Novell is listed, and that’s due to the broader technical collaboration agreement in place between the companies.”

  6. Rich’s avatar

    Just speculating, but maybe VMware’s participation in Microsoft’s SWP program and general cooperation between the 2 companies will help Microsoft’s licensing policies finally anchor to the virtual hardware instead of the physical. The loosened application mobility policy announced yesterday does not include the Windows Server OS!

    http://vmetc.com/2008/08/19/new-microsoft-application-mobility-brief-does-not-cover-the-windows-operating-system/

  7. Jason Willey’s avatar

    One thing I found interesting about the annoucement was the slight change in the clause about reproducing problems in the kb associated with the SVVP announcement. They have now changed the old standby of “you may be required to reproduce the problem on physical hardware” to state “hardware or within Hyper-V.

    I think that will lead to beachheads of Hyper-V within pure VMware or XenServer shops. Pretty smart and subtle by Microsoft.

  8. slowe’s avatar

    Jason,

    I agree completely. I fully expect Hyper-V pockets to spring up within data centers that are primarily virtualized with other solutions, if for no other reason than due to the fact that Hyper-V ships with the operating system. Combine that fact with issues around licensing (Windows Server OS licenses are NOT included in the recent licensing change regarding the 90-day license transfer) and support and I fully expect Hyper-V to show up all over the place.