Windows Server 2008 Hyper-V is the next-generation hypervisor-based server virtualization technology that allows you to make the best use of your server hardware investments by consolidating multiple server roles as separate virtual machines (VMs) running on a single physical machine. With Hyper-V, you can also efficiently run multiple different operating systems in parallel, on a single server, and fully leverage the power of x64 computing. A feature-complete version is now available for download as a release candidate (RC). You can download the RC update for Hyper-V here to learn more about Microsoft and virtualization; please visit the Virtualization Web site, or the Virtualization TechCenter. To be eligible in the Windows Server 2008 Logo program for the Hyper-V designation, tests must be conducted on the latest available version of Hyper-V.
Hyper-V requires an x64-based processor, hardware-assisted virtualization, and hardware data execution protection. The Windows Server catalog, which can be found at the Microsoft Web site (Windows Server Catalog), lists systems that are certified for Windows Server 2008. Systems supporting the x64 architecture and supporting Hyper-V can be identified by the additional qualifier under the text “Certified for Windows”.
To fix this issue, enable the following Bios settings:
You can install Hyper-V on either a Full Windows Server 2008 installation or a Server Core installation. You can use Server Manager to install Hyper-V on a full installation, as described in the following procedure.
To install on a Server Core installation, you must perform the installation from a command prompt by running the following command:
Start /w ocsetup Microsoft-Hyper-V
After you have installed Hyper-V, you can create a virtual machine and set up an operating system on the virtual machine.
Before you create the virtual machine, you may find it helpful to consider the following questions. You can provide answers to the questions when you use the New Virtual Machine Wizard to create the virtual machine.
In the final step of this process, you connect to the virtual machine to set up the operating system. As part of the setup, you install a software package that improves integration between the virtualization server and the virtual machine.
You can configure networking for virtual machines by adding, removing, and modifying their network adapters as necessary. Each network adapter can be connected to one of the virtual networks available on your virtualization server. Virtual Network Manager enables you to add, remove, modify, and manage virtual networks. The Virtual Network Manager is available from Hyper-V™ Manager.
A Snapshot is a point in time of the state of the running or non-running VM that you can revert to anytime. They consist of a memory save state file, a Difference disk (.avhd), and a copy of the VM configuration xml file. When you revert to a snapshot, you are loading that configuration, that memory state, and using that Diff disk.
Right-click on the Virtual Machine name in Hyper-V Manager, and choose 'Snapshot'. You can do this when the VM is still running, or when the VM is turned off. You can also do this on a brand new VM that has never been started before.
When you apply a snapshot, you are reverting to the state of the VM at that point in time, including the VM configuration at that time (such as total RAM, total cores, etc).
A Saved State is a point in time of the state of a running VM, much like a snapshot; however, a Saved State can only be performed on a running VM and it can only be restored ounce, provided that no other snapshot has been applied since the System State has been saved.
To create a Saved State, right-click on the name of a running Virtual Machine in Hyper-V Manager, and choose Save. This will save the system sate and the VM will appear to be shutdown. To resume from a saved state right-click on the name of the saved Virtual Machine in Hyper-V Manager and choose Start.
Written By:
Scott Lanphear