For this new release of Microsoft® Windows®, Microsoft is making available a virtualization technology known as Hyper-V™. With Hyper-V on Windows 8 Pro, you will be able to run Windows in a virtual machine just using the software that is included in the box. Windows Virtual PC and XP Mode will not be supported in Windows 8.
This section provides an overview of Hyper-V in Windows 8 and provides information that you can use to answer questions about Virtual PC and XP Mode no longer being supported.
Hyper-V is the name of the virtualization technology included in Windows 8. Previously, Hyper-V was a server-only product included with operating systems like Windows Server® 2008 R2, and was used primarily as the Microsoft solution for virtualizing servers in a datacenter. Because of its roots as a server virtualization product, Hyper-V is an extraordinarily robust VM solution, and supports a broad number of server and datacenter specific scenarios.
Much work was done to bring Hyper-V to client computers to enable Hyper-V to run on them without compromising the client experience. This included things like adding support for the host going into standby and supporting wireless networking.
The management interface that is provided on Windows 8 is the same as what you will see in our server operating systems. While this exposes a broad array of functionality for creating VMs, it also has the potential to make building and running VMs in Windows 8 a more complicated experience. In this section, we will discuss the most important aspects of Hyper-V and the basics of what you need to do in order to get up and running.
In order to use Hyper-V, your system will need to meet the following requirements.
Figure 1: Hyper-V requirements in MSinfo32
Hyper-V is not enabled by default. It must be enabled through the Turn Windows Features On or Off interface in the Programs Control Panel. After checking Hyper-V and finishing the installation, you will need to reboot your computer.
Figure 2: Turn Windows features on or off
After restarting, you will see two new tiles at the end of your Start Screen.
Figure 3: Hyper-V tiles
Once you've installed Hyper-V, the work of configuring, building, and running Virtual Machines happens through the Hyper-V Manager. We will use this interface to configure and use Hyper-V in the next sections.
Figure 4: Hyper-V Manager
Before we create a virtual machine with Hyper-V, we first need to create a network for it to attach to. We do this by creating a Virtual Switch in the Hyper-V Manager.
Note: Creating a virtual switch prior to creating your VM is not strictly necessary, but having it created before you create your VM makes the process of creating the VM much easier. This is why we recommend creating the virtual switch first.
Figure 5: Actions pane
Figure 6: Virtual Switch Manager
Figure 7: Select external network
Figure 8: Applying Networking Changes
Now that we've created the virtual switch, we can create a VM. Before beginning, it would be a good idea to make sure that you have access to the DVD or ISO that you will be using as your installation source.
Figure 9: New Virtual Machine
Figure 10: Wizard opening screen
Figure 11: Select location for the virtual machine
Note: From here on, you can click the Finish button to automatically create the VM with the defaults defined in Hyper-V.
Figure 12: Specify amount of memory
Note: Any memory that you allocate to a VM will no longer be available for use by the host computer when the VM is running.
Figure 13: Select virtual switch
Figure 14: Create or attach a hard disk
Figure 15: Installation options
Figure 16: Summary of actions
After the VM has been created, you will see it in the list of available Virtual Machines in the Hyper-V Manager.
Figure 17: List of available virtual machines
After you have created your VM, you can modify the properties of that VM by selecting Settings from the Actions pane on the right.
Figure 18: Settings window
From this window you can make a wide variety of changes to your VM to alter its startup behavior or hardware configuration, including some of the following:
Once you have created and configured your VM, starting it is relatively easy. The VM will be accessed through the Hyper-V Virtual Machine Connection software that is installed as part of Hyper-V, and you can launch this software either directly from the Start Screen or by opening the VM from the Hyper-V Manager.
Figure 19: Connecting to a VM
If you open the Virtual Machine Connection software from the Start Screen, you will see a Windows like the one shown below with an option to connect to a remote Hyper-V host and a list of all the VMs running on that host. Selecting a host and VM will open that VM in the Virtual Machine Connection software.
Note: You will need to run this software as an administrator if you open it from the Start Screen.
Figure 20: VM Connection
Many of the options that were exposed in the settings for the VM are also shown in the menu bar for the Virtual Machine Connection software. You can use this bar to do things like take screenshots, change the DVD that is mounted to the VM, or restart or suspend the VM.
Figure 21: VM Connection menu bar
There is an important distinction that should be made between VMs running in Hyper-V and VMs running in Virtual PC or any other client virtualization software. In Virtual PC, running a VM would open that VM on the user's desktop and within the context of their user account. Signing out of that user account would stop and close the VM as part of that process.
With Hyper-V, VMs run as part of the Hyper-V service, and not within the context of any particular user account. Closing the Virtual Machine Connection software does not close, suspend, or shut down the VM; it continues to run in the background. Signing out of Windows 8 while a VM is running will allow the VM to continue running in the background. If you reboot the computer while the VM is running, but don't sign in after the restart, the VM will start on its own and continue to provide services like Remote Desktop or file sharing.
Snapshots provide a way to capture the exact state of a particular VM as it existed at one specific point in time. Unlike a backup or system restore snapshot, this is a complete snapshot of the VM as it exists at the time the snapshot it taken. This means the state of the disk and the contents of memory are saved as well, and you can take these snapshots at any point in time, such as partway through Windows Setup or at beginning of Windows Welcome, should you need to test or repeatedly access these interfaces.
You can quickly take a snapshot of the VM by selecting Action > Snapshot from the menu bar. This will begin taking the snapshot and prompt you to name it.
Figure 22: Snapshot
You can take multiple snapshots of the same VM so that you can just back and forth between different configurations or states of the same VM. All of these snapshots are displayed in the Snapshots section of the Hyper-V Manager.
Figure 23: Snapshots listings
You can apply any snapshot by right-clicking that snapshot in the Hyper-V Manager and selecting Apply. You can also quickly revert back the previously taken snapshot by using the Revert option in the menu bar.
All of this works together to make Hyper-V a very useful tool for recreating and reproducing customer issues.
There are a lot more specific details here, if anyone wants to go deeper:
For more information about Hyper-V on Windows 8, please read the following resources.
Bringing Hyper-V to Windows 8http://blogs.msdn.com/b/b8/archive/2011/09/07/bringing-hyper-v-to-windows-8.aspx
Client Hyper-V Survival Guidehttp://social.technet.microsoft.com/wiki/contents/articles/7704.client-hyper-v-survival-guide-en-us.aspx
Client Hyper-V on Technethttp://technet.microsoft.com/en-us/library/hh857623.aspx
User Interface: Hyper-V Managerhttp://technet.microsoft.com/library/cc770494.aspx
How are you today i hope you are fine?
My name is kama sambo,i saw your profile today and i love it,i think we can build a good relationship/friend from there. Dear please write me back through my email address so that i can send you my photos and for more discussion (firstname.lastname@example.org)
I am waiting for your reply soon
My dear please contact me with this email (email@example.com)
Can I assume that you are able to RDP onto any of your guest vms and if so would this be via the internal switch. If so then it would be good to get a fixed IP address from say a guest hosted DC ... The reason I ask is I have been struggling to RPD onto my guests this way. Instead I have used the external switch and whatever IP address the ISP / gateway provides - which of course changes whenever I move my laptop somewhere. Has been a nightmare for me!
An excellent article - thank you. I had no trouble following your instructions. Only problem was that I could not establish an internet connection with my XP VM. There is no adapter appearing in the network connection window either.
I have all checked "Yes" in MSINFO32 for Hyper-V but I am not seeing it on Add/Remove Feature list. What do I need to do?
Thanks for taking the time to write this article.
I've been researching Hyper-V for the entire morning, and this is exactly the information that I needed to make a start.
what are disadvantages using MS VPC 2007 / Windows VPC ,
Otimo, muito obrigado
Bom Post... Parabéns...
check this usefull article will help you Boot the system using the cd dvd drive in Windows 8 and many more.
Glad I came across this... I have a question when I run msinfo32 on my machine at the bottom of the summary it says "A hypervisor has been detected. Features required for Hyper-V will not be displayed". Is that a yea or nay for Hyper-V? The feature is enabled, and I can access the manager etc. build vm's but can't get into them, meaning I make it, connect, then start it just sits there saying connecting. While in the manager the vm pane shows a login screen. So I'm thinking it's there just not functioning properly...
thanks for your time!
Nice tutorial :)
I was wandering if you could help me out on this: I'm using HP ProBook 470 G0 and have verified all listed prerequisites. Then I install the Hyper-V on my Windows 8.1 Pro and after a reboot Windows won't start. It keeps bouncing those dots around. If I go into BIOS and disable DEP, then Windows will start, but I cannot run a virtual machine because a Hypervisor is not started. A guy from HP says that this laptop is not supported for Hyper-V, but I think he just blew me off :( Where can I verify if this is true or not? With Microsoft, of course.
Could you advice me for how to restart vm on windows8.1 pro after shutdown the vm?
I used windows7 vm, much much better than windows 8!