Yet another Hyper-V feature that you can't get in Windows 10 is Discrete Device Assignments. Virtual Fibre Channel allows a VM to use a physical host bus adapter to connect to Fibre Channel storage. That way, if the primary host fails, a VM copy can be activated on one of the replica hosts.Īnother feature that exists in Windows Server Hyper-V but not in its Windows 10 counterpart is virtual Fibre Channel.

If you are not familiar with the replication feature, it allows individual VMs - and individual virtual hard disks associated with a VM - to be asynchronously synchronized to one or two other Hyper-V hosts. Similarly, Windows Server supports the Hyper-V Replica feature, which is not available on Windows 10. Technically, failover clustering is not a Hyper-V feature, but high-availability is a key capability for any production environment. One of the most important differences is that Windows Server supports failover clustering and high-availability for virtual machines (VMs), while Windows 10 does not. Conversely, Windows Server Hyper-V is suited to hosting production workloads.īecause the two platforms are designed for completely different purposes, they also have differing feature sets and licensing considerations. The short answer is that Windows 10 Hyper-V is primarily intended to be used as a development platform, or by users who need to run applications that do not work on Windows 10 (such as a Linux application). Someone recently asked me if there are any real differences between Windows 10 Hyper-V and Windows Server Hyper-V.

Run a vm on windows 10