Posted by Carl Eschenbach
Executive Vice President of Worldwide Field Operations
The August 19 announcements from Microsoft are good news for VMware customers. VMware is now part of the Microsoft Server Virtualization Validation Program Program (SVVP), and is happy to work with Microsoft to deliver better support to our many mutual customers. Under SVVP, customers running Windows and Microsoft applications on the VMware ESX hypervisor will receive the support they need from Microsoft, in addition to the support they have enjoyed from VMware. VMware customers can continue to leverage the full flexibility and benefits of using Virtual Infrastructure. VMware is working with Microsoft to certify ESX in the near future.
VMware Infrastructure provides customers with high levels of continuous service for applications, enabling customers to achieve significantly higher hardware utilization, dynamically balance workloads across physical resources, and move applications in real time. VMware collaborates with Microsoft and other ISVs to ensure that our customers have access to product support consistent with the vendor’s policies for traditional physical environments.
Last night, we became aware of a code issue with the recently released update to ESX 3.5 and ESXi 3.5 (Update 2).
When the time clock in a server running ESX 3.5 or ESXi 3.5 Update 2 hits 12:00AM on August 12th, 2008, the released code causes the product license to expire. The problem has also occurred with a recent patch to ESX 3.5 or ESXi 3.5 Update 2. When an ESX or ESXi 3.5 server thinks its license has expired, the following can happen:
- Virtual machines that are powered off cannot be turned on;
- Virtual machines that have been suspended fail to leave suspend mode; and,
- Virtual machines cannot be migrated using VMotion.
The issue was caused by a piece of code that was mistakenly left enabled for the final release of Update 2. This piece of code was left over from the pre-release versions of Update 2 and was designed to ensure that customers are running on the supported generally available version of Update 2.
In remedying the situation, we’ve already released an express patch for those customers that have installed/upgraded to ESX or ESXi 3.5 Update 2. Within the next 24 hours, we also expect to issue a full replacement for Update 2, which should be used by customers who want to perform fresh installs of ESX or ESXi.
I am sure you’re wondering how this could happen. We failed in two areas:
- Not disabling the code in the final release of Update 2; and
- Not catching it in our quality assurance process.
We are doing everything in our power to make sure this doesn’t happen again. VMware prides itself on the quality and reliability of our products, and this incident has prompted a thorough self-examination of how we create and deliver products to our customers. We have kicked off a comprehensive, in-depth review of our QA and release processes, and will quickly make the needed changes.
I want to apologize for the disruption and difficulty this issue may have caused to our customers and our partners. Your confidence in VMware is extremely important to us, and we are committed to restoring that confidence fully and quickly.
President and CEO