Windows 8 optimize

Create a test machine in Windows 8 Client Hyper-V

Greg Shultz shows you how to setup and configure Windows 8's Client Hyper-V.

In the article, Get the free 90-day evaluation of Windows 8 Enterprise, I showed you how to download and install the free 90-day evaluation copy of the final version of Windows 8 Enterprise so that you could begin experimenting with the new operating system. I recommended that you install Windows 8 Enterprise to a VHD and use it in a dual-boot configuration, as I showed you in the article titled Dual-boot Windows 7 and Windows 8 using a VHD. After experimenting with Windows 8 in a dual-boot configuration with Windows 7 for a while I decided that I wanted to expand my test bed a bit and rather than setting up another dual-boot system, I decided that I wanted to experiment with the operating system from within Windows 8's Client Hyper-V tool.

This post is also available as a slideshow in a TechRepublic Photo Gallery.

So, I installed the Windows 8 Enterprise evaluation on a system, set up the Client Hyper-V tool, created a virtual machine, and then installed the Windows 8 Enterprise evaluation on that virtual machine. This new setup is working great and has not only allowed me to expand my Windows 8 test bed; it has also allowed me to experiment with all the great features in Windows 8's Client Hyper-V. In this post I'll show you how to setup and configure Windows 8's Client Hyper-V. As I do, I'll show you how to install see your virtual machine in the Hyper-V Manager on that virtual machine. Along the way, I'll show you some of the neat features in Client Hyper-V.

About Client Hyper-V

As you may know, Microsoft has done away with Windows Virtual PC in favor of focusing on Hyper-V, which is also the main virtualization platform in Windows Server. Of course the server version of Hyper-V provides several advanced features that you won't find in the client version. Advanced features aside, the client version provides the same powerful and feature rich virtualization platform, along with an identical user interface and functionality as the server version. For instance, Windows 8's Client Hyper-V will allow you to simultaneously run multiple virtual machines and it can be used to run both 32- and 64-bit operating systems. Of course there is much more to Windows 8's Client Hyper-V than I will be able to cover in one article. But rest assured I will cover this topic in more detail in the future.

Requirements

Windows 8's Client Hyper-V is only available in the 64-bit versions of Windows 8 Pro and Windows 8 Enterprise and of course that means that it will only run on computers with 64-bit CPUs. And, these 64-bit CPUs must incorporate Second Level Address Translation (SLAT) technology. While most current CPUs from AMD and Intel support SLAT, you can verify your system by running the Coreinfo command-line utility from Microsoft's Windows Sysinternals site.

Your system must have at least 4GB of memory. However, if you want to be able to comfortably run more than one virtual machines at a time, you'll want more the 4GB.

Getting started

Windows 8's Client Hyper-V isn't enabled by default, but you can add it rather quickly from the Windows Features tool. To begin, just press the [Windows] key to bring up the Start Screen. Then, type Features, select Settings, and click Turn Windows features on or off, as illustrated in Figure A.

Figure A

Accessing Windows Feature tool from the Start Screen is easy.
When you see the Windows Features dialog box, locate and select the Hyper-V related check boxes and click OK. When you do, Windows 8 will enable the Hyper-V client and then prompt you to restart your system to complete the installation. These steps are illustrated in Figure B.

Figure B

When turning on Hyper-V it is best to enable all of the features.

As you can see, I have selected both the Hyper-V GUI Management Tools and the Hyper-V Module for Windows PowerShell. While the Hyper-V management console provides you with everything that you need to create, manage, and run virtual environments on your PC, having the PowerShell features available will allow you to experiment with scripting various Hyper-V features.

When you system restarts, you'll find two tiles on the Start Screen for Hyper-V, as shown in Figure C. The Hyper-V Virtual Machine Connection is a Remote Desktop-like tool that you will use to connect to your virtual machine after it is created and the Hyper-V Manager tile launches the management console that you'll use to create and manage your virtual machine.

Figure C

Hyper-V places two tiles on the Start Screen.

Creating a virtual network connection

While you can create a virtual machine without a virtual network connection and then add it later, you'll want to have it in place before create your first virtual machine. You'll use the Virtual Switch Manager to create and configure how you want the virtual network connection to work.

After you launch the Hyper-V Manager, navigate to the Actions pane and select the Virtual Switch Manager action, as shown in Figure D.

Figure D

You use the Virtual Switch Manager to create a virtual network connection.

The Virtual Switch Manager allows you to select several types of virtual switches: External, Internal, and Private. The one you choose will depend on how you want to use your virtual machine. If you want your virtual machine to be able to access resources available on your physical network, you'll select External. If you only want a connection between the host and the virtual machine, you'll select Internal. If you have more than one virtual machine running at one time and you only want a connection between your virtual machines, you select Private.

For the purposes of this example, I'll select External and click Next. You'll then be able to assign your virtual switch a name and select the network adapter. These two steps are illustrated in Figure E.

Figure E

The Virtual Switch Manager allows you to specify the way that your virtual machine will connect to the network.
When you click OK, you'll see the warning message shown in Figure F. The reason for this warning is that during the virtual network connection procedure, your network may temporarily go offline.

Figure F

During the virtual network connection procedure, your network may temporarily go offline.

Creating the virtual machine

Creating a virtual machine is easy; to begin, go back to the Actions pane in the Hyper-V Manger and select the New | Virtual Machine command, as shown in Figure G.

Figure G

In addition to creating a virtual machine, you can create virtual hard disk or a virtual floppy disk.
When the first screen of the New Virtual Machine Wizard appears, as shown in Figure H, you'll discover that you can quickly create a virtual machine using the preconfigured default settings or you can work through the wizard and create a custom configuration.

Figure H

You can create a custom virtual machine or select a preconfigured one.
If you want to use the preconfigured default virtual machine, just click Finish button. When you do you'll get a basic configuration with 512MB of RAM and no network connection. Of course you can modify the configuration from the Settings page. However, if you want to create a customized virtual machine, click Next. On the next two screens in the New Virtual Machine Wizard, you'll give your machine a name and specify the amount of RAM you want the virtual machine to have. These two screens are shown in Figure I.

Figure I

When you create a custom virtual machine, you'll start by naming the computer and specifying the amount of RAM.

As you can see, in addition to naming the system, you can specify different location to store the virtual machine files. For instance, you could store the virtual machine file on an external drive or on a file server. Dynamic Memory is a memory management system designed to utilize the available physical memory more efficiently when you are running more than one virtual machine at a time. For the purposes of this example, I won't enable or discuss Dynamic Memory in any more detail; however, you can learn more Microsoft's Overview page.

Moving ahead, you'll link your virtual machine to the virtual switch that you created and specify the virtual hard disk. These two steps are shown in Figure J.

Figure J

You'll connect your virtual machine to the virtual switch and specify the virtual hard disk.

As you can see, there are several options for specifying the virtual hard disk, you can create disk by giving it a name, specifying its location, and choosing its size. By default, the virtual hard disk has the same name as the virtual machine and is 127GB in size. If you have an existing virtual hard disk that you want to use for your virtual machine, you can connect it now or later.

On the Installation Options screen, shown in Figure K, you'll specify when and how you will install an operating system on the virtual machine. As you can see, I've selected to install the operating system from the DVD drive, but I could also choose to install from an ISO file, a bootable virtual floppy disk, or a network installation server. I can also choose to install the operating system later.

Figure K

There are several ways to install the operating system on your virtual machine.

At this point you can click Next to go to a Summary screen or you can just click Finish. When the Wizard closes, you'll see your virtual machine in the Hyper-V Manager.

Launching the installation

For my example, I choose to have the operating system installed from a DVD. So, after you insert the DVD in the drive, go back to the Actions pane in the Hyper-V Manager, scroll down to the virtual machine section and click the Connect command, as shown in Figure L.

Figure L

With your virtual machine selected in the Hyper-V Manager, choose the Connect command.
When you do, you'll see a virtual machine window that tells you that the machine is turned off. At this point, just click the Start button on the menu bar, as shown in Figure M.

Figure M

Click the Start button on the virtual machine window's toolbar.
In a moment, the virtual machine will boot off the DVD and begin the installation. Figure N shows the first screen in the Setup procedure of the Windows 8 Enterprise evaluation.

Figure N

The virtual machine will boot from the DVD and begin the installation procedure.

Once the installation was complete, I could begin experimenting with the Windows 8 Enterprise evaluation in my virtual machine.

What's your take?

Are you already familiar with Hyper-V? Are you planning on using Windows 8 Client Hyper-V? As always, if you have comments or information to share about this topic, please take a moment to drop by the TechRepublic Community Forums and let us hear from you.

Also read:

About

Greg Shultz is a freelance Technical Writer. Previously, he has worked as Documentation Specialist in the software industry, a Technical Support Specialist in educational industry, and a Technical Journalist in the computer publishing industry.

11 comments
bhimraju
bhimraju

Hello Greg, This is an excellent article. My question is can you add Hyper-V switch if you are running Windows 8 Enterprise desktop on a VMWare Workstation as a VM? Thanks Bhim

ron-beauchemin
ron-beauchemin

If you are using Windows Media Center under Windows 8 Professional you definitely will be interested in the following: I have Windows 7 installed in a dual-boot configuration on the same PC and Media Center works perfectly with by protected content and non-protected content. There is currently a conflict between having Hyper-V installed and Windows Media Center supporting HDCP. If Hyper-V is installed you get a message when running the Digital Cable Advisor tool during the Media Center installation and configuration indicating that your video card and/or drivers don't support content protection. I have spent over two weeks going back and forth with Microsoft support on this issue. They initially thought it was the Ceton InfiniTV card, then the ASUS VH236H monitor and finally that the AMD video drivers for my AMD Radeon HD7700 video card did not support HDCP. The were all red herrings. After a lot more digging my part I came across the following posting within the SuperUser forum. http://superuser.com/questions/487038/is-hdcp-working-for-ati-amd-cards-on-windows-8 Once I uninstalled Hyper-V, the Digital Cable Advisor within Media Center was happy and Media Center runs fine with both free and protected content. At this point I decided to see if the problem was just with the Digital Cable Advisor. Maybe once DCA put its entries for OCCURID in the registry everything would be fine? This was not the case. As soon a I reinstalled Hyper-V I received the message indicating that the system did not support protected content. Non-protected content played OK. This explains why the same exact drivers and hardware work fine under Windows 7 which does not come with Hyper-V. I just passed this finding on to Microsoft via email; last night and I am awaiting a response from Microsoft. I am hoping that this posting will save at least 1 person from going through the aggravation that I went through trying to get this issue resolved. My open Microsoft case # is SRX1187519987.

laman
laman

The whole procedure is pretty much the same as installing Hyper-V on Windows Server 2008 R2. I don't know why you need to write again.

GWK
GWK

I checked SLAT enabled on my machine using Coreinfo as advised - all OK. So started the tutorial and found Hyper-V Platform cannot be enabled on my machine - because SLAT is not possible on my machine. Why this discrepancy? Any thoughts? Presumably the above won't work without the platform enabled, so what's the alternative?

gak
gak

Currently neither VMware not VirtualBox can solve Windows 8 application compatibility problems for me. Possibly Hyper-V can, but as far as I know the main OS also runs under Hyper-V and that slows down 3D acceleration. Thus, placing Windows 8 into a VM looks like a better solution.

amj2010
amj2010

we have tested all versions so far except the RTM version...a lot of it is double....

lehnerus2000
lehnerus2000

Thanks for creating this easy to follow tutorial. :)

Mark W. Kaelin
Mark W. Kaelin

Are you taking advantage of Hyper-V in your organization?

Greg Shultz
Greg Shultz

...but can't answer until I've had a chance to experiment with that particular setup. Sounds like you are though, so go ahead and give it a shot and see how/if it works. Let us know the outcome.

XebraTech
XebraTech

Well, it helped me and I didn't have to go chasing and looking. Time saver.

Greg Shultz
Greg Shultz

...it is easy to misinterpret the output. If your CPU does support SLAT you will see an asterisk * next to EPT field: EPT * Supports Intel extended page tables (SLAT) If your CPU doesn't support SLAT you will see an minus sign - next to EPT field: EPT - Supports Intel extended page tables (SLAT) If you don't pay attention to the presence of the asterisk or minus sign, and just focus in on the wording "Supports Intel extended page tables (SLAT)" you would misinterpret the reading. Please run Coreinfo again and I'll bet that you see a minus sign next to EPT field.