Publicada: febrero de 2012
Actualizado: abril de 2012
Se aplica a: Windows 8
This overview explains the hardware requirements, usage scenarios, and installation procedures for Client Hyper-V. Client Hyper-V is the name for the Hyper-V technology available in Windows® 8 Pro. For more information about Client Hyper-V, see Bringing Hyper-V to Windows 8.
Did you mean…
Hyper-V in Windows Server® 2012? See What's New in Hyper-V.
Microsoft Hyper-V Server “8” Beta or Microsoft Hyper-V Server 2008 R2 (stand-alone products)? See What's New in Microsoft Hyper-V Server "8" Beta and Download Microsoft Hyper-V Server 2008 R2 with Service Pack 1 (SP1).
Windows Server 2012? Go to the download.
Windows XP Mode with Virtual PC in Windows 7? Go to the download.
Microsoft Enterprise Desktop Virtualization (MED-V) 2.0 and Microsoft Application Virtualization (App-V) 4.6 SP1? See Agility and compatibility with Microsoft App-V and MED-V.
Client Hyper-V is the same computer virtualization technology that was previously available in Windows Server. In Windows 8 Pro, the technology is now built into the non-server version of Windows, often called the “desktop” version because it does not run on server-class hardware. Client Hyper-V provides the same virtualization capabilities as Hyper-V in Windows Server 2012. A similar functionality in Windows 7 is called Windows XP Mode. To download this feature, see Download Windows XP Mode with Virtual PC.
For more information, see this video: Developing and testing on Windows 8 with Hyper-V.
To understand the architecture of Hyper-V, see the Windows Server 2008 R2: Hyper-V Component Architecture poster.
Because Client Hyper-V is the same technology as in Windows Server 2012, IT pros and developers do not need to learn any new tools or commands. You can move virtual machines from Client Hyper-V to Hyper-V in Windows Server 2012. For example, you can build a “test lab” infrastructure hosted entirely on your laptop or desktop computer, and export the virtual machines you create and test from your laptop into production. As another example, assume you have an application that you must test on the Windows 8 Consumer Preview, Windows 7, and Windows XP operating systems. You can create three virtual machines with these operating systems versions easily and complete your tests (except for scale/performance tests) on the computer running Client Hyper-V, instead of on the production computer or in a dedicated testing lab. You can also use virtual hard disks (VHDs) that are readily available, such as the Datacenter Virtualization & Management Try It .vhd files (available for free).
With Client Hyper-V, you can use Hyper-V virtualization with both wireless network adapters and sleep states on your desktop computer. For example, if you are running Client Hyper-V on a laptop and close the lid, the virtual machines that are running will be put into a saved state, and resumed when the machine wakes. Virtual machine management and other tools created for Hyper-V in Windows Server, such as VMM P2V or Sysinternals DisktoVHD tools, will also work in Client Hyper-V. To download this utility, see Disk2vhd v1.63. Hyper-V virtual switch extensions and Windows PowerShell scripts for managing virtual machines that you develop and test on Client Hyper-V can be moved to Hyper-V in Windows Server 2012. You can also export a virtual machine from your production environment, open it on your desktop with Client Hyper-V, perform your required troubleshooting, and then export it back into the production environment. Using virtual machine networking, you can create a multi-machine environment for test/development/demonstration that is secure from affecting the production network. You can also mount and boot a Windows operating system using Windows to Go VHDs from a USB storage drive as a virtual machine using Client Hyper-V.
Windows PowerShell scripts for managing virtual machines that you create using Client Hyper-V are fully compatible with Hyper-V in Windows Server 2012. For example, assuming you had the .xml files for these virtual machines already available on your computer, network share, or USB storage, the following example Windows PowerShell command would start them all for you on your computer with Client Hyper-V.
Dir *.xml | import-vm | start-vm
For more information about Hyper-V Windows PowerShell commands, see Windows PowerShell Support for Windows Server "8" Beta.
There are some features included in Hyper-V in Windows Server 2012 that are not included in Client Hyper-V. These include the following: the remote FX capability to virtualize GPUs (software GPU in RDP 8), live migration of virtual machines, Hyper-V Replica, SR-IOV networking, and virtual Fibre Channel. For more information, see What's New in Hyper-V.
Hyper-V requires a 64-bit system that has Second Level Address Translation (SLAT). For information about checking and changing the virtualization support settings of your system BIOS, consult your system manufacturer.
Hyper-V supports the creation of both 32-bit and 64-bit operating systems in virtual machines.
|You must license each of the virtual machine operating systems according to their requirements.|
4 GB of RAM is required. The RAM on your computer running Client Hyper-V is allocated and deallocated dynamically as required by the virtual machines. You can run several virtual machines on a computer running Client Hyper-V (also called a “host”) that has the minimum 4 GB of RAM, but you will need additional RAM for 5 or more virtual machines, depending on the RAM requirements for each virtual machine.
Client Hyper-V supports the same storage migration capability that is included in Hyper-V in Windows Server 2012. This means you can have your virtual machines fairly independent of the underlying storage. You can move a virtual machine’s storage to and from one local drive to another, to a USB drive, or to a remote file share without needing to stop the virtual machine.
To use Client Hyper-V, you must first enable the feature.
|Because Hyper-V is an optional feature in Windows 8 Pro, the files required for installation may or may not be present on your computer, depending on your organization’s IT policy. If you are connected to the Internet, enabling the feature will automatically download the required files. If you are not connected to the Internet, you can download the required files and manually copy them to your computer, or otherwise provide the installation media.|
On the Control Panel, click Programs, and then click Programs and Features.
Click Turn Windows features on or off.
Click Hyper-V, click OK, and then click Close.
On the Windows PowerShell command line, type the following:
Enable-WindowsOptionalFeature –FeatureName Microsoft-Hyper-V -All
|You must restart your computer (not just reboot) to complete installation. Depending on your manufacturer, you may have to pause a few seconds with the computer off before restarting for the required changes to take effect. If you are using a laptop, you may have to remove the battery before restarting. After restarting the computer, you can use Hyper-V Manager or Windows PowerShell to create and manage virtual machines. You can also use Virtual Machine Connection to connect to virtual machines remotely. For more information about configuring Hyper-V, see Install the Hyper-V role and Configure a Virtual Machine. For a library of Windows PowerShell cmdlets for virtual machine management, see Hyper-V Module for Windows PowerShell.|
Turning on the Hyper-V feature in Windows 8 also installs Hyper-V Manager. You can use Hyper-V Manager to create and manage your virtual machines.
For more information about Hyper-V Manager, see User Interface: Hyper-V Manager.