Searched refs:guests (Results 1 – 25 of 79) sorted by relevance
1234
| /linux-5.19.10/fs/vboxsf/ |
| 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.
|
| /linux-5.19.10/drivers/vhost/ |
| D | Kconfig | 48 for use with virtio-scsi guests
58 sockets for communicating with guests. The guests must have the
81 This option allows vhost to support guests with a different byte
|
| /linux-5.19.10/arch/x86/kvm/ |
| D | Kconfig | 14 operating systems inside virtual machines (guests).
94 Enables KVM guests to create SGX enclaves.
97 guests via a device node, e.g. /dev/sgx_vepc.
124 Provides KVM support for the hosting Xen HVM guests and
|
| /linux-5.19.10/Documentation/ABI/testing/ |
| D | sysfs-hypervisor-xen | 26 and all other guests. Only available to
27 privileged guests.
|
| /linux-5.19.10/drivers/xen/ |
| 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.
308 Support for auto-translated physmap guests.
362 Require virtio for Xen guests to use grant mappings.
|
| /linux-5.19.10/Documentation/x86/ |
| 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
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
|
| /linux-5.19.10/tools/testing/selftests/arm64/fp/ |
| 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
|
| /linux-5.19.10/Documentation/filesystems/ |
| D | virtiofs.rst | 18 Use cases include making files available to new guests during installation,
20 stateless or ephemeral guests, and sharing a directory between guests.
|
| /linux-5.19.10/fs/fuse/ |
| D | Kconfig | 36 The Virtio Filesystem allows guests to mount file systems from the
39 If you want to share files between guests or with the host, answer Y
|
| /linux-5.19.10/Documentation/virt/kvm/x86/ |
| 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.
|
| D | index.rst | 18 running-nested-guests
|
| 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.
|
| /linux-5.19.10/Documentation/powerpc/ |
| D | dawr-power9.rst | 38 guest on a POWER9 host. Current Linux guests ignore this error, so
56 The same will also be true for any guests started on a POWER9
89 inconsistent view of what's available. Similarly for guests.
|
| /linux-5.19.10/Documentation/admin-guide/hw-vuln/ |
| 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 …]
|
| D | tsx_async_abort.rst | 73 applications running on hosts or guests.
250 1. Trusted userspace and guests
255 disabled. The same applies to virtualized environments with trusted guests.
258 2. Untrusted userspace and guests
261 If there are untrusted applications or guests on the system, enabling TSX
|
| D | multihit.rst | 63 guests in a virtualized system.
156 2. Virtualization with trusted guests
163 3. Virtualization with untrusted guests
|
| /linux-5.19.10/arch/powerpc/kvm/ |
| D | Kconfig | 12 other operating systems inside virtual machines (guests).
116 guests that use hash MMU mode.
149 Old nested HV capable Linux guests have a bug where they don't
153 L2 guests.
|
| /linux-5.19.10/Documentation/virt/kvm/arm/ |
| D | pvtime.rst | 7 support for AArch64 guests:
21 paravirtualized time is not available to 32 bit Arm guests. The existence of
|
| D | ptp_kvm.rst | 6 PTP_KVM is used for high precision time sync between host and guests.
|
| /linux-5.19.10/Documentation/devicetree/bindings/misc/ |
| D | pvpanic-mmio.txt | 9 QEMU exposes the data register to guests as memory mapped registers.
|
| /linux-5.19.10/drivers/virt/coco/efi_secret/ |
| D | Kconfig | 11 guests). The driver exposes the secrets as files in
|
| /linux-5.19.10/net/iucv/ |
| D | Kconfig | 9 communication link between VM guests.
|
| /linux-5.19.10/arch/riscv/kvm/ |
| D | Kconfig | 12 other operating systems inside virtual machines (guests).
|
| /linux-5.19.10/Documentation/s390/ |
| D | vfio-ap.rst | 14 is to make AP cards available to KVM guests using the VFIO mediated device
168 This is valid because both guests have a unique set of APQNs:
177 This is also valid because both guests have a unique set of APQNs:
186 This is an invalid configuration because both guests have access to
201 1. Provides the interfaces to secure APQNs for exclusive use of KVM guests.
210 Reserve APQNs for exclusive use of KVM guests
459 Let's now provide an example to illustrate how KVM guests may be given
461 three guests such that executing the lszcrypt command on the guests would
530 2. Secure the AP queues to be used by the three guests so that the host can not
681 three guests and to provide an interface to the vfio_ap driver for
[all …]
|
| /linux-5.19.10/arch/mips/kvm/ |
| D | Kconfig | 11 other operating systems inside virtual machines (guests).
|
1234