How To Install Hyper V On Windows 8.1 Single Language
Virtual Machines (VMs) are swell for a wide variety of tasks including running different operating systems or software configurations on a single machine. Windows eight is the beginning Windows client operating system to include hardware virtualization support without the need for separate downloads or installs. This feature in Windows 8 is called Client Hyper-V. Client Hyper-Five is the same engineering science as used in Windows Server 2022 Hyper-V, so you tin movement VMs from server to client, and won't need to re-learn how to use Hyper-5 features and tools.
In this commodity I'll give a loftier-level overview of Client Hyper-V in Windows 8 and too guide you through the procedure of configuring Hyper-Five and creating/running VMs.
What Y'all'll Demand to Run Hyper-Five on Windows 8
In order to run Client Hyper-Five on Windows 8 you lot'll need the following:
- Windows 8 Pro or Enterprise 64 bit Operating System
- 64 chip processor with Second Level Address Translation (SLAT)
- BIOS-level Hardware Virtualization support
- At least 4GB organisation ram
If you are running 64-bit Windows eight and meet the hardware requirements listed higher up you're equipped to requite Client Hyper-V a try!
Setting Up Hyper-V
The beginning matter to do when getting ready to run Client Hyper-V is to make sure that hardware virtualization back up is turned on in the BIOS settings. For my demonstration in this article I configured my HP Z820 desktop system to run Customer Hyper-V. Below is a picture of the BIOS settings I configured on my HP Z820:
One time you take confirmed that hardware virtualization support is bachelor and enabled, it'south fourth dimension to enable Hyper-V in the "Plow Windows features on or off" dialog which you tin launch past typing "turn windows features" at the Outset Screen and so selecting "Settings" in the right-paw pane.
Hyper-V Enabled in Windows Features
If Hyper-V wasn't enabled previously, you'll need to reboot after applying this change. After enabling Hyper-V it's a good thought to configure networking for the Hyper-5 environs. In order to support external network connections, you'll need to make sure that a virtual switch has been created and is functional. To become started with this, open the Virtual Switch Manager which you'll find on the Actions panel in the Hyper-V Director (Blazon Hyper-V at the Offset Screen to find the Hyper-5 Managing director).
After clicking on "Virtual Switch Director" in the Actions pane ensure that "External" is highlighted, then click on the "Create Virtual Switch" button.
If you have more than ane NIC in your arrangement, ensure that y'all accept 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 can configure, this is a good starting signal and is all I needed to do to commencement creating and using VMs on Window 8 Pro.
Creating VMs
Since Client Hyper-V is fully compatible with Hyper-V on Windows Server you can use VMs and Vitual Hard Drives (VHDs) created on Windows Server Hyper-V machines. Creating a new VM it's like shooting fish in a barrel. In this section I'll outline the procedure to create a VM from scratch using PXE boot from the network. You tin also very easily perform Os installs from USB drives or optical media similar DVDs.
To create a VM you just click on "New Virtual Motorcar…" under "Actions" on the right panel in the Hyper-V Manager. When y'all do this, the "New Virtual Machine Magician" volition launch. The first task is to choose a VM name and optionally specify a path for the VM file:
Next, y'all'll decide how much retention to allocate. I chose to use the default of 512 MB to see how my VM would perform with default memory settings. I know that I tin always change this later.
After that you'll need to select a virtual switch if networking is needed. In this case I chose the virtual switch that I created in the earlier steps outlined in this post.
The side by side step is to setup the VHD for the VM being created. Hither you have the option to create a new VHD, use an existing VHD, or to postpone VHD configuration for later:
I chose to take a VHD created using the default settings. Notation that you want to recollect about where the VHD file is stored during this process. I like to keep VM files and VHD files in the same directory for virtually configurations.
Later on clicking "End" I had ane important step that'due south required to enable PXE boot from VMs. in This terminal step was to create a Legacy Network Adapter in VM settings. To do this, yous launch the settings dialog for the VM that needs network boot support, and so click "Add Hardware" which is the peak detail in the left pane.
All you need to exercise is click the "Add" push and then ensure that the proper virtual switch is used. That's information technology! It only takes a couple minutes to perform all of these steps one time you know what to exercise. This VM was now ready for PXE boot and the installation of the OS.
After clicking the green "Start" button for your VM in the right pane of the Hyper-Five Manager, yous'll then see the familiar PXE boot menu where yous can press F-12 for a network kicking:
This works simply similar network booting from a physical machine. I used network boot to kicking off a clean Windows vii install as you tin can see here:
Having VMs for different operating systems is great when you lot need to test software on dissimilar operating systems, run motorcar images that are isolated from the network, test upgrade scenarios, and many more activities. Just remember to relieve snapshots for key configurations then that you lot can revert machine state when needed.
Connecting to VMs on Windows 8
Once yous accept your VMs setup at that place are two great options for interacting with and connecting to your VMs: the Hyper-V Manager, or Remote Desktop Connection using Remote Desktop Protocol (RDP).
Using the Hyper-Five manager y'all'll be able to control your VM state in the Virtual Machine Connection Window but you lot'll have a more limited experience (max screen resolution is 1600×1200, less seamless keyboard/mouse interactions, etc).
Here's my clean Windows seven VM running via the Hyper-Five Virtual Machine Connection window: (click/tap to overstate)
For comparison, I continued to this VM via Remote Desktop Connexion on a display running WQHD screen resolution (2560×1440) which you can meet here: (click/tap to enlarge)
When using Remote Desktop with Hyper-V the keyboard and mouse piece of work seamlessly merely similar they do in whatever other Remote Desktop session. The only downside is that you don't have the VM state management controls in this view. If you lot're running RDP on the aforementioned Windows eight automobile as your Hyper-V Manager, yous can always switch over between the Hyper-5 Manger and the Remote Desktop session and have 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 managing director to run it. Remember the "stabbing fingers" animation at the log on screen? Good times…
In that location are many different ways to create VMs, and in this mail I've illustrated how piece of cake it is to get started with Hyper-Five on Windows 8. There are a lot of powerful tools for managing Hyper-5 on Windows 8 including the same PowerShell direction capabilities that exist on Windows Server! If you want to know more, please refer to the resources below.
Resources
- Customer Hyper-5 Overview on TechNet
- Windows PowerShell Support for Windows Server 2022 (applies to Client Hyper-Five)
- Bringing Hyper-V to Windows 8 (from the B8 Blog)
You lot can also stay up to date by following me on twitter here: @GavinGear
Source: https://blogs.windows.com/windowsexperience/2013/06/20/hyper-v-support-in-windows-8/
Posted by: harbinforrounce.blogspot.com
0 Response to "How To Install Hyper V On Windows 8.1 Single Language"
Post a Comment