| /linux/drivers/vhost/ |
| A 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/fs/vboxsf/ |
| 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.
|
| /linux/arch/x86/kvm/ |
| A D | Kconfig | 14 operating systems inside virtual machines (guests).
90 Enables KVM guests to create SGX enclaves.
93 guests via a device node, e.g. /dev/sgx_vepc.
120 Provides KVM support for the hosting Xen HVM guests and
|
| /linux/drivers/staging/unisys/Documentation/ABI/ |
| A D | sysfs-platform-visorchipset | 64 situation by sending a message to guests using these VFs, and
66 another message is sent to the guests to re-enable the VFs.
83 situation by sending a message to guests using these VFs, and
85 another message is sent to the guests to re-enable the VFs.
|
| /linux/drivers/xen/ |
| 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.
308 Support for auto-translated physmap guests.
|
| /linux/Documentation/virt/kvm/ |
| 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.
|
| A D | running-nested-guests.rst | 2 Running nested guests with KVM
61 multiple nested guests (level-2 guests), running different OSes, on
64 - Live migration of "guest hypervisors" and their nested guests, for
197 actually running L2 guests, is expected to function normally even on AMD
198 systems but may fail once guests are started.
|
| A D | index.rst | 32 running-nested-guests
|
| /linux/tools/testing/selftests/arm64/fp/ |
| 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
|
| /linux/Documentation/filesystems/ |
| A 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/Documentation/ABI/testing/ |
| A D | sysfs-hypervisor-xen | 26 and all other guests. Only available to
27 privileged guests.
|
| /linux/Documentation/admin-guide/hw-vuln/ |
| 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
258 which run untrusted guests, reduces the attack vector space.
261 guests, provide interesting data for an attacker depends on the system
352 with SMT enabled, because the effective page tables for guests are
459 2. Virtualization with trusted guests
472 3. Virtualization with untrusted guests
509 Confinement of guests to a single or a group of physical cores which
521 affinity to the CPUs which run the untrusted guests can depending on
590 SMT systems vulnerable when running untrusted guests with EPT enabled.
[all …]
|
| A 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
|
| A D | spectre.rst | 266 For Spectre variant 1 attacks, rogue guests can pass parameters
272 For Spectre variant 2 attacks, rogue guests can :ref:`poison
279 guests from affecting indirect branching in the host kernel.
281 To protect host processes from rogue guests, host processes can have
292 between guests. This may be done via mechanisms such as shared memory
302 Linux kernel mitigates attacks to other guests running in the same
507 Within the kernel, Spectre variant 1 attacks from rogue guests are
513 For Spectre variant 2 attacks from rogue guests to the kernel, the
515 poisoned entries in branch target buffer left by rogue guests. It also
518 or attacker guests leaving poisoned entries in the return stack buffer.
[all …]
|
| A D | multihit.rst | 63 guests in a virtualized system.
156 2. Virtualization with trusted guests
163 3. Virtualization with untrusted guests
|
| /linux/fs/fuse/ |
| A 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/Documentation/powerpc/ |
| A D | dawr-power9.rst | 30 guest on a POWER9 host. Current Linux guests ignore this error, so
48 The same will also be true for any guests started on a POWER9
81 inconsistent view of what's available. Similarly for guests.
|
| /linux/Documentation/virt/kvm/arm/ |
| A D | pvtime.rst | 7 support for AArch64 guests:
21 paravirtualized time is not available to 32 bit Arm guests. The existence of
|
| A D | ptp_kvm.rst | 6 PTP_KVM is used for high precision time sync between host and guests.
|
| /linux/Documentation/s390/ |
| A 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
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
681 three guests and to provide an interface to the vfio_ap driver for
682 use by the guests::
690 To create the mediated devices for the three guests::
[all …]
|
| /linux/Documentation/admin-guide/mm/damon/ |
| A D | reclaim.rst | 22 memory to host, and the host reallocates the reported memory to other guests.
24 guests could be not so memory-frugal, mainly because some kernel subsystems and
26 guests could report only small amount of memory as free to host, results in
28 guests could mitigate this problem.
|
| /linux/Documentation/devicetree/bindings/misc/ |
| A D | pvpanic-mmio.txt | 9 QEMU exposes the data register to guests as memory mapped registers.
|
| /linux/drivers/visorbus/ |
| A D | Kconfig | 11 Virtualized devices allow Linux guests on a system to share disks and
|
| /linux/arch/riscv/kvm/ |
| A D | Kconfig | 12 other operating systems inside virtual machines (guests).
|
| /linux/net/iucv/ |
| A D | Kconfig | 9 communication link between VM guests.
|