SVVP - how does it work?

There's been some good discussion around this today, and it was good, tomorrow am some official language will come out that will be along the clarifying lines in the body of this post.   Remember, just because I post it doesn't make it official, it's not official until it comes from VMware.   But, this should elucidate things a bit.  

Ok - open standing proposal...   First some history...   EMC has a long experience in working specific customer configurations through the Windows Server Catalog.   Getting MSCS configs certified historically (it's recently gotten a lot better, thank goodness) was BLACK AND WHITE.  Only that EXACT configuration was supported.   For many people this was a deal-breaker.    Over time we got really good This turned out to be a good thing for MSCS as a whole, when you're building these mission critical config, support testing    We became a machine at doing this.   Want a fun proof point?

Step 1 - go here: http://www.windowsservercatalog.com/

Step 2 - click on "cluster solutions" - note there are: 6,792 items found

Step 3 - type "EMC" in the storage field and search: 3,380 items found

You can see that we've done this A LOT - just about half the MSCS configs are on EMC.

OK - here's the open offer - if you are a customer, and the only thing stopping you from adopting a joint VMware/EMC solution for your Microsoft apps is a specific gap on the SVVP that matches you, post your needed config as a response to this thread, I'll work with VMware to get it up there. 

I'm that sure that virtualizing wth VMware is the right thing for customers - I'll get YOUR config tested.   We do have experience on getting this sort of thing done fast.

Ok - for some Q n A - read on.

VMware Products Certified Under Microsoft SVVP – FAQ and Update

Microsoft now supports their server products on VMware.  This eliminates a significant barrier to adoption for many prospective customers, and makes all our customers more confident about deploying on VMware.

You can see the list of certified hypervisors here.  Products supported by Microsoft are here.  The official support policy from Microsoft is here.

Since this policy change was announced, several questions have come up from VMware’s partners and customers:

Q:  What about Active Directory?  Its not on the list.

A: Active Directory is a Server Role provided in Windows Server since Server 2000.  This is similar to file services, print services, or other roles that are included in the operating system.  All of these roles are supported under SVVP.  Active Directory is fully supported under SVVP.

Q: Why isn’t VMware certified with 64-bit versions of Windows?

A: Each SVVP run is a multi-day process.  The tools provided by the qualification kit have not always worked as expected.  We have worked through the learning curve, and are now doing SVVP runs continuously.  We chose to certify the 32-bit version of the OS first in order to cover the large installed base of virtual machines that haven’t yet upgraded.  64-bit versions are in the queue and will begin to appear in the next few weeks.  VMware ESX and ESXi products will both be supported.

Q: Why isn’t ESXi certified?

A: As a new product, ESXi will be certified after ESX certification is complete.  Our priorities have been placed on the larger number of users running ESX today.

Q: What do the memory limits mean in the certification?

A: Certification is completed for a specific “maximum” virtual machine.  The numbers shown are the biggest configuration that VMware has submitted for certification.  These configurations will expand in the fourth quarter.

Q: Why aren’t we certified with bigger memory limits in the virtual machine?

A: Our initial test runs were conservative to ensure that we fully understood the behavior of the qualification kit.  We’re upgrading the servers soon to provide support for larger VMs.  We plan to deliver certification for all our products at the maximum supportable memory limit with ESX 3.5 update 3.  We will be re-certifying update 2 variants to increase the memory limit well beyond 4 GB early in the fourth quarter.

Q: How long will it take for new product releases to be fully certified?

A: Our plan is to ensure that all SVVP certifications are complete within 60 days of product GA.  We hope to significantly out-perform on this commitment if possible.

Q: What does SVVP mean for hardware certification and the VMware HCL?

A: SVVP isn’t related to VMware’s HCL.  Microsoft’s SVVP program demonstrates that a hypervisor runs Windows just like physical hardware, and is a requirement for Microsoft to offer support for Windows and other server products like they do on logoed hardware.  VMware’s HCL remains the standard for determining what hardware is supported with VMware products.

Q: I’ve still got questions about Microsoft support with VMware.

A: Ask your VMware representative or channel partner.  VMware is happy to help you to understand the details and implications of this program, and how it helps you to deploy Microsoft products on VMware.

Comments

[Kenon Owens]

Looks like you got the email and put it up there before I did.

http://dantedog29.blogspot.com/2008/09/what-deal-with-svvp.html

Great blogs, interesting reading.

[Confused MS Customer]

Interested in your view pertaining to SVVP...

1. Will MS require customers to reproduce on a physical platform during troubleshooting approved apps ruuning on virtualized systems.
--> aka: Does MS indicate they will not force customers to reproduce on physical servers if running HyperV but will if running on ESX?

2. SQL2008 is called out in the new SVVP (SQL2005 is not).

What are the explicit differences in the customer experience for the following scnearios.

a. sql2008 on HyperV versus VMware ESX
b. sql2005 on HyperV versus VMware ESX

[Chad Sakac]

Thanks for the question, confused MS customer - I think you're not alone :-)

WARNING: I've learned NEVER to make statements about Microsoft support, those definitive statements can only come from Microsoft. This is couched in my understanding, and in my experience of what happens.

NOTE: this has nothing to do with what works (they all work!) but what is explicitly in or out in the current support stance.

OK - so my answer:

1) If the configuration is not one explicitly supported in the SVVP, KB article 897615 applies (here: http://support.microsoft.com/kb/897615). This is the governing paragraph:

"For Microsoft customers with Premier-level support running non-Microsoft hardware virtualization software from vendors with which Microsoft does not have an established support relationship that covers virtualization solutions, Microsoft will investigate potential issues with Microsoft software running together with non-Microsoft hardware virtualization software.

As part of the investigation, Microsoft may require the issue to be reproduced by the customer independently from the non-Microsoft hardware virtualization software. This may be done on Windows Server 2008 (with Hyper-V), the actual hardware platform with the Windows operating system installed directly upon it, or on both."

Decoded, this means "if you're a Premier support customer, we'll do our best, but may ask you to repro in a physical.".

NOTE - you said "required", and the answer is NO they won't require that, but they reserve the right to ask you to do it when "reasonable" efforts are fruitless.

2) SQL Server 2008 is in SVVP, SQL server 2005 is governed like case 1) above.

So, the governing part of KB 897615 (same one) becomes this paragraph: "Additionally, for vendors with whom Microsoft has established a support relationship that covers virtualization solutions, or for vendors who have Server Virtualization Validation Program (SVVP) validated solutions, Microsoft will support server operating systems subject to the Microsoft Support Lifecycle policy for its customers who have support agreements when the operating system runs virtualized on non-Microsoft hardware virtualization software"

Decoded: you'll be supported, period. Now, note that Microsoft does state that they may need joint support/escalation with the virtualization vendor, and STILL reserve the right (less reserved?) to eventually ask to ask to repro on a physical.

OK - WANT MY 2 CENTS?

- Microsoft is a trusted vendor, in the same way VMware, Cisco and EMC (and many others) are for many customers.
- Trusted vendors know that saying "nah, not supported, you're screwed" is not a smart move, and results in... well... not so happy customers.
- They aren't trying to be devious, but are trying to draw the line somewhere about where they are point, and where the virtualization vendor is point (a blurry line, to be sure).

The most important thing is what happens at the first inbound call into support. These days, SVVP means that with ESX 3.5u2, you are not going to get the "I can't talk to you until you run it on a physical". After that, it's up to Microsoft (up to the point where they are stumped, at which point they engage through joint escalation VMware) to support you, together, which they will.

[Kenon Owens]

One other thing, Microsoft updated their KB Article on what Apps are supported by SVVP here: http://support.microsoft.com/kb/957006/ (which was updated VERY recently), SQL Server 2005 is now on the list. Also, we (VMware) have updated our current Certifications with more OSs and Platforms supported. Check out http://www.windowsservercatalog.com/item.aspx?idItem=fb304f90-92ed-4bed-ae4f-96805c16b61c&bCatID=1521 for the latest versions and platforms updated as we will be continously updating our current Certifications with larger product support and server capacity.

[PC tech support]

I never heard of this activity yet but it seemed pretty much interesting. I can see the productive reason behind it and I was actually impressed. I would love to hear more form you guys and updates regarding this.