Home
last modified time | relevance | path

Searched refs:KVM (Results 126 – 150 of 1802) sorted by relevance

12345678910>>...73

/dports/emulators/qemu/qemu-6.2.0/hw/intc/
H A DKconfig31 depends on ARM_GIC && KVM
48 depends on S390_FLIC && KVM
/dports/multimedia/libv4l/linux-5.13-rc2/virt/kvm/
H A DKconfig2 # KVM common configuration items and defaults
50 depends on KVM && COMPAT && !(S390 || ARM64)
/dports/emulators/qemu60/qemu-6.0.0/hw/intc/
H A DKconfig31 depends on ARM_GIC && KVM
48 depends on S390_FLIC && KVM
/dports/multimedia/v4l-utils/linux-5.13-rc2/virt/kvm/
H A DKconfig2 # KVM common configuration items and defaults
50 depends on KVM && COMPAT && !(S390 || ARM64)
/dports/emulators/qemu-devel/qemu-de8ed1055c2ce18c95f597eb10df360dcb534f99/hw/intc/
H A DKconfig31 depends on ARM_GIC && KVM
48 depends on S390_FLIC && KVM
/dports/devel/aws-sdk-cpp/aws-sdk-cpp-1.9.129/aws-cpp-sdk-storagegateway/source/model/
H A DHostEnvironment.cpp47 return HostEnvironment::KVM; in GetHostEnvironmentForName()
73 case HostEnvironment::KVM: in GetNameForHostEnvironment()
/dports/emulators/qemu5/qemu-5.2.0/roms/skiboot/doc/opal-api/
H A Dopal-pci-phb-mmio-enable-27.rst29 hardware does not support disable. KVM may call this function for all MMIO
30 windows and ignore the opal_unsuppsorted return code so long as KVM has
31 disabled MMIO to all downstream PCI devices and assured that KVM and OS guest
/dports/emulators/qemu42/qemu-4.2.1/roms/skiboot/doc/opal-api/
H A Dopal-pci-phb-mmio-enable-27.rst29 hardware does not support disable. KVM may call this function for all MMIO
30 windows and ignore the opal_unsuppsorted return code so long as KVM has
31 disabled MMIO to all downstream PCI devices and assured that KVM and OS guest
/dports/emulators/qemu-utils/qemu-4.2.1/roms/skiboot/doc/opal-api/
H A Dopal-pci-phb-mmio-enable-27.rst29 hardware does not support disable. KVM may call this function for all MMIO
30 windows and ignore the opal_unsuppsorted return code so long as KVM has
31 disabled MMIO to all downstream PCI devices and assured that KVM and OS guest
/dports/emulators/qemu-guest-agent/qemu-5.0.1/roms/skiboot/doc/opal-api/
H A Dopal-pci-phb-mmio-enable-27.rst29 hardware does not support disable. KVM may call this function for all MMIO
30 windows and ignore the opal_unsuppsorted return code so long as KVM has
31 disabled MMIO to all downstream PCI devices and assured that KVM and OS guest
/dports/emulators/qemu/qemu-6.2.0/roms/skiboot/doc/opal-api/
H A Dopal-pci-phb-mmio-enable-27.rst29 hardware does not support disable. KVM may call this function for all MMIO
30 windows and ignore the opal_unsuppsorted return code so long as KVM has
31 disabled MMIO to all downstream PCI devices and assured that KVM and OS guest
/dports/emulators/qemu60/qemu-6.0.0/roms/skiboot/doc/opal-api/
H A Dopal-pci-phb-mmio-enable-27.rst29 hardware does not support disable. KVM may call this function for all MMIO
30 windows and ignore the opal_unsuppsorted return code so long as KVM has
31 disabled MMIO to all downstream PCI devices and assured that KVM and OS guest
/dports/multimedia/libv4l/linux-5.13-rc2/Documentation/virt/kvm/arm/
H A Dhyp-abi.rst9 KVM). It doesn't cover the interaction of the kernel with the
10 hypervisor when running as a guest (under Xen, KVM or any other
14 Note: KVM/arm has been removed from the kernel. The API described
16 booted at HYP. It can also be used by a hypervisor other than KVM
/dports/multimedia/v4l-utils/linux-5.13-rc2/Documentation/virt/kvm/arm/
H A Dhyp-abi.rst9 KVM). It doesn't cover the interaction of the kernel with the
10 hypervisor when running as a guest (under Xen, KVM or any other
14 Note: KVM/arm has been removed from the kernel. The API described
16 booted at HYP. It can also be used by a hypervisor other than KVM
/dports/multimedia/v4l_compat/linux-5.13-rc2/Documentation/virt/kvm/arm/
H A Dhyp-abi.rst9 KVM). It doesn't cover the interaction of the kernel with the
10 hypervisor when running as a guest (under Xen, KVM or any other
14 Note: KVM/arm has been removed from the kernel. The API described
16 booted at HYP. It can also be used by a hypervisor other than KVM
/dports/devel/util-linux/util-linux-2.36/tests/expected/lscpu/
H A Dlscpu-s390-kvm11 Hypervisor: KVM/Linux
12 Hypervisor vendor: KVM
/dports/multimedia/libv4l/linux-5.13-rc2/Documentation/virt/kvm/
H A Ds390-pv-boot.rst17 KVM to decrypt the protected virtual machine.
19 Based on this data, KVM will make the protected virtual machine known
22 hashes, to ensure integrity. Afterwards KVM can run the PVM via the
23 SIE instruction which the UV will intercept and execute on KVM's
H A Dnested-vmx.rst10 On Intel processors, KVM uses Intel's VMX (Virtual-Machine eXtensions)
31 Single-level virtualization has two levels - the host (KVM) and the guests.
32 In nested virtualization, we have three levels: The host (KVM), which we call
63 which are used in practice by popular hypervisors (KVM and others).
70 Still, for debugging purposes, KVM developers might be interested to know the
79 of this structure changes, this can break live migration across KVM versions.
/dports/multimedia/v4l-utils/linux-5.13-rc2/Documentation/virt/kvm/
H A Ds390-pv-boot.rst17 KVM to decrypt the protected virtual machine.
19 Based on this data, KVM will make the protected virtual machine known
22 hashes, to ensure integrity. Afterwards KVM can run the PVM via the
23 SIE instruction which the UV will intercept and execute on KVM's
H A Dnested-vmx.rst10 On Intel processors, KVM uses Intel's VMX (Virtual-Machine eXtensions)
31 Single-level virtualization has two levels - the host (KVM) and the guests.
32 In nested virtualization, we have three levels: The host (KVM), which we call
63 which are used in practice by popular hypervisors (KVM and others).
70 Still, for debugging purposes, KVM developers might be interested to know the
79 of this structure changes, this can break live migration across KVM versions.
/dports/multimedia/v4l_compat/linux-5.13-rc2/Documentation/virt/kvm/
H A Ds390-pv-boot.rst17 KVM to decrypt the protected virtual machine.
19 Based on this data, KVM will make the protected virtual machine known
22 hashes, to ensure integrity. Afterwards KVM can run the PVM via the
23 SIE instruction which the UV will intercept and execute on KVM's
/dports/emulators/qemu/qemu-6.2.0/docs/system/arm/
H A Dvirt.rst40 - running guests using the KVM accelerator on aarch64 hardware
59 - ``host`` (with KVM only)
60 - ``max`` (same as ``host`` for KVM; best possible emulation with TCG)
69 with KVM. You may also need to ensure your guest kernel is configured
103 Use the same GIC version the host provides, when using KVM
105 Use the best GIC version possible (same as host when using KVM;
/dports/emulators/qemu5/qemu-5.2.0/docs/system/arm/
H A Dvirt.rst40 - running guests using the KVM accelerator on aarch64 hardware
56 - ``host`` (with KVM only)
57 - ``max`` (same as ``host`` for KVM; best possible emulation with TCG)
66 with KVM. You may also need to ensure your guest kernel is configured
100 Use the same GIC version the host provides, when using KVM
102 Use the best GIC version possible (same as host when using KVM;
/dports/emulators/qemu60/qemu-6.0.0/docs/system/arm/
H A Dvirt.rst40 - running guests using the KVM accelerator on aarch64 hardware
58 - ``host`` (with KVM only)
59 - ``max`` (same as ``host`` for KVM; best possible emulation with TCG)
68 with KVM. You may also need to ensure your guest kernel is configured
102 Use the same GIC version the host provides, when using KVM
104 Use the best GIC version possible (same as host when using KVM;
/dports/emulators/qemu-devel/qemu-de8ed1055c2ce18c95f597eb10df360dcb534f99/docs/system/arm/
H A Dvirt.rst40 - running guests using the KVM accelerator on aarch64 hardware
59 - ``host`` (with KVM only)
60 - ``max`` (same as ``host`` for KVM; best possible emulation with TCG)
69 with KVM. You may also need to ensure your guest kernel is configured
103 Use the same GIC version the host provides, when using KVM
105 Use the best GIC version possible (same as host when using KVM;

12345678910>>...73