Lines Matching refs:nested

2 Running nested guests with KVM
5 A nested guest is the ability to run a guest inside another guest (it
34 - L2 – level-2 guest; a VM running on L1, this is the "nested guest"
42           resulting in at least four levels in a nested setup — L0 (bare
44           (guest hypervisor), L3 (nested guest).
54 There are several scenarios where nested KVM can be useful, to name a
59   Provider, using nested KVM lets you rent a large enough "guest
61   multiple nested guests (level-2 guests), running different OSes, on
64 - Live migration of "guest hypervisors" and their nested guests, for
74 Enabling "nested" (x86)
77 From Linux kernel v4.19 onwards, the ``nested`` KVM parameter is enabled
82 nesting, set the ``nested`` KVM module parameter to ``Y`` or ``1``.  To
95     $ modinfo kvm_intel | grep -i nested
96     parm:           nested:bool
98 3. For the nested KVM configuration to persist across reboots, place the
103     options kvm-intel nested=y
110 5. Verify if the ``nested`` parameter for KVM is enabled::
112     $ cat /sys/module/kvm_intel/parameters/nested
119 Additional nested-related kernel parameters (x86)
137 .. note:: If you suspect your L2 (i.e. nested guest) is running slower,
142 Starting a nested guest (x86)
157 nested guest with accelerated KVM.
160 Enabling "nested" (s390x)
163 1. On the host hypervisor (L0), enable the ``nested`` parameter on
167     $ modprobe kvm nested=1
170           with the ``nested`` paramter — i.e. to be able to enable
171           ``nested``, the ``hpage`` parameter *must* be disabled.
182 Live migration with nested KVM
185 Migrating an L1 guest, with a  *live* nested guest in it, to another
203 - Migrating a nested guest (L2) to another L1 guest on the *same* bare
206 - Migrating a nested guest (L2) to another L1 guest on a *different*
209 - Migrating a nested guest (L2) to a bare metal host.
211 Reporting bugs from nested setups
214 Debugging "nested" problems can involve sifting through log files across
218 - Mention that you are in a "nested" setup.  If you are running any kind
221   *mention* that they're using nested virtualization.
226   they think they're running nested KVM.  Thus confusing "nested Virt"
227   (which could also mean, QEMU on KVM) with "nested KVM" (KVM on KVM).