Private virtual networks are used where you want to allow communications between
In order of most permissive to least permissive, this is why you would want to chose one type of Virtual Switch over the other:Įxternal virtual networks are used where you want to allow communications between
If you need to be able to do these, you might want to consider the free Hyper-V Server product, or Windows Server 2012 R2.įor additional information on the full feature set of Hyper-V, click here.Ĭlient Hyper-V is only available in the following versions of Windows:įor this demonstration though, we'll concentrate on the Windows 8.1 versions, as it is a free upgrade from Windows 8, and that's the version most users will likely be using.įrom the Virtual Switch Manager, create a new virtual switch by choosing External, Internal, or Private, and then clicking on "Create Virtual Switch", and then "OK". Cannot do Live migration of virtual machines from one host to another.Does not have Remote FX capability to virtualize GPUs.If you're a software developer and need to do testing, or simply want additional operating system(s) running on your computer, such as Linux, Hyper-V can be a great feature to have enabled on your PC.Ĭlient Hyper-V has remarkably few limitations compared to its Server sibling. The virtual machines you create on your desktop with Client Hyper-V are fully compatible with those server systems as well. This is the very same Type-1 hypervisor that runs virtualized enterprise workloads and comes with Microsoft Windows Server 2012 R2.
Many Windows users aren't aware of it, but a powerful virtualization tool is built into every copy of Microsoft Windows 8.x Pro and Windows 8.x Enterprise, Client Hyper-V.