Nested Virtualization is not a new idea. In fact, we announced our first preview of Nested Virtualization running on Windows way back in 2015. From that Windows Insider preview to now, Nested...
Updated Jun 12, 2020
Version 2.0
Blog Post
proboszcz Thanks for the information, I have set up a double boot with native vhd boot and an Insider track installed on VHD + my C drive as my main OS.
I have found that after using it a few times to test it out, it works OK, but is far far from ideal. I feel separated from my Main OS when I am in a Dual Boot environment.
It is a bit disingenuous to state that you are not switching your main rig over, Right?
I mean, it does keep your "Main OS" Intact, but otherwise, it's a complete change that introduces additional problems.
- what about all your files, your settings, everything being remapped to D:, all your program install's, and an ever-expanding VHD taking up all your precious space on your SSD?
- And dual-booting between OS's means you will never be able to pick up where you just left off?
- Problems with hibernate/suspend/resume?
- Permissions HELL where there are unknown users with permissions in either OS?
- Windows Insiders cannot be updated inside a VHD Boot. For some unknown reason.
- One needs to hack with Hyperv VM on the Main OS side, boot up the Hyper-V VHD in a VM on the Main OS Side, to update.
- This introduces activation and Licence Hell, as windows belives the hardware has changed.
- And on... and on... and on... lots of niggly issues with this approach.
- It really is not an ideal solution.
Amateur Opinion time:
In My Very amateur and humble opinion, my understanding is the following:
Hyper-V is a HyperVisor that sits UNDER Windows 10. Windows 10 isn't even aware of it. The Hyper-V management tools such as Hyper-V manager connect to the underlying hypervisor via a socket on the localhost network interface port.
Windows has nothing to do with this Hypervisor management. Hyper-V is its own things that sits underneath.
Again, I am by no means a super expert on these things, but I just can't see why I cannot only update the Hyper-V underneath without moving to an insider build. Even the management tools do not need an update, as nested virtualisation & the VM Version is managed over flags and commands inside PowerShell.
Why can't I JUST update the Hyper-V???
Manually, separately, like I do with the WSL2 Linux Kernel?
Can anyone explain?
Thanks very much.