Windows IT Pro is the leading independent community for IT professionals deploying Microsoft Windows server and client applications and technologies.
  
  
  Advanced Search 


May 27, 2008

Virtualization Shootout, Part 1

Microsoft Hyper-V vs. VMware ESX Server 3.5
RSS
Subscribe to Windows IT Pro | See More Products / Software Articles Here | Reprints | Or get the Monthly Online Pass—only $5.95 a month!
SideBar    Commonsense Virtualization

The Price Is Right
A big difference between VMware’s ESX Server and Microsoft’s Hyper-V is the price. Despite the trend toward free virtualization products, ESX Server has always been a chargeable product and is the staple of VMware’s product line.

The fact that VMware charges for ESX Server hasn’t hindered the product’s adoption. Its performance and robustness have convinced many organizations to use it as their primary virtualization platform. For this review I used the VMware Infrastructure Foundation product, which includes ESX Server 3.5, VMware Virtual Machine File System (VMFS), VMware Virtual Symmetric Multi-Processing (vSMP), the VirtualCenter agent, VMware Consolidated Backup, and VMware Update Manager.

In contrast, Hyper-V is part of the Server 2008 OS, making it essentially free to organizations running Server 2008. Hyper-V is included in the following x64 editions of Server 2008:

  • Windows Server 2008 Standard Edition x64
  • Windows Server 2008 Enterprise Edition x64
  • Windows Server 2008 Datacenter Edition x64

Because Hyper-V is a 64-bit technology, you need x64 hardware and you need to run one of the x64 editions of Server 2008. Mysteriously, Microsoft does make three versions of Server 2008 that don’t include Hyper-V (aptly named Windows Server 2008 without Hyper-V)—but the price difference is negligible, at $28. Hyper-V is also not included in Windows Web Server 2008, Windows HPC Server 2008, or Windows Server 2008 for Itanium-Based Systems.

Table 2 shows pricing for the two configurations I tested. In each case the system was set up to run eight VMs, all with Server 2008 Enterprise Edition. This table uses retail pricing. Most businesses use Microsoft’s volume licensing, which has a lower cost for the Windows Server OS. Remember that in a production scenario you would also need CALs to access the Windows Server OS. The retail prices in Table 2 include 25 CALs. However, in a production setting you would typically require additional CALs.

Windows Server 2003 R2 and Server 2008 Enterprise Edition allow as many as four active virtual Windows instances at no additional cost. This licensing is the same whether you use Microsoft or VMware virtualization products. Running eight active VMs requires two Server 2008 Enterprise Edition licenses. Although not used in this comparison, Windows Server 2003 R2 Datacenter Edition and Server 2008 Datacenter Edition allow an unlimited number of virtual Windows instances no matter which virtualization platform you choose.

First Across the Line…
The basic virtualization and feature sets provided by Microsoft’s Hyper-V and VMware’s ESX Server are quite comparable and so far it’s a dead heat. ESX Server offers broader support for more Linux distributions and has a couple of more advanced features, such as support for live migration and shared memory between VMs. However, its command-line management is unfamiliar to most Windows administrators, its limited device support requires a more restrictive hardware platform, and it comes at a higher price than Hyper-V—which is essentially incorporated into Server 2008. Stay tuned for part 2 where I continue this shootout by looking at ESX Server’s and Hyper-V’s advanced systems management and then find out where the rubber meets that road as I run some revealing performance tests.

End of Article

   Previous  1  [2]  Next  


Reader Comments
II registered specifically to comment on this, I must say it was an interesting read. Comments such as "The VMware Virtual Infrastructure Client [...] doesn’t let you perform server management functions such as adding and removing network cards." are just _wrong_, there's no other way of putting it.

I'm also not entirely sure of your driver arguments - as I understand from looking at the ESX boot procedure, it only loads the ones it needs, and you're also relying on thirdparty drivers for hyper-v. In fact, I would agree with the infoworld post (http://weblog.infoworld.com/enterprisedesktop/archives/2008/05/hypervs_achille.html), the drivers are just not up to snuff for me to trust running multiple servers in a production environment on it.

jutasuk May 29, 2008 (Article Rating: )


Yo brother, if you ain't familiar with the cli either nix or Mickeysoft how do you survive in the real world ? All S&P 500 enterprizes have nix and MS on board. But I hope you will have a good look at DRS and HA along with storage virtualisation which are available with VirtualCenter, I did not hear you mention this sofar.

rohad May 29, 2008 (Article Rating: )


> The VMware Virtual Infrastructure Client lets you create and manage VMs. However, it doesn’t let you perform server management functions such as adding and removing network cards. You need to use the command line to perform those types of functions.
The above statement and several others in the article are false. One can manage ESX without knowing any Linux. The article insinuates that one can manage (i.e. create VM, configure the host, etc) from the console using a command line. That is not true and really casts doubt on the article an “unbiased” comparison. The VI client can manage the host fully including adding hardware. The install process does have a GUI version and with ESXi you essentially don’t have a service console anymore.
> The Hyper-V hypervisor has no device drivers
This of course is a complex topic but in this article it is written to insinuate that Hyper-V will be a much more stable product. That remains to be seen, but it is misleading to suggest that it will be based on what is still release candidate software. The hypervisor level for ESX (the vmkernel) is a few MB in size – about 200K lines of code. The Hyper-V hypervisor is smaller (600 kb), but it has a significant dependence on the parent partition (as well as for device drivers). If you lose the parent partition with Hyper-V you lose your VM (see 1st link). With ESX if the service console goes down, your VMs continue to run. You might not be able to manage your host, but at least the VMs run until you can bring the host down at a more convenient time. Which is the better architecture remains to be seen, but to say Hyper-V is better today is poor journalism.
http://blogs.technet.com/mattmcspirit/archive/2008/05/16/getting-my-head-around-the-hyper-v-architecture.aspx
http://it20.info/blogs/main/archive/2007/06/17/25.aspx

Dave Mishchenko May 29, 2008 (Article Rating: )


continuing from above...
>> which introduces third-party code into the hypervisor and limits the hardware that ESX Server supports. <<

Various statements in the article suggest that ESX will be less stable due to 3rd party drivers. It’s somewhat of a misconception that one can add any Linux driver to ESX to have it support a given piece of hardware. This is not the case. Driver are created in co-operation with VMware and based on past experience, I have no concerns about drivers that have been developed for ESX. All software, including drivers, will have potential bugs, but this is the case with drivers for both ESX and Hyper-V and in both cases VMware and Microsoft are taking the steps necessary to ensure that only quality drivers are provided.
A few other shorter points on this http://windowsitpro.com/files/01/98879/table_01.gif
- ESX is 32 bit / Hyper-V is 64 bit therefore it is better. Your performance testing will show that is not the case.
- “Hyper-V can run an unlimited number of active VMs” - but practically how many will a host be able to run. The 128 VM limit for ESX in a practical limit.
- Hyper-V host memory supported is 2TB – ESX is actually 256 GB and that’s the tested figure.

Dave Mishchenko May 29, 2008 (Article Rating: )


And lastly ... :)

Pricing – a) if one is going to include 3 years of 24 x 7 support on the VMware side, then one should also include Software Assurance on the Microsoft side as well as support cost. It would be more accurate to have the cost of ESX Foundation at $1545 and that would include one year’s worth of upgrades and support.
b) It would have been better to have used Datacenter processor licensing in this case. In both cases, 2 DC processor licenses would be roughly $6000 lowering the overall cost of both systems.
c) Pricing comparisons such as this are disappointing. The cost of a system is much more than just adding up the licensing components. Plus in the situation given, ESXi would be a fairer product to use with a price of only $500 (actually $99 from Dell). But in reality, one must add up the cost of hardware, training, VM density, etc to really do a fair cost comparison.

Dave Mishchenko May 29, 2008 (Article Rating: )


Another thing that is not pretty correct is the data in Figure 1.

Support for 32 socket in ESX and 64 socket in Hyper-V is wrong.

ESX supports 32 logical processors that in actual tecnology would mean 32 cores (example: 8-socket quad-core). Hyper-V only supports 16 logical processor or simply put, with the latest technology, 4-socket quad-core.

When Intel is coming out with their new 6-core cpu's (sooner than later) this will make 24 cores for a standard 4-socket systems .... Hyper-V won't likely be able to handle that.

I wanted to mention this because this is usually a big source of confusion.

Massimo.

MassimoReFerre May 30, 2008 (Article Rating: )


Just dont understand the many comments in the article, such as the one I've copied in below, that refer to ESX as the "heavyweight" hypervisor - inferring that Hyper-V is a smaller footprint, with therefore a smaller attack surface. That is rediculous - has the author ever heard of ESX Server 3i - or whatever VMware is calling it these days?

Our testing shows ESX Server 3i - is a fully functional hypervisor in a 32 mg footprint. Our current evaluations of the pre-release of Hyper-V, which requires at least Windows Server Core to function, show that it has at minimum a 3.9GB footprint. That's a full 120X larger than ESX 3i. Even ESX Server 3.5 with the service console is arund 2GB - half the size of Hyper-V. With obvious faults like this inthe aurthors analysis, it makes me wonder how much influence MSFT had in this article - I can't view the rest of the analysis as unbiased - the article even uses MSFT graphics.



"the ESX Server hypervisor is a heavyweight hypervisor that contains device drivers. In contrast, the Hyper-V hypervisor is a thin hypervisor that contains no drivers and no thirdparty code."

BretStephens May 30, 2008 (Article Rating: )


Here are some major corrections for your article. It will be in multiple parts:

Note: I do work for VMware but the items I'm listing are public fact and just corrections to the author's research.

1) The "real" drivers for the Hyper-V solution are housed in the parent partition. They use regular Windows drivers developed by MS and 3rd parties like the OEMs and others. The VMs have generic drivers that must push traffic through the real drivers in the parent partition. Both VMware and MS use 3rd party drivers. The big disadvantage of the Hyper-V solution is scaling of I/O since all I/O must go through the parent. MS delayed the release of Hyper-V previously because of "scalability of I/O" issues. It's also been well blogged and documented on the web. A little google search will turn it up in a flash. What you stated in the article is completely inaccurate about the drivers and shows a complete lack of knowledge of the architecture. You also might want to read Randall Kennedy's article about 3rd party drivers in Hyper-V and the security risk there: http://weblog.infoworld.com/enterprisedesktop/archives/2008/05/hypervs_achille.html.

mikedipetrillo June 02, 2008 (Article Rating: )


2) Reliance on the Linux CLI:

Very few people out there use the CLI in our Linux Service Console. Furthermore this has been removed in the ESXi product line. Everything in the product is and can be done from the Virtual Center Client. The client is free with every version of the product so there's no extra cost for using it. In addition, you were incorrect about needing the CLI in order to add network or storage devices. Both of those are in the GUI and have been since VMware ESX 1.5 (2002). Here are links to the manuals with pictures in case you need a refresher before posting a more accurate article: http://www.vmware.com/support/pubs/vi_pages/vi_pubs_35.html.

Here's the part on networking: http://pubs.vmware.com/vi35/server_config/sc_networking.5.6.html.

Here's the part on storage: http://pubs.vmware.com/vi35/server_config/sc_storage.10.1.html.

Lastly, we have tens of thousands of installations in Microsoft only shops and those customers have had no issues installing or managing VMware for the past 9 years.

mikedipetrillo June 02, 2008 (Article Rating: )


“The Hyper-V virtualization role can be installed on either a full Server 2008 installation or on a minimal Server Core installation. Server Core is the better choice for a virtualization server host because it has all the extraneous Windows components stripped out (e.g., the graphical shell, Internet Explorer—IE, Outlook). This bare-metal approach gives Server Core less overhead and makes it more efficient. Server Core is also more secure because of the reduced attack surface area, as well as more reliable because of the smaller number of components that might need patching.”

Server Core may be less than a full installation but at the current RC1 release of Hyper-V an install of Hyper-V plus the required Server Core installation runs 3.99 GB. That’s not a typo. That’s still a HUGE trusted computing base when you compare it to 32 MB for ESXi or even 1.8 GB for a full ESX install. Microsoft may claim that VMware is a large, monolithic hypervisor because of where we put the drivers but 32 MB still seems pretty compact compared to the 3.99 GB of a minimal Hyper-V install.

mikedipetrillo June 02, 2008 (Article Rating: )


 See More Comments  1   2   3 

You must be a registered user or online subscriber to comment on this article. Please log on before posting a comment. Are you a new visitor? Register now




Top Viewed ArticlesView all articles
WinInfo Short Takes: Week of November 9, 2009

An often irreverent look at some of the week's other news, including some more Windows 7 sales momentum, some Sophos stupidity, Microsoft's cloud computing self-loathing, more whining from the browser makers, Zoho's "Fake Office," and much, much more ...

Command Prompt Tricks

One reader shares his tip for setting up the command prompt to reflect a remote path. ...

Windows 7 Sets Sales Record

Microsoft CEO Steve Ballmer described Windows 7's first ten days of sales as "fantastic" while in Japan yesterday. ...


Related Articles Essential Server Core Setup Commands

The Soul of Windows Server 2008: Server Core and Hyper-V

A First Look at Windows Server 2008 Hyper-V

Windows Server Virtualization Features

Related Events Deep Dive into VMware vSphere

RUUP4IT? R2 Takes You Vertical and Virtual

Check out our list of Free Email Newsletters!

News and Analysis eBooks Getting Maximum Performance from Your Web-based Applications

Business Process Automation - Managing Cost in Your Enterprise

Related News and Analysis Resources Introducing Left-Brain.com, the online IT bookstore
Looking for books, CDs, toolkits, eBooks? Prime your mind at Left-Brain.com

Discover Windows IT Pro eLearning Series!
Clear & detailed technical information and helpful how-to's, all in our trademark no-nonsense format


Windows IT Pro Home Register FAQ for Windows WinInfo News
Europe Edition About Us Contact Us/Customer Service Media Kit Affiliates / Licensing  
SQL Server Magazine Office & SharePoint Pro DevProConnections IT Job Hound
Left-Brain.com Technology Resource Directory asp.netPRO ITTV Windows SuperSite 
 
 Windows IT Pro is a Division of Penton Media Inc.
 © 2009 Penton Media, Inc. Terms of Use | Privacy Statement