Data Centre

Virtualization

Nested virtualization comes to Google's cloud

Not just for Inception fans: This is how you cloudify tricky-to-migrate workloads

By Simon Sharwood, APAC Editor

3 SHARE

In late August 2017 The Reg's virtualization desk learned that Google was working hard to make KVM better at nested virtualization. And now we know why, as the advertising giant's cloud has just revealed a nested virtualization beta.

The new offering means that you can run a virtual machine inside the virtual machines you rent from the company's infrastructure-as-a-service limb. The service is a beta for now, and requires you to get the KVM hypervisor running inside a Google Cloud VM, which itself runs on KVM. Google's not supporting ESX or Xen, but that's not a huge barrier to overcome as KVM can import VMware's VMDK files and plenty of tools let you re-format VMs.

Why bother? There's a few reasons. You might have workload you'd quite like to run in the cloud, but shy away from migrating because a lift-and-shift would likely break it. Packaging it as a VM and running it as a nested VM sorts that out.

Or perhaps you'd like to have some VMs in the cloud as a disaster recovery option, but don't want to make them native to your chosen IaaS provider. Again, nested virtualization helps by letting you get those VMs into a cloud without first having to perform major renovations.

Google's nested virtualization won't work with any old VM: you'll need to specify a Haswell or later CPU to get access to the Intel VT-x extensions that make this all possible. And then be prepared to wear what Google warns will be “at least a 10% penalty for CPU-bound workloads and possibly much more for I/O bound workloads.”

Microsoft's Azure switched on its own nested virtualization in January 2017 and AWS' EC2 can do so with help from third parties like Ravello. ®

Sign up to our NewsletterGet IT in your inbox daily

3 Comments

More from The Register

Xen Project's plan after AWS goes KVM: Talk up embedded future

Update AWS changes its tune, multi-hypervisor plan is its future

Xen 4.11 debuts new ‘PVH’ guest type, for the sake of security

Take some paravirtualization, add hardware extensions and – voila – QEMU flies away

KVM plans big boosts to storage and nested virtualization

Project maintainer Paolo Bonzini details open source hypervisor's future directions

Developer plots server virtualization comeback for XenServer

Plans open source revival of XCP, to go places Citrix won’t

Secure microkernel in a KVM switch offers spy-grade app virtualization

CSIRO and Data61 have a way to get a few air-gapped apps on one screen

KVM? Us? Amazon erases new hypervisor from AWS EC2 FAQ

We've fro-Xen page to preserve evidence of NVMe servers and Xen's stay of execution

Xen Project patches Intel’s Lazy FPU flaw, VMware doesn't need to

UPDATE Guest register states are readable, but the patch cavalry has arrived

Xen 4.11 is over a month late and its devs are mostly cool with that

Hardware hassles mean rc7 was needed, spark discussion about release cadence

Xen turns it up to 4.11 and shrinks itself to contain containers

New version turns Meltdown mitigation into a feature

AWS adopts home-brewed KVM as new hypervisor

Out with Xen, in with 'core KVM technology' for new C5 instances and future VMs too