How To Install Hyper V On Windows 8.1 Single Language
Virtual Machines (VMs) are great for a wide variety of tasks including running unlike operating systems or software configurations on a single auto. Windows 8 is the showtime Windows client operating system to include hardware virtualization support without the need for split downloads or installs. This feature in Windows 8 is called Client Hyper-V. Client Hyper-V is the same engineering science as used in Windows Server 2012 Hyper-5, so you can movement VMs from server to client, and won't need to re-learn how to use Hyper-V features and tools.
In this commodity I'll requite a high-level overview of Client Hyper-V in Windows eight and also guide y'all through the procedure of configuring Hyper-V and creating/running VMs.
What Y'all'll Need to Run Hyper-V on Windows 8
In order to run Client Hyper-Five on Windows 8 you'll need the post-obit:
- Windows 8 Pro or Enterprise 64 fleck Operating System
- 64 bit processor with Second Level Address Translation (SLAT)
- BIOS-level Hardware Virtualization back up
- At least 4GB system ram
If y'all are running 64-bit Windows 8 and see the hardware requirements listed in a higher place you're equipped to give Client Hyper-V a endeavor!
Setting Upwardly Hyper-5
The first affair to do when getting ready to run Customer Hyper-V is to make sure that hardware virtualization support is turned on in the BIOS settings. For my demonstration in this article I configured my HP Z820 desktop organisation to run Client Hyper-V. Below is a picture of the BIOS settings I configured on my HP Z820:
Once y'all have confirmed that hardware virtualization support is available and enabled, information technology's fourth dimension to enable Hyper-V in the "Turn Windows features on or off" dialog which you tin launch past typing "plow windows features" at the Commencement Screen and and so selecting "Settings" in the correct-hand pane.
Hyper-V Enabled in Windows Features
If Hyper-V wasn't enabled previously, yous'll need to reboot after applying this change. After enabling Hyper-5 it'due south a skilful idea to configure networking for the Hyper-Five environment. In order to back up external network connections, you'll need to make sure that a virtual switch has been created and is functional. To go started with this, open the Virtual Switch Manager which yous'll find on the Actions console in the Hyper-Five Manager (Type Hyper-Five at the Start Screen to find the Hyper-V Managing director).
After clicking on "Virtual Switch Manager" in the Deportment pane ensure that "External" is highlighted, and then click on the "Create Virtual Switch" button.
If you have more than than one NIC in your system, ensure that you have selected the NIC to be used for VM external network connections. Here's the settings that I used on my HP Z820:
While there are many other options and features that you lot tin configure, this is a expert starting point and is all I needed to do to beginning creating and using VMs on Window 8 Pro.
Creating VMs
Since Client Hyper-V is fully compatible with Hyper-V on Windows Server y'all tin use VMs and Vitual Hard Drives (VHDs) created on Windows Server Hyper-Five machines. Creating a new VM it'due south easy. In this section I'll outline the process to create a VM from scratch using PXE boot from the network. You can also very easily perform OS installs from USB drives or optical media like DVDs.
To create a VM you simply click on "New Virtual Auto…" nether "Deportment" on the right panel in the Hyper-V Manager. When you do this, the "New Virtual Automobile Magician" volition launch. The first task is to choose a VM name and optionally specify a path for the VM file:
Next, you lot'll determine how much retention to allocate. I chose to use the default of 512 MB to see how my VM would perform with default retention settings. I know that I can always change this later.
After that you'll need to select a virtual switch if networking is needed. In this example I chose the virtual switch that I created in the earlier steps outlined in this post.
The next pace is to setup the VHD for the VM being created. Hither you accept the option to create a new VHD, employ an existing VHD, or to postpone VHD configuration for later:
I chose to have a VHD created using the default settings. Annotation that you want to think about where the VHD file is stored during this procedure. I like to keep VM files and VHD files in the same directory for most configurations.
After clicking "Finish" I had one important step that's required to enable PXE kicking from VMs. in This last step was to create a Legacy Network Adapter in VM settings. To do this, you lot launch the settings dialog for the VM that needs network boot support, and then click "Add Hardware" which is the acme item in the left pane.
All you need to do is click the "Add" button and and then ensure that the proper virtual switch is used. That'due south it! Information technology but takes a couple minutes to perform all of these steps once y'all know what to exercise. This VM was now ready for PXE kicking and the installation of the OS.
Afterward clicking the green "Start" button for your VM in the right pane of the Hyper-V Manager, you'll then see the familiar PXE boot carte du jour where you can press F-12 for a network boot:
This works only like network booting from a physical machine. I used network kick to kick off a clean Windows 7 install equally you lot can see here:
Having VMs for different operating systems is keen when you need to exam software on different operating systems, run machine images that are isolated from the network, examination upgrade scenarios, and many more activities. Just remember to save snapshots for key configurations so that you tin revert machine state when needed.
Connecting to VMs on Windows 8
Once y'all take your VMs setup there are two great options for interacting with and connecting to your VMs: the Hyper-Five Managing director, or Remote Desktop Connection using Remote Desktop Protocol (RDP).
Using the Hyper-V manager you lot'll exist able to command your VM state in the Virtual Machine Connection Window only you'll accept a more express experience (max screen resolution is 1600×1200, less seamless keyboard/mouse interactions, etc).
Here's my clean Windows 7 VM running via the Hyper-V Virtual Machine Connection window: (click/tap to enlarge)
For comparison, I connected to this VM via Remote Desktop Connection on a display running WQHD screen resolution (2560×1440) which you can run across here: (click/tap to enlarge)
When using Remote Desktop with Hyper-5 the keyboard and mouse piece of work seamlessly just like they practise in whatever other Remote Desktop session. The simply downside is that yous don't have the VM land management controls in this view. If you lot're running RDP on the same Windows 8 auto as your Hyper-Five Manager, you tin can always switch over betwixt the Hyper-V Manger and the Remote Desktop session and accept the best of both worlds.
For fun, I found an old Windows 3.51 VHD file that was last modified in 2003 and created a VM in the Hyper-V director to run information technology. Remember the "stabbing fingers" blitheness at the log on screen? Good times…
There are many dissimilar ways to create VMs, and in this post I've illustrated how easy information technology is to get started with Hyper-V on Windows eight. At that place are a lot of powerful tools for managing Hyper-Five on Windows viii including the same PowerShell management capabilities that exist on Windows Server! If you want to know more than, please refer to the resource below.
Resources
- Client Hyper-V Overview on TechNet
- Windows PowerShell Support for Windows Server 2012 (applies to Client Hyper-V)
- Bringing Hyper-5 to Windows 8 (from the B8 Blog)
Yous can too stay up to date past following me on twitter here: @GavinGear
Source: https://blogs.windows.com/windowsexperience/2013/06/20/hyper-v-support-in-windows-8/
Posted by: beckerstroardlean.blogspot.com
0 Response to "How To Install Hyper V On Windows 8.1 Single Language"
Post a Comment