This apple makes terrible orange juice!
There's nothing more likely to get a VMwarite riled up than comparing Microsoft Virtual Server (MSVS) and VMware ESX Server. Although they both virtualize an x86 system, MSVS runs on top of Windows, and ESX Server doesn't. VMware does have a server product that runs on top of a host operating system like MSVS, and it's the free VMware Server. MSVS should by all rights be compared to VMware Server, not ESX Server. ESX Server is much more powerful, but comes at a higher price, a bit more complexity for enterprise-scale deployments, and a smaller universe of supported hardware.
So let's look at this article by the usually excellent Alex Barrett at the usually excellent SearchServerVirtualization. It starts with a fair premise -- for some small shops, it's a path of least resistance to just use MSVS and call it a day. And when you read closely, Alex mentions VMware Server, but when the people he interviews start talking about price and VMotion in an article on MSVS, my alarm bells go off.
Microsoft Virtual Server flawed, not broken, users say.
That's fairly typical of most small shops, said Chris Wolf, senior analyst with the Burton Group and author of Virtualization: From the Desktop to the Enterprise. "If [you] have just a few test systems, you're not going to see much of a difference in performance," he said, between MSVS and VMware. But systems that start to max out their physical RAM might not get the performance from MSVS that they would with VMware, whose memory management feature moves underutilized memory to the hard disk, freeing up RAM for other busy virtual machines.
I think he's talking about ESX Server's balloon memory driver, which along with shared memory pages does help use memory more effectively between multiple virtual machines ... for ESX Server, not VMware Server. Also note how he compares "MSVS" (a product) and "VMware" (a company name, but he means ESX Server).
But the performance kick he gets from VMware does come at a price: having to learn an unfamiliar new operating system. "I wish I were more of a Linux person," Laudenslager said about having to administer his Linux-based VMware Server. Especially when it comes to setting up security policies, "I feel I could do a better job with Windows."
Laudenslager should be running VMware Server on Windows, not Linux, if he's a Windows person. VMware Server comes in both flavors.
Then, there are a few things that MSVS flat out does better than VMware. Hardware compatibility, for one thing, said Anil Desai, an independent consultant in Austin, Texas. VMware has done a good job expanding an extensive hardware compatibility list, but it can't compare with the 20,000 to 30,000 devices supported by MSVS's underlying Windows Server 2003 platform, Desai said.
Again, if you run VMware Server on Windows, you get to take advantage of all the device compatibility of Windows 2003, the same as MSVS does. It's when you move up to the power of ESX Server that you start having to be more careful about hardware compatibility.
If you buy contemporary hardware from tier-one OEMs, hardware compatibility shouldn't be much of an issue for most VMware shops, said Andrew Kutz, an operating systems specialist for the University of Texas, which runs VMware. But, "if you're a white box shop that builds all your own stuff, you're going to run in to some problems," he said.
And now I sound like a broken record -- use VMware Server on Linux or Windows on your white box all day long. Go to the VMware Forums if you're hardware savvy and you can probably even get ESX Server up on unsupported hardware for your lab, although we don't recommend it for production. But great googly moogly, don't go saying VMware doesn't have a free product to run on that cheapo white box you just bought -- just use VMware Server!
Is it sour grapes to complain about an article that calls your competitor's product "flawed" in the title? I see this mistaken comparison so often, maybe I should start a new "apples to oranges" category in the blog for all these sightings. Of course, they'll go away as soon as Microsoft's upcoming Viridian hypervisor is here (2008? 2009? Infinity + 1?), and they strangle MSVS and dump it in a back alley. In the meantime, I guess VMware has some more marketing to do, since VMware Server is a great solution to pop on top of Windows Server and get started virtualizing -- no cost, no Linux, and it runs just fine on your current hardware.
--jtroyer

Not sure why my trackback never showed up, but I've commented on this here: http://h0bbel.p0ggel.org/2006/12/05/esx-vs-virtual-server/
Posted by: Christian Mohn | December 05, 2006 at 02:20 AM
Maybe we should setup a site
http://esx!=msvs.com
Posted by: Tarry Singh | December 05, 2006 at 04:56 AM
So much scaremongering about Linux. People should get familiar with it, 'cause it's really a great OS, and they potentially have a *lot* to gain from it. It's *really* not hard at all. Pick Ubuntu and you're good to point-n-click your way to freedom. Sheesh.
Posted by: Joseph | December 05, 2006 at 05:45 AM
No, it's not sour grapes, and don't stop complaining. In order to have _balanced_ article, Barrett should have inteviewed VMware customers as well as MSFT customers. If not that, at least he should have interviewed people who know the difference between VMware Inc. and it's products. This article does it's readers and the general community a disservice. Keep up the noise on these, and the authors will hear and respond.
Posted by: c2v3m2n | December 05, 2006 at 12:50 PM
John is right, but part of the problem is that many people are starting to consider the word "VMware" as synonymous with virtualization. It's almost like the whole "Kleenex and tissue" or "Xerox and photo copy" situation. Although not quite that bad yet, it's a problem that is good and bad to have.
Again, in this case like so many others, people start talking about VMware but forget to qualify their argument with the product name, ESX Server or Server. And then to add fuel to the fire, they mix the products mid-stream causing further confusion. Good points John!
Posted by: David Marshall | December 06, 2006 at 06:22 PM