Client Hyper-V is the same virtualization technology previously available in Windows Server operating system. Unlike in earlier client operating systems, the technology is now built into Windows 8.
Hyper- V is currently selling like a hot cake across the world and itâ€™s nothing like rocket science to understand and configure Client Hyper-V too. IT Pros and developers can use this technology to create virtual Machines (VM) and can move them from Client Hyper-V to server Hyper-V.
To Enable using GUI:
On the Control Panel click â€œProgramsâ€, and then click â€œPrograms and Featuresâ€
Click â€œTurn Windows features on or offâ€
Click â€œHyper-Vâ€, and then click â€œOKâ€, and then click â€œCloseâ€
Machine must be restarted to complete installation.
There a few features included in Windows Server 2012 Hyper-V that are not included in Client Hyper-V like the remote FX, Live VM migration, Hyper-V Replica, etc.
Note that Hyper-V requires a 64-bit system that has Second Level Address Translation (SLAT). Atleast 4 GB RAM is required. The RAM on your Client Hyper-V machine is allocated and de-allocated dynamically as required by the VMs. We can run several VMs on a Client Hyper-V machine depending on the RAM requirements for each VM.
Client Hyper-V supports server Hyper-Vâ€™s â€œLive Storage Moveâ€ capability. This means we can use our host VMs keeping it independent of the underlying storage. We can move VMs to and from one local drive to another, to a USB stick, or to a remote file share without needing to stop the VM.