Difference between revisions of "stoney cloud: Nested virtualization"

From stoney cloud
Jump to: navigation, search
[unchecked revision][unchecked revision]
(Setup)
(Abstract)
Line 12: Line 12:
 
* https://docs.google.com/file/d/0BzyAwvVlQckedmpobUY1Sm0zNWc/edit
 
* https://docs.google.com/file/d/0BzyAwvVlQckedmpobUY1Sm0zNWc/edit
  
For Intel CPUs we are going to enable [http://www.spinics.net/lists/kvm/msg87634.html Shadow VMCS] which requires a sufficiently new CPU, otherwise it gets ignored.
+
For Intel CPUs we are going to enable [http://www.spinics.net/lists/kvm/msg87634.html Shadow VMCS] which requires a sufficiently new CPU, otherwise it gets ignored. This should give some performance increase, disable it if it causes problems.
  
 
== Setup ==
 
== Setup ==

Revision as of 14:06, 20 December 2013

Abstract

This document describes how to set up nested virtualization on a default installation (until it gets enabled by default).

Nested virtualization permits to start another hypervisor (in our case KVM) inside a virtual machine.

With the current version of Qemu/KVM you can expect a performance of about 25% of the host performance (concerning CPU and Memory access) in a guest within a guest (L2). In the future Qemu/KVM should support Intels Virtual EPT which should give 80% of the host performance for L2.

See:

For Intel CPUs we are going to enable Shadow VMCS which requires a sufficiently new CPU, otherwise it gets ignored. This should give some performance increase, disable it if it causes problems.

Setup

Login as root, then execute the following:

cat > /etc/modprobe.d/nested-virtualization.conf << EOF
options kvm-intel nested=Y enable_shadow_vmcs=Y
options kvm-amd nested=Y
EOF

You either have to reboot or rmmod/modprobe the corresponding module if no VM is running