| /openbmc/linux/include/xen/interface/ |
| H A D | xenpmu.h | 45 * - XENPMU_MODE_SELF: Guests can profile themselves
46 * - XENPMU_MODE_HV: Guests can profile themselves, dom0 profiles
49 * everyone: itself, the hypervisor and the guests.
77 * guests set to vcpu_id;
82 * Domain that was interrupted. On non-privileged guests set to
84 * On privileged guests can be DOMID_SELF, DOMID_XEN, or, when in
|
| /openbmc/qemu/docs/system/i386/ |
| H A D | hyperv.rst | 14 KVM on x86 implements Hyper-V Enlightenments for Windows guests. These features
15 make Windows and Hyper-V guests think they're running on top of a Hyper-V
127 to the specification, guests shouldn't use this information and it is unknown
143 The enlightenment is nested specific, it targets Hyper-V on KVM guests. When
150 (Reference TSC page) to its own guests.
160 The enlightenment is nested specific, it targets Hyper-V on KVM guests. When
190 is required by Windows and Hyper-V guests to properly mitigate SMT related CPU
198 of host setup. To keep guests secure, this can only be used in conjunction with
229 The enlightenment is nested specific, it targets Hyper-V on KVM guests. When
249 The enlightenment is nested specific, it targets Hyper-V on KVM guests. When
[all …]
|
| H A D | xen.rst | 8 KVM has support for hosting Xen guests, intercepting Xen hypercalls and event
9 channel (Xen PV interrupt) delivery. This allows guests which expect to be
54 to be in the upper 64 bits of the MSI message. For guests with large numbers
64 through simultaneous grants. For guests with large numbers of PV devices and
86 model for emulated Xen guests, meaning that just the default NIC provided
105 VirtIO devices can also be used; Linux guests may need to be dissuaded from
108 Booting Xen PV guests
|
| /openbmc/qemu/docs/system/ |
| H A D | confidential-guest-support.rst | 6 can compromise any of its guests. A number of platforms have added
7 mechanisms in hardware and/or firmware which give guests at least some
12 operation, but are often referred to as Secure Guests or Confidential
13 Guests. We use the term "Confidential Guest Support" to distinguish
15 attacks from other guests, or from network sources).
|
| H A D | security.rst | 64 CPU, memory, disk, or network. Guests must be unable to exceed their resource
69 could allow malicious guests to gain code execution in QEMU. At this point the
73 Guests often interact with other guests and share resources with them. A
74 malicious guest must not gain control of other guests or access their data.
75 Disk image files and network traffic must be protected from other guests unless
96 necessary for QEMU but are not exposed to guests. A guest that escapes into
|
| H A D | cpu-models-x86.rst.inc | 214 By disabling TSX, KVM-based guests can avoid paying the price of
291 This should be provided to guests, even if amd-ssbd is also provided,
306 exposed to guests whenever available in the host. ``virt-ssbd`` should
335 compatibility checks before launching guests, the default is guaranteed
347 ``qemu64`` is used for x86_64 guests and ``qemu32`` is used for i686
348 guests, when no ``-cpu`` argument is given to QEMU, or no ``<cpu>`` is
356 featureset, which prevents guests having optimal performance.
|
| /openbmc/linux/drivers/xen/ |
| H A D | Kconfig | 106 For example, by reading and writing the "xenbus" file, guests
195 device backend driver without para-virtualized support for guests.
198 other guests.
215 PCI devices to other guests. If you select this to be a module, you
217 you want to make visible to other guests.
257 to other guests via a high-performance shared-memory interface.
259 if guests need generic access to SCSI devices.
315 Support for auto-translated physmap guests.
369 Require virtio for Xen guests to use grant mappings.
|
| /openbmc/linux/drivers/vhost/ |
| H A D | Kconfig | 53 for use with virtio-scsi guests
63 sockets for communicating with guests. The guests must have the
86 This option allows vhost to support guests with a different byte
|
| /openbmc/qemu/docs/system/ppc/ |
| H A D | pseries.rst | 7 is also known as sPAPR, System p guests, or simply Power Linux guests (although
119 hypervisor and non-Linux guests in mind, you should use the virtio counterparts
121 since they will most probably give you better performance with Linux guests in a
175 KVM-PR uses the so-called **PR**\ oblem state of the PPC CPUs to run the guests,
183 Because all privileged instructions are trapped, guests that use a lot of
186 able to emulate a lot of guests CPUs. This module can even be used to run other
187 PowerPC guests like an emulated PowerMac.
196 In order to run KVM-PR guests with POWER9 processors, someone will need to start
208 to start pSeries guests. As the pSeries guest doesn't have access to the
211 pSeries guests as well, making nested virtualization possible with KVM-HV.
[all …]
|
| /openbmc/linux/arch/x86/include/asm/xen/ |
| H A D | interface.h | 78 * bit guests. */
106 /* Maximum number of virtual CPUs in multi-processor guests. */
205 * for HVM and PVH guests, not all information in this structure is updated:
207 * - For HVM guests, the structures read include: fpu_ctxt (if
210 * - PVH guests are the same as HVM guests, but additionally use ctrlreg[3] to
261 * For PV(H) guests these fields are RO.
284 * For PV(H) guests these fields are RO.
335 * WO for hypervisor, RO for guests.
|
| /openbmc/linux/arch/x86/kvm/ |
| H A D | Kconfig | 14 operating systems inside virtual machines (guests).
95 Enables KVM guests to create SGX enclaves.
98 guests via a device node, e.g. /dev/sgx_vepc.
136 Provides KVM support for the hosting Xen HVM guests and
|
| /openbmc/linux/Documentation/filesystems/ |
| H A D | virtiofs.rst | 17 Guests often require access to files residing on the host or remote systems.
18 Use cases include making files available to new guests during installation,
20 stateless or ephemeral guests, and sharing a directory between guests.
|
| /openbmc/linux/Documentation/arch/x86/ |
| H A D | tdx.rst | 25 TDX guests behave differently from bare-metal and traditional VMX guests.
26 In TDX guests, otherwise normal instructions or memory accesses can cause
63 In general, the #GP MSRs should not be used in guests. Their use likely
67 The #VE MSRs are typically able to be handled by the hypervisor. Guests
135 TDX guests ensure that all guest memory has been "accepted" before memory
174 emulates the access. That is not possible in TDX guests because VMEXIT
175 will expose the register state to the host. TDX guests don't trust the host
|
| /openbmc/linux/Documentation/virt/kvm/x86/ |
| H A D | nested-vmx.rst | 11 to easily and efficiently run guest operating systems. Normally, these guests
12 *cannot* themselves be hypervisors running their own guests, because in VMX,
13 guests cannot use VMX instructions.
16 hypervisors (which use VMX) with their own nested guests. It does so by
31 Single-level virtualization has two levels - the host (KVM) and the guests.
|
| H A D | running-nested-guests.rst | 4 Running nested guests with KVM
63 multiple nested guests (level-2 guests), running different OSes, on
66 - Live migration of "guest hypervisors" and their nested guests, for
199 actually running L2 guests, is expected to function normally even on AMD
200 systems but may fail once guests are started.
|
| /openbmc/qemu/include/hw/xen/interface/ |
| H A D | arch-arm.h | 19 * registers, the first argument in x0/r0 (for arm64/arm32 guests
46 * (including the hypervisor and other guests) must reside in memory
121 * - struct start_info is not exported to ARM guests.
123 * - struct shared_info is mapped by ARM guests using the
127 * - All the per-cpu struct vcpu_info are mapped by ARM guests using the
192 * Maximum number of virtual CPUs in legacy multi-processor guests.
264 /* AArch32 guests only */
267 /* AArch64 guests only */
387 * hypervisor. Guests must not rely on these hardcoded values but
|
| /openbmc/linux/Documentation/admin-guide/hw-vuln/ |
| H A D | l1tf.rst | 219 guests affine to one or more physical cores. The proper mechanism for
223 If only a single guest or related guests run on sibling SMT threads on
235 **Note**, that assigning guests to a fixed set of physical cores affects
241 For further information about confining guests to a single or to a group
258 which run untrusted guests, reduces the attack vector space.
261 guests, provide interesting data for an attacker depends on the system
282 of other mitigation solutions like confining guests to dedicated cores.
352 with SMT enabled, because the effective page tables for guests are
459 2. Virtualization with trusted guests
472 3. Virtualization with untrusted guests
[all …]
|
| H A D | gather_data_sampling.rst | 34 Guests can infer data from hosts
35 Guest can infer guest from other guests
39 lower-privilege contexts like guests and when running outside SGX enclaves.
42 that guests are not allowed to disable the GDS mitigation. If a host erred and
|
| /openbmc/linux/Documentation/virt/hyperv/ |
| H A D | overview.rst | 15 Hyper-V runs on x86/x64 and arm64 architectures, and Linux guests
21 Linux guests communicate with Hyper-V in four different ways:
89 On arm64, Hyper-V supports guests with 4/16/64 Kbyte pages as
127 earlier versions may provide guests with ACPI tables that indicate
143 On x86/x64, Hyper-V supports 32-bit and 64-bit guests, and Linux
148 On arm64, Hyper-V supports only 64-bit guests.
|
| /openbmc/linux/fs/vboxsf/ |
| H A D | Kconfig | 6 VirtualBox hosts can share folders with guests, this driver
10 If you want to use shared folders in VirtualBox guests, answer Y or M.
|
| /openbmc/qemu/docs/system/arm/ |
| H A D | virt.rst | 40 - running guests using the KVM accelerator on aarch64 hardware
225 - For guests using the Linux kernel boot protocol (this means any
227 of the DTB is passed in a register (``r2`` for 32-bit guests,
228 or ``x0`` for 64-bit guests)
230 - For guests booting as "bare-metal" (any other kind of boot),
|
| /openbmc/linux/arch/powerpc/kvm/ |
| H A D | Kconfig | 12 other operating systems inside virtual machines (guests).
117 guests that use hash MMU mode.
167 Old nested HV capable Linux guests have a bug where they don't
171 L2 guests.
|
| /openbmc/linux/arch/x86/boot/ |
| H A D | io.h | 24 * TDX guests override these to use hypercalls.
35 * TDX guests override these callbacks with TDX-specific helpers.
|
| /openbmc/linux/tools/testing/selftests/arm64/fp/ |
| H A D | README | 68 should be run in parallel in two KVM guests, while simultaneously
71 1) Start 2 guests, using the following command for each:
83 allows multiple guests to be run in parallel while running other
|
| /openbmc/qemu/docs/specs/ |
| H A D | pci-serial.rst | 9 guests work out-of-the box with all cards. There is a Windows inf file
10 (``docs/qemupciserial.inf``) to set up the cards in Windows guests.
|