Virtualization technologies have become the Next Big Thing in corporate IT over the past couple of years. With the potential for huge savings, IT executives have been clamoring to virtualize, especially in the data center.
VMware has dominated the virtualization market, but last year Microsoft released its first serious server virtualization product: Hyper-V. While not as fully featured as VMware’s ESX Server, Hyper-V is an impressive first attempt.
Hyper-V Server 2008 is a free download from Microsoft that installs on bare-metal systems. Server Core is used as the basis for the install, but you’ll only be able to perform a few basic tasks, such as join a domain and configure network settings, which are essential for integrating Hyper-V into your environment.
The Hyper-V Server Role can be added to Full or Core editions of Server 2008. The final Hyper-V code wasn’t available at the time of Server 2008’s release to manufacturers, so you’ll need to download the updated bits from Microsoft to avoid installing the release candidate code. The RTM version of Hyper-V will be included in Server 2008 Service Pack 2. (Hyper-V RTM Update: http://support.microsoft.com/default.aspx/kb/950050.)
I strongly recommend that, as a Hyper-V beginner, you work with the Full edition of Server 2008 and install the Hyper-V role. Once you’ve mastered the basics, you can then move to Hyper-V Server or Server Core; any sooner and you’ll be tearing your hair out, as these editions require remote management of Hyper-V, which brings its own set of complications.
Unlike Microsoft Virtual Server 2005, Hyper-V relies on hardware-assisted virtualization technology from Intel, or Intel VT for short. Don’t assume that all of Intel’s newest processors support Intel VT. Check Intel’s website before making a purchase. Not only does the processor need to support Intel VT (or AMD’s virtualization technology, AMD-V), but a compatible motherboard and BIOS are also key components to ensure that Windows Server can start the hypervisor. Hyper-V runs only on x64 processors with hardware Data Execution Prevention — Intel XD or AMD NX — enabled.
If you’ve got the hardware requirements right, installing Hyper-V is simple. Log on to Windows Server 2008 (Full Edition) with an admin account:
Before installing your first virtual machine (VM), it’s important to understand networking in Hyper-V, which uses the concept of virtual switches to route traffic between VMs, hosts and other physical devices.
When you add a virtual network interface card (NIC) to a VM, you have the choice of leaving it disconnected or connecting it to a virtual network, often referred to as a virtual switch. Here are the steps to create a virtual network that will be used to connect VMs to the physical NIC on the parent partition (physical host):
Open the Network and Sharing Center Control Panel applet and click Manage network connections under Tasks, and you’ll see the new network represented as a virtual switch (Figure 2). Right click and select Properties for both the physical and virtual NICs, and you’ll notice the physical NIC has only the Microsoft Virtual Network Switch Protocol bound. Conversely, the virtual switch has all other installed protocols bound (Figures 3 and 4).
While it is possible to get Hyper-V up and running with only one physical NIC, Microsoft recommends a minimum of two NICs — one for the parent partition and one for your child partitions (VMs) — so that if the parent partition wants to communicate with other physical servers on the network, it can do so on a dedicated NIC without having to pass traffic through a virtual switch.
Once you’ve got your virtual switch configured, creating a new VM is as easy as clicking New on the Actions pane and selecting Virtual Machine from the menu. The wizard will guide you through the process of configuring a disk, assigning memory and connecting the VM to a virtual network. Figure 5 shows the full range of configurable options (note the lack of support for USB devices).
Hyper-V Integration Services provide optimized performance and usability enhancements for Windows operating systems running in child partitions. In Vista and Server 2008, Integration Services are built in and will be activated automatically if a child partition is detected, but must be installed manually for all other operating systems. You can install Integration Services on Windows Server 2000 (SP4), Server 2003 (SP2) and XP (SP2) by pressing CTRL+I in a Virtual Machine Connection window.
Of interest to those who want to use Hyper-V to create test labs, snapshots of a child partition’s state can be created to facilitate roll-back to a given point in time. You can right click on a snapshot and select Apply from the menu, and the VM’s recorded state is restored within seconds (Figure 6).
The Hyper-V Manager console can be downloaded as a separate component for Vista SP1 and includes the Virtual Machine Connection tool (http://support.microsoft.com/kb/952627/). However, there’s a multitude of configuration steps required to get it working.
If you intend to use Server Core or Hyper-V Server 2008, you’ll have little choice but to set up remote administration. While not a supported solution, the complex configuration can be simplified using the Hyper-V Remote Management Configuration Utility (http://code.msdn.microsoft.com/HVRemote). HVRemote reduces the workload to one or two commands on client and server. You’ll find documentation on the site that explains clearly how to use the tool.
There’s good news on the licensing front. If you license Windows Server 2008 Enterprise and run the Hyper-V role, you can install up to four virtual instances of Server 2008, or downgrade to a previous release. One caveat, however: If you use the maximum four free licenses, the host server can be used only for Hyper-V and not for other infrastructure tasks such as Active Directory or Dynamic Host Configuration Protocol. As of January 2009, a Windows Server 2008 Client Access License is no longer required to access child partitions, as long as the host server is used only for Hyper-V.
Storage options for Hyper-V include direct attached storage, Fibre Channel and iSCSI storage area networks. Hyper-V provides a feature called Quick Migration on the Enterprise and Datacenter editions of Windows Server, which lets you move VMs from one physical host to another by saving the VM, moving and then restoring to the previously saved state. This system involves some down time and requires two physical hosts to be clustered. Also, be aware that unlike VMware’s ESX, Hyper-V doesn’t natively support NIC teaming. That’s not to say NIC teaming can’t be done with Hyper-V, but it’s dependent on the capabilities of third-party NIC drivers and utilities, and cannot be managed in Hyper-V Manager.
Russell Smith is an independent consultant based in the United Kingdom who specializes in Microsoft systems management.