Client Hyper-V in Windows 8
Windows PowerShell scripts for managing virtual machines that you create using Client Hyper-V are fully compatible in with Windows Server 8 Hyper-V.
There a few features included in Windows Server 8 Hyper-V that are not included in Client Hyper-V. These include: the remote FX capability to virtualize GPUs (software GPU in RDP 8), Live VM migration, Hyper-V Replica, SR-IOV networking, and synthetic fiber channel.
HARDWARE : Hyper-V requires a 64-bit system that has Second Level Address Translation (SLAT). GB RAM is required. The RAM on your Client Hyper-V machine is allocated and de-allocated dynamically as required by the VMs. You can run several VMs on a Client Hyper-V machine (also called a “host”) that has the minimum 4GB of RAM, but you will need additional RAM for 5 or more VMs, depending on the RAM requirements for each VM.
Client Hyper-V supports server Hyper-V’s “Live Storage Move” capability. This means you can use your VMs fairly independent of the underlying storage. You 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.
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”
Enable-WindowsOptionalFeature –FeatureName Microsoft-Hyper-V -Restart
Important :
You must restart your machine, not just reboot, to complete installation
For more info: Windows 8 Client Hyper-V wiki page (FWLINK) (http://social.technet.microsoft.com/wiki/contents/articles/7704.client-hyper-v-survival-guide.aspx)
What hardware do you suggest for a setup that would use 3 VMs at the same time? Core i3, i5, or i7? Is 6 GB RAM enough?
Hi, It all depends on the workloads that you plan to run. I currently use an i7 with 8Gb and I am running 6 VM’s