Published On: Thu, Sep 28th, 2017

Google Compute Engine now lets we play nesting dolls with your VMs

Here is a cloud computing underline that might seem a bit peculiar during initial yet that does indeed have a uses. Google’s Compute Engine now launched a beta of a new underline called “nested virtualization.” As a name implies, this radically allows we to run VMs inside of VMs.

But because would we wish to do that? “Nested virtualization creates it easier for craving users to pierce their on-premises, virtualized workloads to a cloud but carrying to import and modify VM images,” Compute Engine product manager Scott Van Woudenberg writes in today’s announcement. “Dev/test and CI/CD workloads that need to countenance program in mixed environments are a good compare for nested virtualization.”

He also argues that this is a useful underline for building cheaper cloud-based disaster liberation solutions and that it’ll be useful for companies that wish to set adult practical environments for training and certification, where we wish to make certain that everybody gets a same sourroundings to work from.

This new underline is accessible for probably any form of Compute Engine VM, including preemptible VMs. The usually requirement is that a VM has to run on an Intel Haswell or newer CPU.

The approach this works most is that we set adult a unchanging VM and afterwards implement a KVM-compatible hypervisor on that instance. Google records that it doesn’t now support non-KVM hypervisors like Xen, ESX and Microsoft’s Hyper-V. This usually works for Linux instances, though. Nested virtualization isn’t accessible for Windows machines.

It’s value observant that Microsoft Azure already upheld nested virtualization (using a Hyper-V hypervisor). On AWS, developers can use collection like Oracle’s Ravello nested hypervisor to grasp a same capabilities.

Featured Image: Cube/Getty Images

About the Author

Leave a comment

XHTML: You can use these html tags: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>