The Role of Microsoft Hyper-V for Virtualization in Windows Server 2008
Microsoft Hyper-V (or Windows Server Virtualization) is a hypervisor-based virtualization system for x64 systems. A beta version of HyperV is included in the x64 editions of Windows Server 2008. A big attraction with Hyper-V is that it is built-in to Windows Server 2008. reducing the expenses considerably, straight away.
Microsoft describes the Hyper-V architecture as ‘micro-kernelised’, which enables it to minimize the footprint of the core Hyper-V code, while still delivering a rich set of features.
Hyper-V includes a hypervisor which is a very thin software layer, less than 1 megabyte in size. This separates the processor from the parent and child partitions. The hypervisor supports all the partitions on the host computer and also provides strong security separation between the parent and child partitions.
More information about the architecture of Hyper-V can be obtained from the last reference link that is mentioned in this article.
Table of Contents
- System Requirements
- How to enable HyperV role in Windows Server 2008
- How to create and set up a virtual machine
- Guest OS Installation
1. System Requirements
1.1. Production and Testing Environment
An x64 processor with Hardware-assisted Virtualization. This is available in processors that includes a virtualization option; specifically, Intel VT or AMD Virtualization.
Hardware Data Execution Protection (DEP) must be available and should be enabled. To be exact, you must enable Intel XD bit (execute disable bit) or AMD NX bit (no execute bit).
Recommended : 2 GHz or Faster
Minimum: 1 GB RAM; Recommended: 2+ GB RAM Maximum (for 64-bit systems): 32 GB
Available Disk Space
Minimum: 10 GB; Recommended: 40 GB or greater
Note: Computers with more than 16 GB of RAM will require more disk space for paging, hibernation and dump files.
Minimum: 1; Recommended: 2 or more
The actual requirements can vary, based on your system configuration and the number of virtual machines that you choose to run. Processor performance is dependent upon the clock frequency of the processor as well as on the number of cores and the size of the processor cache. Disk space requirements for the system partitions are approximate.
You can gather more details about the requirements of Hyper-V at:
The following table outlines which Hyper-V-enabled product would suit your needs:
|Virtualization Needs||Microsoft Hyper-V Server 2008||Windows Server 2008 Standard||Windows Server 2008 Enterprise||Windows Server 2008 Datacenter|
|Test and Development|
|Mixed OS Virtualization(Linux and Windows)|
|Local Graphical User Interface|
|High Availability – Clustering|
|Large Memory Support(Host OS) > 32 GB RAM|
|Support for > 4 Processors(Host OS)|
|Ability to Add Additional Server Roles|
|Guest Virtualization Rights Included in Host Server License||None – Each Windows Guest VM Requires a License||1 Physical + 1 VM*||1 Physical + 4 VMs*||1 Physical + Unlimited VMs(Free)|
In order to install the Hyper-V, you need to make sure of the following:
1. The Processor must be VT (Virtualization Technology) enabled. 2. The Operating system must be Windows Server 2008.
You can verify whether your processor has the VT function using the following steps:
- “Start -> Run -> dxdiag”. From the General tab you can check the details of processor.
- If the processor is “Intel® Core2 Quad processor (Q9300)”, then you can check out its functions at:
- The VT function is available for this processor “Intel® Core2 Quad processor (Q9300)”.
- You need to enable VT via BIOS too.
2.1. How to enable processor-VT via BIOS:
You have to do the following to enable processor-VT via BIOS.
Advance Settings > Processor Options > Intel Virtualization Technology (in this case)> Enable > Save Setting.
You must also enable Hardware Data Execution Protection (DEP).
In case you enabled VT (Virtualization Technology) after the OS installation (Windows 2008) or forgot to do so, then the installation of Hyper-V role will throw an error message which says that Hypervisor couldn’t be loaded or initiated.
If it is found to be disabled, you need to enable it using the steps mentioned above and then perform an OS reload to make sure that it is working with VT enabled version. Note that Hyper-V will work with Windows 2008, only after enabling VT.
3. How to enable HyperV role in Windows Server 2008
- Click Start -> Server Manager ->
- In the Roles Summary area of Server Manager, click “Add Roles”.
- On the “Select Server Roles” page, click Hyper-V.
- On the “Create Virtual Networks” page, click one or more network adapters, if you want to make the network connection available to virtual machines.
- On the “Confirm Installation Selections” page, click Install.
- In order to complete the installation, you need to restart the computer.
Click “Close” to quit the wizard, and then click “Yes” to restart the computer.
- After the computer is restarted, log on to the same account that you used to install the role.
After the “Resume Configuration Wizard” completes the installation, click Close to quit the wizard.
4. How to create and set up a Virtual Machine
After you installed Hyper-V, you can use the steps below to create a virtual machine and set up an operating system on the virtual machine.
- Open Hyper-V Manager (Click Start -> Administrative Tools -> Hyper-V Manager).
- From the Action panel -> New -> Virtual Machine.
- From the “New Virtual Machine” Wizard, click Next.
- On the “Specify Name and Location” page, specify the name for the virtual machine and where you want to store it.
- On the “Memory” page, specify the required memory to run the guest operating system which you want to use on the virtual machine.
- On the “Networking” page, connect the network adapter to an existing virtual network, if you want to establish network connectivity at this point.
- On the “Connect Virtual Hard Disk” page, specify a name, location and size to create a virtual hard disk and then install an operating system on it.
- On the “Installation Options” page, choose the method that you want to use to install the operating system.
- Click Finish.
Here are the short cut commands to get into the Management console:
Microsoft Hyper-V-Image Management Service - vhdsvc Microsoft Hyper-V-Networking Management - nvspwmi Virtual Machine Management - vmms
5. Hyper-V Supported Guest OS
You can see the list of Hyper-V Supported Guest OS at the link :
The installation of FreeBSD (as Guest OS) also worked fine for me.
Other guest operating systems such as Ubuntu Linux 6.06/6.10/7.10 or Fedora 8/9 are not supported, though they have been reported to run. The Installation guide links are added in the reference section.
You can download and install the guest OS from the following sources:
- Free BSD source: ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/200806
Follow the steps below:
- Create a new Virtual Machine using Hyper-V.
- Remove the default network card that is added by the wizard.
- Add hardware and chose Legacy network adapter.
- Start the machine and “mount” ISO image to start booting FreeBSD.
- Modify the parameters as per your requirements.
- For OpenSuse, please go here:
Likewise, you can install Linux distribution as well as Windows in a HyperV role enabled Windows server 2008. You can install the Windows Guest OS by downloading the ISO image of it.
- For Installing Fedora Core 8 on Hyper-V, use the link:http://blogs.msdn.com/virtual_pc_guy/archive/2007/12/31/installing-fedora-core-8-on-hyper-v.aspx
The biggest criticism Hyper-V receives is that:
- It doesn’t do “Live Migration”, that is, moving a Virtual Machine (VM) from one server to another without any downtime.
- Hyper-V’s “Quick Migration” gives only a few seconds downtime until everything is back as it was before.
Advantages & Disadvantages:
- Server Virtualization allows your client to run multiple servers on one physical computer, which renders into more efficient use of resources.
- As it is included with Windows Server 2008, the license cost is less than VMware.
- However, Hyper-V is still on Version 1.0 and this makes it hard to predict how good it is.
- Hyper-V comes with just the basic management software. Further Advanced systems may need the Microsoft System Center Virtual Machine Manager. HyperV management software has less options as compared to the Virtual Machine Manager.
About the Author
Joseph Symon has been with Bobcares for more than two years. He has marked his presence in the company through his contributions towards enriching the knowledge level in the company. He is a Linux expert, and specializes in installing and configuring systems and customizing them for specific needs. Joseph is highly passionate about learning new technologies.