Lines Matching full:l1
17 | L1 (Guest Hypervisor) |
31 - L1 – level-1 guest; a VM running on L0; also called the "guest
34 - L2 – level-2 guest; a VM running on L1, this is the "nested guest"
43 metal, running the LPAR hypervisor), L1 (host hypervisor), L2
47 L1, and L2) for all architectures; and will largely focus on
146 able to start an L1 guest with::
173 2. The guest hypervisor (L1) must be provided with the ``sie`` CPU
177 3. Now the KVM module can be loaded in the L1 (guest hypervisor)::
185 Migrating an L1 guest, with a *live* nested guest in it, to another
189 On AMD systems, once an L1 guest has started an L2 guest, the L1 guest
192 or save-and-load an L1 guest while an L2 guest is running will result in
194 kernel 'oops', or an outright kernel panic. Such a migrated or loaded L1
196 Migrating an L1 guest merely configured to support nesting, while not
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*
215 L0, L1 and L2; this can result in tedious back-n-forth between the bug
224 have KVM enabled for their guest hypervisor (L1), which results in
236 - Kernel, libvirt and QEMU version from L1
238 - QEMU command-line of L1 -- when using libvirt, you'll find it here:
246 - ``cat /sys/cpuinfo`` from L1
250 - ``lscpu`` from L1
254 - Full ``dmesg`` output from L1
264 - Output of: ``x86info -a`` from L1
268 - Output of: ``dmidecode`` from L1
276 - ``/proc/sysinfo`` from L1; this will also include the info from L0