Oh no, you're thinking, yet another cookie pop-up. Well, sorry, it's the law. We measure how many people read us, and ensure you see relevant ads, by storing cookies on your device. If you're cool with that, hit “Accept all Cookies”. For more info and to customize your settings, hit “Customize Settings”.

Review and manage your consent

Here's an overview of our use of cookies, similar technologies and how to manage them. You can also change your choices at any time, by hitting the “Your Consent Options” link on the site's footer.

Manage Cookie Preferences
  • These cookies are strictly necessary so that you can navigate the site as normal and use all features. Without these cookies we cannot provide you with the service that you expect.

  • These cookies are used to make advertising messages more relevant to you. They perform functions like preventing the same ad from continuously reappearing, ensuring that ads are properly displayed for advertisers, and in some cases selecting advertisements that are based on your interests.

  • These cookies collect information in aggregate form to help us understand how our websites are being used. They allow us to count visits and traffic sources so that we can measure and improve the performance of our sites. If people say no to these cookies, we do not know how many people have visited and we cannot monitor performance.

See also our Cookie policy and Privacy policy.

This article is more than 1 year old

Microsoft offers sneak peak of Hyper-V containers with Win 10 nested virtualisation

If you find Leonardo Di Caprio down there in a nested VM, please let us know

Microsoft has added nested virtualisation to Windows 10 as a prelude to revealing its Hyper-V Containers technology.

As we've previously explored, Hyper-V containers will be deployable by Docker. The technology will sit alongside Windows Server Containers, which will offer a more Microsoft-centric containerisation approach. Microsoft's desktop hypervisor, Client Hyper-V, appeared in business-oriented versions of Windows 8 and is a downloadable add-on for Windows 10. Redmond offers Client Hyper-V for developers, who appreciate being able to run different OSes in one machine, and for businesses that need to give users access to oddities without also giving them two computers.

But Client Hyper-V is only good for virtualising one layer deep: you can't run guests inside guests.

Nested virtualisation allows that trick.

Microsoft needs to make nested virtualisation possible because Hyper-V containers need to run inside Hyper-V.

The trick here is to make sure guests can “see” the Intel VT-x and AMD-V virtualisation extensions that the companies' CPUs offer guests to help speed VM operations. By doing so in Windows 10, Microsoft makes it possible for developers to spin up the many Hyper-V containers it is expected containerised apps will require.

Build 10565 of Windows 10 offers the new functionality, which is billed as a preview fit only for footling thanks to the presence of many known issues.

Nested virtualisation is sometimes called “virtuception” in homage to dream-within-a-dream flick Inception. If you put this new tech to the test and find the film's star Leonardo Di Caprio down there, please let us know. ®

 

Similar topics

TIP US OFF

Send us news


Other stories you might like