Documenting a virtualization project

Experiences in Virtualization

Notes about the Hyper-V Planning and Deployment Guide

Posted by martijnl on November 11, 2008

Because I want to know more about Hyper-V I decided to download and read the official Planning and Deployment Guide. The current version is from August 2008. Here’s what interested me about the document (combined with information from the Microsoft website):

Regarding enterprise virtualization deployments:

  • Licensing for virtualization can be done for the Standard, Enterprise and Datacenter Editions. Looking up “licensing for virtualization” on the website directs you to the datacenter edition. This edition is only available through a Volume License agreement. It has an estimated retail price of $2999 per CPU. This will not be the price that most large customers pay because of volume discounts. Datacenter Edition has the advantage  that you do not have to pay for licensing on the individual virtual machines that you run on a Datacenter Edition licensed host. Although you license the processor you still need to buy CAL’s (Client Access Licenses). These are $40 per user (list price, much lower through volume discounts) and a company using Windows Servers should have those already.
  • The host system specification for Standard Edition are limited to 32GB of RAM. A VM running on Standard Edition can not have more than 31GB of vRAM.
  • The maximum host memory specification for Enterprise and Datacenter Edition is 1TB with 64GB of vRAM per VM.
  • You can run a maximum of 128 VM’s at the same time.
  • Guest OS support for Linux is limited to SLES 10 (Suse Linux Enterprise Server) SP1 and SP2 with only 1 vCPU. No other Linux flavours (RHEL, Debian, Ubuntu Server) or Solaris are supported.
  • Operations such as a remote OS shutdown command or time synchronization (Integration Services) are not available for Linux servers.

I am still looking into the differences between Hyper-V on a Server Core installation and Hyper-V on a full servers installation. More on that in a follow-up post probably.


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: