Eric Siebert should be commended for the blog he wrote today, calling on the major virtualization vendors to “stop bickering with each other … and work towards the betterment of virtualization.”
Siebert, a virtualization expert and SearchServerVirtualization.com contributor, said the virtualization market should be more like sports: full of fierce competition, but also mutual respect and professionalism between competitors. He even illustrated his point with a photo of a UCLA player helping a crying Adam Morrison to his feet after Gonzaga’s 2006 NCAA Tournament loss.
Unfortunately, for every touching moment like that, there’s one like this:
Tensions run high in sports because of all the money on the line, and the same is true in the virtualization market. It would be great if Microsoft and VMware could be more civil towards each other, but let’s look at the track record there:
- April 2008: VMware accuses of Microsoft of knowingly distributing an inaccurate Yankee Group report that didn’t exactly paint VMware in the best light.
- September 2008: Microsoft launches a guerrilla marketing campaign at VMworld 2008, handing out poker chips that advertise a now-defunct website called VMwareCostsWayTooMuch.com.
- April 2009: Microsoft posts its smugness-tinged “Top 10 VMware Myths” video. Even some Microsoft loyalists decry the video as “embarrassing,” and VMware proponents fire back in force.
- June 2009: VMware’s Scott Drummonds is forced to apologize for anonymously posting a misleading video that showed Hyper-V crashing while running VMware’s VMmark platform and implied that Hyper-V caused massive TechNet and MSDN outages. Microsoft’s Jeff Woolsey wrote of VMware at the time: “This isn’t how billion dollar companies behave.”
- August 2009: Even though a year had passed since a VMware ESX bug caused serious VMotion and VM booting problems, Microsoft’s Woolsey still wrote a three-part blog slamming VMware for the problem.
The history speaks for itself. VMware won’t be helping a crying Microsoft up to its feet anytime soon.
Imagine seeing a car commercial where the announcer said, “Sure, the car doesn’t have air conditioning, a radio or a trunk, but at least it doesn’t spontaneously explode!”
You may remember the VMware ESX 3.5 Update 2 bug, which wreaked havoc on users. They couldn’t reboot virtual machines or run VMotion. And Update 3, meant to fix the problem, caused some VMs to uncontrollably reboot. In a new blog post, Hyper-V program manager Jeff Woolsey criticizes VMware for this incident, which happened more than a year ago:
It’s now less than three weeks away, and I am really getting excited for VMworld 1979.
Oh, I’m sorry. I mean VMworld 2009. You’ll have to excuse my confusion. It’s just that, ever since VMware announced the band playing the VMworld Party, I’ve had a little trouble figuring out what year it is.
If you haven’t heard by now, here’s the band:
That’s right. It’s Foreigner.
After all, there’s no better way to unwind after three days of virtualization than to hold your lighter up in the air and sing along to “I Want to Know What Love Is.” Don’t believe me? See for yourself:
VMware is going to be a cloud company. A real cloud company.
That was the message at Thursday’s New England VMware User Group summer meeting in Brunswick, Maine. Mike DiPetrillo, VMware’s global cloud architect, described the one thing that will set VMware apart from Amazon, Google, Microsoft and other cloud providers: interoperability.
“These guys are completely proprietary,” DiPetrillo said, referring to Amazon Web Services, Google and Microsoft Azure.
EMC has owned VMware since 2004, but for the most part, the two companies have continued to operate separately. Very separately.
That may be changing.
Microsoft released Hyper-V R2 to manufacturing today, along with Windows Server 2008 R2 and Windows 7.
The release to manufacturing (RTM) means the final code is available for partners to test and install on their hardware. Microsoft will make the software available for evaluation in the first half of August and offer it to customers with Software Assurance in the second half of August, technical product manager Oliver Rist said on the Windows Server Division WebLog.
Microsoft said at last week’s Worldwide Partner Conference that Hyper-V R2 will be generally available in September, and the company is planning a launch event in November.
To be clear, there are two versions of Hyper-V R2: Windows Server 2008 R2 Hyper-V, which comes with Windows Server 2008 R2, and Hyper-V Server 2008 R2, a free, standalone hypervisor. The free version will still include many of R2’s most sought-after features, including Live Migration.
For more on the new features in Hyper-V R2, check out this podcast with expert Greg Shields, which, completely coincidentally, we just launched today.
You probably read the above headline and had a question of your own. Something along the lines of, “Colin, what have you been smoking?”
I know, it seems ridonklulous to think that Microsoft would give up on its Windows operating system — a product that dominates its market like few others in IT or any other industry. But in light of Microsoft’s recent Linux outreach, it’s a legitimate question.
You may remember that back in February, the Burton Group released a hypervisor comparison report. And in that report, the only hypervisor to meet 100% of the firm’s required criteria for enterprise readiness was VMware Virtual Infrastructure 3.5.
(If you don’t remember, you can check out a full recap in our recent list of the top 10 server virtualization news stories of the year so far.)
Anyway, since February — but before we published that list — something changed. Another hypervisor has since met 100% of the Burton Group’s criteria. And that hypervisor is Citrix XenServer 5.5.
VMware is reaching out to Virtual Iron users, following Oracle’s decision to kill off the Virtual Iron product line last week. (Oracle acquired Virtual Iron in May.) As my colleague Alex Barrett reports today, VMware is offering Virtual Iron customers 40% off the list price of vSphere and vCenter.
The offer is an apparent attempt to keep Virtual Iron’s customers from moving to Oracle VM (which is what Oracle wants them to do). But that raises the question: Why does VMware care?
We still don’t know what Oracle’s plans are for the Virtual Iron technology it acquired in May, but in light of these developments, a much bigger question is arising about a much bigger acquisition: Will Oracle kill off Sun Microsystems’ virtualization line too?