> For the complete documentation index, see [llms.txt](https://kenvb.gitbook.io/hyper-converged-solution-in-windows-server/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kenvb.gitbook.io/hyper-converged-solution-in-windows-server/setup-hyper-v-and-test/create-a-high-available-vm.md).

# Create a High Available VM

Via the Cluster configuration manager, you can create a high available VM. After selecting a node, everything proceeds as you would normally configure a VM, only now it's immediatly High Available.

I'm not sure myself what caused this option to appear. Is it the cluster manager detecting the Hyper-V services on the nodes?

![](https://3108435343-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-Lp2rB1gAFhoLXwsXIIR%2F-Lp2rDugz51IbJxnu7OE%2F-Lp2s84RZ01XImqLNe_X%2FNew-HA-VM.PNG?generation=1568801858449107\&alt=media)

I'm installing a Generation 1, Windows 7 machine of which the iso is already copied to the clustered volume. After which you get a "VM-ception": Windows 7-VM on a Server 2016-VM on a Windows 10 host.

![](https://3108435343-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-Lp2rB1gAFhoLXwsXIIR%2F-Lp2rDugz51IbJxnu7OE%2F-Lp2s84TXIJmBqTsY45j%2FVM-ception.PNG?generation=1568801858480216\&alt=media)