By now you might have seen that VMware ESX 3.5 update 2 has passed the Microsoft Server Virtualization Validation Program. They announced it here.
today announced it has qualified its industry-leading VMware ESX hypervisor under the Microsoft Server Virtualization Validation Program (SVVP). VMware ESX 3.5 update 2 (ESX 3.5u2) is the first hypervisor to be listed under the program, providing VMware customers who run Windows Server and Microsoft applications with access to cooperative support from Microsoft and VMware.
Of course we all read that VMware only agreed to participate in SVVP a couple weeks ago, around the time we announced expanded technical support for 31 server applications running on validated hypervisors. Congrats to them for achieving a validated configuration so quickly. ESX 3.5 update 2 now joins Windows Server 2008 Hyper-V as being validated to run Windows Server and associated Microsoft server applications. And now that ESX 3.5 has passed SVVP, VMware customers will join Novell customers as receiving cooperative technical support (if there’s a support policy in place, and the customer is running the validated configuration) for Microsoft software running in/on their virtualization software.
I’d expect to see other hypervisors pass the SVVP soon. There are 7 vendors now committed to participate in SVVP, the newest addition being Unisys.
And given today’s news, it’s a good time to review the details on Microsoft’s support policy for Microsoft software running in non-Microsoft virtualization software, read KB article 897615. Here’s an excerpt:
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. This support will include coordinating with the vendor to jointly investigate support issues. As part of the investigation, Microsoft may still require the issue to be reproduced independently from the non-Microsoft hardware virtualization software. Where issues are confirmed to be unrelated to the non-Microsoft hardware virtualization software, Microsoft will support its software in a manner that is consistent with support provided when that software is not running together with non-Microsoft hardware virtualization software.
Patrick
UPDATE on Sept. 9 – I incorrectly noted that vendors who pass SVVP will be noted in a KB article. Wrong. I’m told the vendors will be listed in the Windows Server catalog. You’ll see three vendors’ products listed there now. And if you’re attending VMworld 2008 next week, there’s a new session being added so that you can learn more about SVVP from Microsoft and VMware. See session EA4460
PingBack from http://blog.scottlowe.org/2008/09/03/vmware-esx-35-u2-validated-via-svvp/
http://www.virtualizationfeed.com/rss.aspx how did I manage without this RSS summary before?   
You may have seen that there is a big Microsoft Virtualization event happening in the US on Monday. 
body { font-family: Arial; font-size: 10pt} 183 Microsoft Team blogs searched, 82 blogs have new articles
Hi Patrick,
In your previous post on this subject (see http://blogs.technet.com/virtualization/archive/2008/08/19/Thoughts-on-today_2700_s-virtualization-licensing-and-support-news.aspx) you indicated that KB 944987 would be updated if the hypervisor became validated. Does this imply that it’s still not "official"?
Bert
The Validated Hypervisor – Windows Virtualization Team Blog – Site Home – TechNet Blogs