This post is also available in: Italian

Reading Time: 2 minutes

Until now Microsoft simple does not support nested virtualization in its Hyper-V product. Nothing wrong with it, but it’s a case where not supported means also that it simple does not work at all.

So the only way to test Hyper-V (or other hypervisor) in a lab with a single physical system (server or client) was using other hypervisors (VMware ESXi, Workstation, or also Paralles or others). Or using this trick (useful also with the new hardware requirement of the next Hyper-V) but with the big limit where the VMs cannot be powered on at all.

Now with the next Windows Server release (Windows Server 2016) there will be some changes. According to a Build Conference session (Windows Containers: What, Why and How), seems that Hyper-V Windows Server 2016 will support nested Virtualization.

What seems sure is that the Microsoft Hyper-V based containers will require a nested Hyper-V.

Docker-ClientSo seems reasonable that nested Hyper-V will be possible in the next product. This does not necessary that also other hypervisors could be nested in Hyper-V (or that they will be supported).

And it’s still not clear if also the Windows 10 Hyper-V will support this feature. Considering that nested hypervisors are more interesting in lab and testing could be really nice have also on the client Hyper-V!

See also: Hyper-V vNext is going to support nested Virtualization.


Virtualization, Cloud and Storage Architect. Tech Field delegate. VMUG IT Co-Founder and board member. VMware VMTN Moderator and vExpert 2010-20 and vExpert Pro. Dell TechCenter Rockstar 2014-15. Microsoft MVP 2014-16. Veeam Vanguard 2015-19. Nutanix NTC 2014-20. Several certifications including: VCDX-DCV, VCP-DCV/DT/Cloud, VCAP-DCA/DCD/CIA/CID/DTA/DTD, MCSA, MCSE, MCITP, CCA, NPP.