stoney cloud: Nested virtualization - Revision history

Michael: /* Setup */

2013-12-24T13:57:08Z

Setup

← Older revision		Revision as of 15:57, 24 December 2013
Line 15:		Line 15:

	== Setup ==		== Setup ==
			=== Intel ===
			Login as root, then execute the following:
			<source lang='bash'>
			cat > /etc/modprobe.d/nested-virtualization.conf << EOF
			options kvm-intel nested=Y enable_shadow_vmcs=Y
			EOF
			</source>

			You either have to reboot or <code>rmmod/modprobe</code> the corresponding module if no VM is running. For example:
			rmmod kvm_intel
			modprobe kvm_intel

			=== AMD ===
	Login as root, then execute the following:		Login as root, then execute the following:

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

	You either have to reboot or <code>rmmod/modprobe</code> the corresponding module if no VM is running		You either have to reboot or <code>rmmod/modprobe</code> the corresponding module if no VM is running. For example:
			rmmod kvm_amd
			modprobe kvm_amd

	== VM configuration ==		== VM configuration ==

2013-12-20T13:25:22Z

VM configuration

← Older revision		Revision as of 15:25, 20 December 2013
Line 31:		Line 31:
	The following is largely untested, therefore this is more an instruction on how to figure out what the correct setting is. (hint: remove this line and update the configuration below if you have figured it out)		The following is largely untested, therefore this is more an instruction on how to figure out what the correct setting is. (hint: remove this line and update the configuration below if you have figured it out)

	First try to start any VM and execute the following ~~to see whether virtualization is available~~ '''~~in the~~ guest''':		First try to start any VM and execute the following '''inside a Linux guest''' to see whether virtualization is available:

	<source lang='bash'>		<source lang='bash'>

2013-12-20T13:24:47Z

VM configuration

← Older revision		Revision as of 15:24, 20 December 2013
Line 29:		Line 29:
	== VM configuration ==		== VM configuration ==

	The following is largely untested, therefore this is more an instruction on how to figure out what the correct setting is.		The following is largely untested, therefore this is more an instruction on how to figure out what the correct setting is. (hint: remove this line and update the configuration below if you have figured it out)

	First try to start any VM and execute the following to see whether virtualization is available '''in the guest''':		First try to start any VM and execute the following to see whether virtualization is available '''in the guest''':

2013-12-20T13:24:09Z

Setup

← Older revision		Revision as of 15:24, 20 December 2013
Line 27:		Line 27:
	You either have to reboot or <code>rmmod/modprobe</code> the corresponding module if no VM is running		You either have to reboot or <code>rmmod/modprobe</code> the corresponding module if no VM is running

			== VM configuration ==

			The following is largely untested, therefore this is more an instruction on how to figure out what the correct setting is.

			First try to start any VM and execute the following to see whether virtualization is available '''in the guest''':

			<source lang='bash'>
			grep vmx /proc/cpuinfo
			</source>

			If there is support, the output should be something like this:

			<pre>
			flags : [...] vmx [...]
			</pre>

			If it does not get enabled automatically by libvirt as soon as the hypervisor supports nested virtualization (it should, though), you have to change to XML description of the VM. To that end, use <code>virsh edit</code> on the node after having it defined it and replace the lines:

			<source lang='xml'>
			<cpu mode='host-model'>
			<model fallback='allow'/>
			</cpu>
			</source>

			with

			<source lang='xml'>
			<cpu mode='host-model'>
			<model fallback='allow'/>
			<feature policy='require' name='vmx'/>
			</cpu>
			</source>

	[[Category:stoney cloud]][[Category:Installation]]		[[Category:stoney cloud]][[Category:Installation]]

2013-12-20T13:06:01Z

Abstract

← Older revision		Revision as of 15:06, 20 December 2013
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 ==

2013-12-20T13:05:20Z

Setup

← Older revision		Revision as of 15:05, 20 December 2013
Line 16:		Line 16:
	== Setup ==		== Setup ==

	Login as root, then execute the following ~~and reboot (or <code>rmmod/modprobe</code> the corresponding module if no VM is running)~~		Login as root, then execute the following:

	<source lang='bash'>		<source lang='bash'>
Line 24:		Line 24:
	EOF		EOF
	</source>		</source>

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


	[[Category:stoney cloud]][[Category:Installation]]		[[Category:stoney cloud]][[Category:Installation]]

2013-12-20T13:04:50Z

Setup

← Older revision		Revision as of 15:04, 20 December 2013
Line 16:		Line 16:
	== Setup ==		== Setup ==

	Login as root, then execute the following and reboot (or <code>rmmod/modprobe</code> the corresponding ~~modules~~ if no VM is running)		Login as root, then execute the following and reboot (or <code>rmmod/modprobe</code> the corresponding module if no VM is running)

	<source lang='bash'>		<source lang='bash'>

2013-12-20T13:04:39Z

Setup

← Older revision		Revision as of 15:04, 20 December 2013
Line 20:		Line 20:
	<source lang='bash'>		<source lang='bash'>
	cat > /etc/modprobe.d/nested-virtualization.conf << EOF		cat > /etc/modprobe.d/nested-virtualization.conf << EOF
	options kvm-intel nested=1		options kvm-intel nested=Y enable_shadow_vmcs=Y
	options kvm-amd nested=1		options kvm-amd nested=Y
	EOF		EOF
	</source>		</source>

	[[Category:stoney cloud]][[Category:Installation]]		[[Category:stoney cloud]][[Category:Installation]]

2013-12-20T13:02:03Z

Abstract

← Older revision		Revision as of 15:02, 20 December 2013
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 [		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.
	http://www.spinics.net/lists/kvm/msg87634.html Shadow VMCS] which requires a sufficiently new CPU, otherwise it gets ignored.

	== Setup ==		== Setup ==

2013-12-20T13:01:43Z

Abstract

← Older revision		Revision as of 15:01, 20 December 2013
Line 11:		Line 11:
	* http://events.linuxfoundation.org/sites/events/files/cojp13_nakajima.pdf		* http://events.linuxfoundation.org/sites/events/files/cojp13_nakajima.pdf
	* 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.

	== Setup ==		== Setup ==