Trabajo De Toluca

Using Windows 8 Client Hyper-V

Provided by

Work Smart

Contents

Topics in this guide include:

Practical applications for Client Hyper-V

Hardware requirements

Enabling Client Hyper-V

Tools

What isn’t included in Client Hyper-V?

For more information

Client Hyper-V® is the virtualization technology built into Windows® 8. Client Hyper-V is the same virtualization technology previously available only in Windows Server®. A similar functionality in Windows 7 is called Windows XP Mode.

Client Hyper-V enables you to run more than one 32-bit or 64-bit x86 operating system at the same time on the same host computer. But instead of working directly with the computer’s hardware, the operating systems run inside a virtual machine (VM).

Hyper-V enables developers and IT professionals to easily maintain multiple test environments and provides a simple mechanism to quickly switch between these environments.

Practical applications for Client Hyper-V

As a developer or IT professional, consider using Client Hyper-V for any of the following scenarios:

• Build a test lab infrastructure on your desktop or laptop. After creating virtual machines and testing them on the desktop or laptop, move the VMs to a Windows Server production environment.

• Test an application with different operating systems. For example, you might have an application that you need to test in Windows 8, Windows 7, and Windows XP. You can create three VMs with these OS versions on your desktop or laptop. You then can run your tests (except for scale/performance tests) on the Client Hyper-V computer instead of in a production environment or dedicated testing lab.

• Export, or simply copy, a VM from your production environment, import it to your desktop or laptop with Client Hyper-V (you’ll need to adjust settings), and do the required troubleshooting. Then export the VM (with adjustments) back to the production environment.

• Using VM networking, create a multi-computer environment for test/development/demonstration that doesn’t affect the production network.

• Take a snapshot of a virtual machine while it is running. A snapshot saves everything about the virtual machine, enabling you to go back to a previous point in time in the life of a VM. This is a great tool when you are trying to debug tricky problems.

• Mount and boot a Windows operating system using Windows To Go Virtual Hard Disks (VHDs) from a USB drive as a virtual machine.

Interaction with Windows Update

A computer running Client Hyper-V can take advantage of Windows Update, so you don’t need to set up additional maintenance processes.

Wireless network adapters and sleep states

Client Hyper-V works with wireless network adapters and is compatible with sleep states. For example, if you are running Client Hyper-V on a laptop and you close the lid, the VMs that are running will be put into a saved state. The VMs can be resumed when the computer wakes.  

Hardware requirements

Hyper-V supports creation of both 32-bit and 64-bit operating systems in VMs. To be the Client Hyper-V host system, your computer must:

• Be running a 64-bit version of Windows 8 Professional or Enterprise Editions.

• Have a CPU that supports Second Level Address Translation (SLAT), a feature present in the current generation of 64-bit processors by Intel and AMD. To determine if a CPU supports SLAT, go to http://social.technet.microsoft.com/wiki/contents/

articles/1401.aspx.

• Microsoft IT recommends testing of the CPU for NX and SSE2. You can use the Sysinternals COREINFO tool to test for both. For more information, go to http://technet.microsoft.com/en-us/sysinternals/cc835722. Because BIOS support for virtualization is required, before you enable Client Hyper-V, ensure that your computer has the latest BIOS version. For information on checking and changing the virtualization support settings of your system BIOS, check with your computer manufacturer. Visit http://social.technet.microsoft.com/wiki/contents/

articles/3190.aspx.

• Have 4 gigabytes (GB) of RAM. Hyper-V’s dynamic memory allows memory needed by the VM to be allocated and de-allocated dynamically (you specify a minimum and maximum), and it shares unused memory between VMs. You can run a few VMs on a computer that has 4 GB of RAM. The number of VMs that you can run will depend on the RAM size and required performance. At the upper end of the spectrum, you can create large VMs with 32 processors and 512 GB RAM (maximum RAM per VM).

For storage, you can add multiple hard disks to the IDE or SCSI controllers available in the VM. You can use Virtual Hard Disks (.VHD or .VHDX files) or actual disks that you pass directly through to the virtual machine. VHDs can also reside on a remote file serve. That makes it easy to maintain and share a common set of predefined VHDs across a team.

Hyper-V’s “Live Storage Move” capability helps your VMs to be fairly independent of the underlying storage. With Live Storage Move, you can move the VM’s storage from one local drive to another, to an USB drive, or to a remote file share without needing to stop your VM. This is very handy for fast deployments if you need a VM quickly. You can start a VM from a VM library maintained on a file share, and then move the VM’s storage to your local drive.

Enabling Client Hyper-V

You can enable Client Hyper-V in Windows 8 in three ways.

Use the Control Panel

1. In the Windows 8 Control Panel, tap or click Programs, and then tap or click Programs and Features.

2. Tap or click Turn

...