/qemu/ |
H A D | meson_options.txt | 45 description: 'Documentations build support') 51 description: 'modules support (non Windows)') 63 description: 'build support utilities that come with QEMU') 65 description: 'build QGA VSS support (broken with MinGW)') 73 description: 'KVM acceleration support') 75 description: 'WHPX acceleration support') 77 description: 'HVF acceleration support') 79 description: 'NVMM acceleration support') 81 description: 'Xen backend support') 83 description: 'Xen PCI passthrough support') [all …]
|
H A D | meson.build | 196 error('Your compiler does not support -fsanitize=fuzzer') 479 # Emscripten doesn't support -no-pie but meson can't catch the compiler 571 error('Your compiler does not support -fsanitize=address') 590 error('Your compiler does not support -fsanitize=undefined') 609 # However, clang does not support this warning and this triggers an error. 617 # Detect support for PT_GNU_RELRO + DT_BIND_NOW. 648 # library. They need to be configurable, to support OSS-Fuzz 1136 gdbus_codegen_error = '@0@ uses gdbus-codegen, which does not support control flow integrity' 1275 # slirp < 4.7 is incompatible with CFI support in QEMU. This is because 1702 warning('could not find glib support for hv-balloon, disabling') [all …]
|
/qemu/scripts/ |
H A D | meson-buildoptions.sh | 20 printf "%s\n" ' --disable-qom-cast-debug cast debugging support' 31 printf "%s\n" ' graph lock debugging support' 32 printf "%s\n" ' --enable-debug-mutex mutex debugging support' 33 printf "%s\n" ' --enable-debug-remap syscall buffer debugging support' 96 printf "%s\n" ' af-xdp AF_XDP network backend support' 97 printf "%s\n" ' alsa ALSA sound support' 98 printf "%s\n" ' attr attr/xattr support' 101 printf "%s\n" ' bochs bochs image format support' 102 printf "%s\n" ' bpf eBPF support' 104 printf "%s\n" ' bzip2 bzip2 support for DMG images' [all …]
|
/qemu/docs/system/arm/ |
H A D | emulation.rst | 3 A-profile CPU architecture support 6 QEMU's TCG emulation includes support for the Armv5, Armv6, Armv7, 7 Armv8 and Armv9 versions of the A-profile architecture. It also has support for 11 - FEAT_AA32EL0 (Support for AArch32 at EL0) 12 - FEAT_AA32EL1 (Support for AArch32 at EL1) 13 - FEAT_AA32EL2 (Support for AArch32 at EL2) 14 - FEAT_AA32EL3 (Support for AArch32 at EL3) 17 - FEAT_AA64EL0 (Support for AArch64 at EL0) 18 - FEAT_AA64EL1 (Support for AArch64 at EL1) 19 - FEAT_AA64EL2 (Support for AArch64 at EL2) [all …]
|
/qemu/replay/ |
H A D | stubs-system.c | 62 error_report("replay support not available"); in hmp_info_replay() 66 error_report("replay support not available"); in hmp_replay_break() 70 error_report("replay support not available"); in hmp_replay_delete_break() 74 error_report("replay support not available"); in hmp_replay_seek() 79 "replay support not available"); in qmp_query_replay() 85 "replay support not available"); in qmp_replay_break() 90 "replay support not available"); in qmp_replay_delete_break() 95 "replay support not available"); in qmp_replay_seek()
|
/qemu/docs/system/i386/ |
H A D | tdx.rst | 15 while KVM hypervisor has TDX support and has TDX enabled. If those requirements 16 are met, the ``KVM_CAP_VM_TYPES`` will report the support of ``KVM_X86_TDX_VM``. 28 Since TDX doesn't support readonly memslot, TDVF cannot be mapped as pflash 31 OVMF is the opensource firmware that implements the TDVF support. Thus the 79 Current KVM doesn't support MSR based feature (e.g., MSR_IA32_ARCH_CAPABILITIES) 81 support of it. 90 "warning: host doesn't support requested feature: CPUID.07H:EBX.intel-pt [bit 25]" 112 -machine ...,confidential-guest-support=tdx0 \\ 123 - No readonly support for private memory; 125 - No SMM support: SMM support requires manipulating the guest register states [all …]
|
H A D | xen.rst | 1 Xen HVM guest support 8 KVM has support for hosting Xen guests, intercepting Xen hypercalls and event 12 Using the split irqchip is mandatory for Xen support. 24 Additionally, virtual APIC support can be advertised to the guest through the 31 When Xen support is enabled, QEMU changes hypervisor identification (CPUID 44 Setting this property enables the Xen guest support. If Xen version 4.5 or 47 vector support to the guest. 128 options, and as of Xen 4.17, Xen's PV shim mode does not support using a serial 141 The minimal Xen support in the KVM accelerator requires the host to be running
|
/qemu/docs/specs/ |
H A D | riscv-iommu.rst | 3 RISC-V IOMMU support for RISC-V machines 33 As of this writing the existing Linux kernel support `linux-v8`_, not yet merged, 34 does not have support for features like VFIO passthrough. The IOMMU emulation 37 enable features like KVM VFIO passthrough with irqbypass. Until the kernel support 41 The current Linux kernel support will use the IOMMU device to create IOMMU groups 68 use the riscv-iommu-pci device with the existing kernel support we need to emulate 80 - "intremap": enable/disable MSI support 81 - "ats": enable ATS support 83 - "s-stage": enable s-stage support 84 - "g-stage": enable g-stage support [all …]
|
/qemu/docs/ |
H A D | bypass-iommu.txt | 7 devices in the system can only support go through vIOMMU or not, which 8 is not flexible. We introduce this bypass iommu property to support 22 The bypass iommu feature support PXB host bridge and default main host 26 on AArch64. Other machine types do not support bypass iommu for default 77 - Arm SMMUv3 support 80 - X86 IOMMU support 81 To support Intel iommu, we traverse all PCI host bridge and get information 83 explicit device scope info. To support AMD iommu, add check of bypass iommu
|
H A D | pcie_sriov.txt | 1 PCI SR/IOV EMULATION SUPPORT 12 to support SR/IOV. 17 implementing support for two types of device classes; the "normal" physical device 33 1) To enable SR/IOV support in the PF, it must be a PCI Express device so 38 which is necessary to support more than 7 functions, or 93 enabling. Support for this was added in kernel v.3.8, so not all drivers 94 support it yet.
|
/qemu/docs/about/ |
H A D | build-platforms.rst | 6 QEMU aims to support building and executing on multiple host OS 21 support targets, QEMU considers only the version number, and assumes the 25 support for those backports, unless the feature is auto-detectable in a 62 ``--enable-tcg-interpreter`` option to enable the TCI support, but note that 64 requires host-specific support for signal handling, therefore TCI won't help 73 The project aims to support the most recent major version at all times for 74 up to five years after its initial release. Support 76 version is released or when the vendor itself drops support, whichever comes 96 Distributions with long-term support often provide multiple versions 97 of the Python runtime. While QEMU will initially aim to support the [all …]
|
H A D | deprecated.rst | 66 topology parameter as "1", which is meaningless. So support for this kind of 78 ever needed to support ancient kernels on some old board types 81 ``param_struct`` support, so this option has been deprecated and will 202 MIPS moved out of support making it hard to maintain our 204 CI coverage support may bitrot away before the deprecation process 215 Support for 32-bit x86 host deployments is increasingly uncommon in mainstream 217 The QEMU project no longer considers 32-bit x86 support for system emulation to 222 TCG Plugin support not enabled by default on 32-bit hosts (since 9.2) 225 While it is still possible to enable TCG plugin support for 32-bit 234 TCG Plugin support not enabled by default with TCI (since 9.2) [all …]
|
/qemu/docs/system/openrisc/ |
H A D | emulation.rst | 1 OpenRISC 1000 CPU architecture support 4 QEMU's TCG emulation includes support for the OpenRISC or1200 implementation of 7 The or1200 cpu also has support for the following instruction subsets: 12 In addition to the instruction subsets the QEMU TCG emulation also has support
|
/qemu/docs/system/ |
H A D | confidential-guest-support.rst | 1 Confidential Guest Support 13 Guests. We use the term "Confidential Guest Support" to distinguish 22 1. Use ``-object`` to create a "confidential guest support" object. The 25 2. Set the ``confidential-guest-support`` machine parameter to the ID of 32 -machine ...,confidential-guest-support=sev0 \
|
/qemu/hw/mem/ |
H A D | cxl_type3_stubs.c | 55 error_setg(errp, "CXL Type 3 support is not compiled in"); in qmp_cxl_inject_poison() 62 error_setg(errp, "CXL Type 3 support is not compiled in"); in qmp_cxl_inject_uncorrectable_errors() 68 error_setg(errp, "CXL Type 3 support is not compiled in"); in qmp_cxl_inject_correctable_error() 79 error_setg(errp, "CXL Type 3 support is not compiled in"); in qmp_cxl_add_dynamic_capacity() 93 error_setg(errp, "CXL Type 3 support is not compiled in"); in qmp_cxl_release_dynamic_capacity()
|
/qemu/hw/ppc/ |
H A D | pef.c | 2 * PEF (Protected Execution Facility) for POWER support 17 #include "system/confidential-guest-support.h" 37 * -machine ...,confidential-guest-support=pef0 50 "KVM implementation does not support Secure VMs (is an ultravisor running?)"); in kvmppc_svm_init() 77 * that don't support this ioctl.
|
H A D | spapr_caps.c | 66 /* Make sure the virtual hardware can support this capability */ 182 /* TODO: We don't support disabling htm yet */ in cap_htm_apply() 186 error_setg(errp, "No Transactional Memory support in TCG"); in cap_htm_apply() 190 "KVM implementation does not support Transactional Memory"); in cap_htm_apply() 201 /* TODO: We don't support disabling vsx yet */ in cap_vsx_apply() 208 error_setg(errp, "VSX support not available"); in cap_vsx_apply() 218 /* TODO: We don't support disabling dfp yet */ in cap_dfp_apply() 222 error_setg(errp, "DFP support not available"); in cap_dfp_apply() 242 warn_report("TCG doesn't support requested feature, cap-cfpc=%s", in cap_safe_cache_apply() 267 warn_report("TCG doesn't support requested feature, cap-sbbc=%s", in cap_safe_bounds_check_apply() [all …]
|
/qemu/tests/qemu-iotests/ |
H A D | 113.out | 5 qemu-img: nbd://example.com: Format driver 'bochs' does not support image creation 9 qemu-img: Format driver 'bochs' does not support image creation 14 qemu-img: Format driver 'IMGFMT' does not support option amendment
|
H A D | 142.out | 74 …e.node-name=file,file.cache.writeback=off: Block protocol 'file' doesn't support the option 'cache… 77 …riteback=off: Could not open backing file: Block format 'qcow2' does not support the option 'cache… 80 …riteback=off: Could not open backing file: Block protocol 'file' doesn't support the option 'cache… 150 …e.node-name=file,file.cache.writeback=off: Block protocol 'file' doesn't support the option 'cache… 153 …riteback=off: Could not open backing file: Block format 'qcow2' does not support the option 'cache… 156 …riteback=off: Could not open backing file: Block protocol 'file' doesn't support the option 'cache… 226 …e.node-name=file,file.cache.writeback=off: Block protocol 'file' doesn't support the option 'cache… 229 …riteback=off: Could not open backing file: Block format 'qcow2' does not support the option 'cache… 232 …riteback=off: Could not open backing file: Block protocol 'file' doesn't support the option 'cache… 302 …e.node-name=file,file.cache.writeback=off: Block protocol 'file' doesn't support the option 'cache… [all …]
|
/qemu/linux-user/ |
H A D | flat.h | 7 * support uClinux flat-format executables. 15 /* QEMU doesn't support bflt shared libraries */ 55 * tools still need this support in the kernel. So this section is 59 * with the format above, except to fix bugs with old format support.
|
/qemu/include/standard-headers/linux/ |
H A D | virtio_bt.h | 9 #define VIRTIO_BT_F_VND_HCI 0 /* Indicates vendor command support */ 10 #define VIRTIO_BT_F_MSFT_EXT 1 /* Indicates MSFT vendor support */ 11 #define VIRTIO_BT_F_AOSP_EXT 2 /* Indicates AOSP vendor support */
|
/qemu/docs/devel/ |
H A D | codebase.rst | 21 - Block devices and `disk images<disk images>` support 25 - `GDB support<GDB usage>` 55 Audio (host) support. 84 eBPF program support in QEMU. `virtio-net RSS<ebpf-rss>` uses it. 88 `VirtFS <https://www.linux-kvm.org/page/VirtFS>`_ support. 90 `GDB <GDB usage>` support. 98 KVM support and user-mode. 121 Network (host) support. 154 Code related to SCSI support, used by SCSI devices. 167 QEMU `system mode <System emulation>` implementation (cpu, mmu, boot support). [all …]
|
/qemu/docs/devel/migration/ |
H A D | vfio.rst | 16 support by reporting the VFIO_MIGRATION_PRE_COPY flag in the 26 To support migration of multiple devices that might do P2P transactions between 33 All the devices that support P2P migration are first transitioned to the P2P 39 support P2P migration. Single VFIO device migration is allowed regardless of 40 P2P migration support. 134 IOMMU support for dirty page tracking. For this reason, all pages are 169 support it is similar, except that the relevant states for precopy and P2P are 249 attempted in configurations that otherwise support it.
|
/qemu/include/hw/intc/ |
H A D | arm_gicv3_common.h | 2 * ARM GIC support 94 * If the CPU doesn't support EL3 then the G1 element is unused. 100 * not have security support enabled, because security can be disabled 113 * (If the CPU or the GIC, respectively, don't support the Security 177 * virtualization support is not implemented. 204 * Whether the CPU interface has NMI support (FEAT_GICv3_NMI). The 205 * CPU interface may support NMIs even when the GIC proper (what the 241 int dev_fd; /* kvm device fd if backed by kvm vgic support */
|
/qemu/tests/functional/ |
H A D | test_aarch64_virt_gpu.py | 3 # Functional tests for the various graphics modes we can support. 70 self.skipTest("No blob support for virtio-gpu") 72 self.skipTest("No venus support for virtio-gpu") 76 self.skipTest("egl-headless support is not available") 78 self.skipTest("dbus display support is not available")
|