Here is a cloud computing characteristic that can appear a bit of ordinary to start with however that does in truth have its makes use of. Google’s Compute Engine nowadays introduced the beta of a brand new characteristic referred to as “nested virtualization.” As the identify implies, this necessarily permits you to run VMs inside VMs.
But why would you need to do this? “Nested virtualization makes it easier for enterprise users to move their on-premises, virtualized workloads to the cloud without having to import and convert VM images,” Compute Engine product supervisor Scott Van Woudenberg writes in nowadays’s announcement. “Dev/test and CI/CD workloads that need to validate software in multiple environments are a good match for nested virtualization.”
He additionally argues that it is a helpful characteristic for construction inexpensive cloud-based crisis restoration answers and that it’ll be helpful for corporations that need to arrange digital environments for coaching and certification, the place you need to ensure that everyone will get the similar setting to paintings from.
This new characteristic is to be had for just about any form of Compute Engine VM, together with preemptible VMs. The simplest requirement is that the VM has to run on an Intel Haswell or more moderen CPU.
The method this works nearly is that you arrange a typical VM after which set up a KVM-compatible hypervisor on that example. Google notes that it doesn’t lately beef up non-KVM hypervisors like Xen, ESX and Microsoft’s Hyper-V. This simplest works for Linux circumstances, regardless that. Nested virtualization isn’t to be had for Windows machines.
It’s value noting that Microsoft Azure already supported nested virtualization (the usage of the Hyper-V hypervisor). On AWS, builders can use gear like Oracle’s Ravello nested hypervisor to reach the similar functions.
Featured Image: Cube/Getty Images