Windows Failover Cluster with Hyper-V nested

%3CLINGO-SUB%20id%3D%22lingo-sub-1071312%22%20slang%3D%22en-US%22%3EWindows%20Failover%20Cluster%20with%20Hyper-V%20nested%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1071312%22%20slang%3D%22en-US%22%3E%3CP%3EIs%20it%20okay%20to%20build%20a%20Windows%20Failover%20Cluster%20with%20Hyper-V%20nested%3F%3C%2FP%3E%3CP%3EPlease%20let%20me%20know%20if%20there%20are%20restrictions%20on%20Windows.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1071312%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EClustering%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EHyper-V%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1071539%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%20Failover%20Cluster%20with%20Hyper-V%20nested%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1071539%22%20slang%3D%22en-US%22%3E%3CP%3EYou%20can%20use%20nested%20virtualization%20on%20a%20Hyper-V%20failover%20cluster.%3C%2FP%3E%3CP%3EYou%20need%20the%20following%20system%20requirements%20on%20your%20physical%20hosts%3A%3C%2FP%3E%3CUL%3E%3CLI%3EWindows%20Server%202016%20or%20higher%3C%2FLI%3E%3CLI%3EIntel%20Processor%20with%20VT-x%20and%20EPT%3C%2FLI%3E%3C%2FUL%3E%3CP%3EYou%20also%20need%20to%20take%20special%20care%20for%20virtual%20machine%20networking.%20You%20have%20to%20enable%20MAC%20Address%20Spoofing%20for%20your%20virtual%20Hyper-V%20hosts.%20Also%20you%20lose%20any%20online%20memory%20resizing%20inside%20a%20VM%20with%20enabled%20nested%20virtualization.%20Meaning%20you%20can't%20use%20dynamic%20memory%20or%20hot-add%2Fremove%20memory%20with%20nested%20virtualization.%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F483700%22%20target%3D%22_blank%22%3E%40Akira_Kato%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1071581%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%20Failover%20Cluster%20with%20Hyper-V%20nested%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1071581%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F261242%22%20target%3D%22_blank%22%3E%40dretzer%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThank%20you%20for%20answering.%3C%2FP%3E%3CP%3EDoes%20it%20mean%20that%20it%20can%20be%20built%20with%20some%20restrictions%3F%3CBR%20%2F%3EIs%20it%20not%20recommended%20for%20MS%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Occasional Contributor

Is it okay to build a Windows Failover Cluster with Hyper-V nested?

Please let me know if there are restrictions on Windows.

2 Replies
Highlighted

You can use nested virtualization on a Hyper-V failover cluster.

You need the following system requirements on your physical hosts:

  • Windows Server 2016 or higher
  • Intel Processor with VT-x and EPT

You also need to take special care for virtual machine networking. You have to enable MAC Address Spoofing for your virtual Hyper-V hosts. Also you lose any online memory resizing inside a VM with enabled nested virtualization. Meaning you can't use dynamic memory or hot-add/remove memory with nested virtualization.

@Akira_Kato 

Highlighted

@dretzer 

 

Thank you for answering.

Does it mean that it can be built with some restrictions?
Is it not recommended for MS?