| /qemu/docs/devel/ |
| H A D | kconfig.rst | 13 SCSI adapters. Arm, s390 and x86 boards can all present a virtio-blk
16 Each QEMU target enables a subset of the boards, devices and buses that
21 QEMU uses a simple domain-specific language to describe the dependencies
24 * new targets and boards can be added without knowing in detail the
27 include all the required dependencies and all the devices that the
31 of boards or devices. For example, by default most targets will include
32 all emulated PCI devices that QEMU supports, but the build process is
36 This domain-specific language is based on the Kconfig language that
41 is instead specified in per-target files under the ``configs/``
44 QEMU; the default configuration that QEMU ships with should be okay in
[all …]
|
| /qemu/docs/system/s390x/ |
| H A D | bootdevices.rst | 1 Boot devices on s390x
5 --------------------------------
9 in s390x-speak -- IPL means "Initial Program Load").
15 qemu-system-s390x -drive if=none,id=dr1,file=guest.qcow2 \
16 -device virtio-blk,drive=dr1,bootindex=1
18 Multiple devices may have a bootindex. The lowest bootindex is assigned to the
21 remaining boot devices to try.
23 For booting from a CD-ROM ISO image (which needs to include El-Torito boot
24 information in order to be bootable), it is recommended to specify a ``scsi-cd``
27 qemu-system-s390x -blockdev file,node-name=c1,filename=... \
[all …]
|
| H A D | css.rst | 5 functionless) channel paths, and channel devices (virtio-ccw, 3270, and
6 devices passed via vfio-ccw). It supports multiple subchannel sets (MSS) and
7 multiple channel subsystems extended (MCSS-E).
9 All channel devices support the ``devno`` property, which takes a parameter
12 The default channel subsystem image id (``<cssid>``) is ``0xfe``. Devices in
14 enable MCSS-E. Note that devices with a different cssid will not be visible
15 if the guest OS does not enable MCSS-E (which is true for all supported guest
18 Supported values for the subchannel set id (``<ssid>``) range from ``0-3``.
19 Devices with a ssid that is not ``0`` will not be visible if the guest OS
24 The device number can range from ``0-0xffff``.
[all …]
|
| H A D | vfio-ap.rst | 7 ------------
11 These AP devices provide cryptographic functions to all CPUs assigned to a
19 -------------------------
51 An AP queue is the means by which an AP command-request message is sent to an
57 which the AP command-request message is to be sent for processing.
63 * NQAP: to enqueue an AP command-request message to a queue
64 * DQAP: to dequeue an AP command-reply message from a queue
73 ----------------------------------------------
84 an APID from 0-255. If a bit is set, the corresponding adapter is valid for
89 corresponds to an AP queue index (APQI) from 0-255. If a bit is set, the
[all …]
|
| /qemu/docs/system/i386/ |
| H A D | microvm.rst | 7 It's a minimalist machine type without ``PCI`` nor ``ACPI`` support,
8 designed for short-lived guests. microvm also establishes a baseline
13 Supported devices
14 -----------------
16 The microvm machine type supports the following devices:
18 - ISA bus
19 - i8259 PIC (optional)
20 - i8254 PIT (optional)
21 - MC146818 RTC (optional)
22 - One ISA serial port (optional)
[all …]
|
| /qemu/docs/ |
| H A D | qdev-device-use.txt | 1 = How to convert to -device & friends =
5 In qdev, each device has a parent bus. Some devices provide one or
7 -device parameter bus.
10 where this address can be configured, devices provide a bus-specific
16 SCSI scsi-id %u
19 virtio-serial-bus nr %u
20 ccid-bus slot %u
23 Example: device i440FX-pcihost is on the root bus, and provides a PCI
24 bus named pci.0. To put a FOO device into its slot 4, use -device
25 FOO,bus=/i440FX-pcihost/pci.0,addr=4. The abbreviated form bus=pci.0
[all …]
|
| H A D | pcie_pci_bridge.txt | 6 PCIE-to-PCI bridge is a new method for legacy PCI
9 Previously Intel DMI-to-PCI bridge was used for this purpose.
10 But due to its strict limitations - no support of hot-plug,
11 no cross-platform and cross-architecture support - a new generic
12 PCIE-to-PCI bridge should now be used for any legacy PCI device usage
15 This generic PCIE-PCI bridge is a cross-platform device,
16 can be hot-plugged into appropriate root port (requires additional actions,
17 see 'PCIE-PCI bridge hot-plug' section),
18 and supports devices hot-plug into the bridge itself
21 Hot-plug of legacy PCI devices into the bridge
[all …]
|
| H A D | nvdimm.txt | 11 -----------
14 backend (i.e. memory-backend-file and memory-backend-ram). A simple
18 -machine pc,nvdimm=on
19 -m $RAM_SIZE,slots=$N,maxmem=$MAX_SIZE
20 -object memory-backend-file,id=mem1,share=on,mem-path=$PATH,size=$NVDIMM_SIZE,readonly=off
21 -device nvdimm,id=nvdimm1,memdev=mem1,unarmed=off
25 - the "nvdimm" machine option enables vNVDIMM feature.
27 - "slots=$N" should be equal to or larger than the total amount of
28 normal RAM devices and vNVDIMM devices, e.g. $N should be >= 2 here.
30 - "maxmem=$MAX_SIZE" should be equal to or larger than the total size
[all …]
|
| H A D | pcie.txt | 7 devices in PCI Express based machines and explains the reasoning behind
25 QEMU does not have a clear socket-device matching mechanism
34 PCI Express devices should be plugged only into PCI Express Root Ports and
39 Place only the following kinds of devices directly on the Root Complex:
40 (1) PCI Devices (e.g. network card, graphics card, IDE controller),
41 not controllers. Place only legacy PCI devices on
43 Note: Integrated Endpoints are not hot-pluggable.
45 Although the PCI Express spec does not forbid PCI Express devices as
47 devices with the Root Complex. Guest OSes are suspected to behave
48 strangely when PCI Express devices are integrated
[all …]
|
| /qemu/docs/system/ |
| H A D | introduction.rst | 7 ---------------------------
10 memory and emulated devices) to run a guest OS. It supports a number
14 .. list-table:: Supported Accelerators
15 :header-rows: 1
17 * - Accelerator
18 - Host OS
19 - Host Architectures
20 * - KVM
21 - Linux
22 - Arm (64 bit only), MIPS, PPC, RISC-V, s390x, x86
[all …]
|
| H A D | cpu-models-x86.rst.inc | 31 features, to alter what is presented to the guest by default.
51 lists the long term stable CPU model versions (eg Haswell-v4).
56 .. _ABI compatibility levels: https://gitlab.com/x86-psABIs/x86-64-ABI/
58 .. csv-table:: x86-64 ABI compatibility levels
59 :file: cpu-models-x86-abi.csv
61 :header-rows: 1
77 ``SierraForest``, ``SierraForest-v2``
78 Intel Xeon Processor (SierraForest, 2024), SierraForest-v2 mitigates
81 ``GraniteRapids``, ``GraniteRapids-v2``
84 ``Cascadelake-Server``, ``Cascadelake-Server-noTSX``
[all …]
|
| H A D | device-url-syntax.rst.inc | 3 devices, QEMU can also use networked resources such as iSCSI devices.
12 "iscsi://<target-ip>[:<port>]/<target-iqn>/<lun>"
14 By default qemu will use the iSCSI initiator-name
15 'iqn.2008-11.org.linux-kvm[:<name>]' but this can also be set from
20 session. The timeout is specified in seconds. The default is 0 which
24 Example (without authentication):
26 .. parsed-literal::
28 |qemu_system| -iscsi initiator-name=iqn.2001-04.com.example:my-initiator \\
29 -cdrom iscsi://192.0.2.1/iqn.2001-04.com.example/2 \\
30 -drive file=iscsi://192.0.2.1/iqn.2001-04.com.example/1
[all …]
|
| /qemu/docs/system/riscv/ |
| H A D | virt.rst | 8 real-world hardware.
10 Supported devices
11 -----------------
13 The ``virt`` machine supports the following devices:
17 * Platform-Level Interrupt Controller (PLIC)
22 * 8 virtio-mmio transport devices
26 The hypervisor extension has been enabled for the default CPU, so virtual
27 machines with hypervisor extension can simply be used without explicitly
31 ----------------------------------
34 which it passes to the guest, if there is no ``-dtb`` option. This provides
[all …]
|
| /qemu/docs/system/devices/ |
| H A D | usb.rst | 2 -------------
5 plug virtual USB devices or real host USB devices (only works with
7 connect virtual USB hubs as necessary to connect multiple USB devices.
16 more virtualization-friendly when compared to EHCI and UHCI, thus XHCI
21 |qemu_system| -device qemu-xhci
23 XHCI supports USB 1.1, USB 2.0 and USB 3.0 devices, so this is the
26 need to use the bus= parameter when adding USB devices.
32 The QEMU EHCI Adapter supports USB 2.0 devices. It can be used either
34 devices. The companion controller setup is more convenient to use
36 1.1 devices. See next section for details.
[all …]
|
| /qemu/docs/devel/migration/ |
| H A D | qpl-compression.rst | 4 The Intel Query Processing Library (Intel ``QPL``) is an open-source library to
8 The ``QPL`` compression relies on Intel In-Memory Analytics Accelerator(``IAA``)
21 +----------------+ +------------------+
22 | MultiFD Thread | |accel-config tool |
23 +-------+--------+ +--------+---------+
27 +-------+--------+ | Setup IAA
29 +-------+---+----+ |
31 | +-------------+-------+
33 | Devices +-----+-----+
35 | +-----+-----+
[all …]
|
| H A D | main.rst | 15 the same devices that the one it was saved (this last requirement can
41 - tcp migration: do the migration using tcp sockets
42 - unix migration: do the migration using unix sockets
43 - exec migration: do the migration using the stdin/stdout through a process.
44 - fd migration: do the migration using a file descriptor that is
46 - file migration: do the migration using a file that is passed to QEMU
48 application to add its own metadata to the start of the file without
54 (see add-fd QMP command documentation). This method allows a
59 - the fdset must contain two file descriptors that are not
61 - if the direct-io capability is to be used, exactly one of the
[all …]
|
| /qemu/docs/devel/testing/ |
| H A D | fuzzing.rst | 5 This document describes the virtual-device fuzzing infrastructure in QEMU and
9 ------
16 is an *in-process* fuzzer. For the developer, this means that it is their
17 responsibility to ensure that state is reset between fuzzing-runs.
20 --------------------
24 Here, enable-asan and enable-ubsan are optional but they allow us to reliably
25 detect bugs such as out-of-bounds accesses, uses-after-free, double-frees
28 CC=clang-8 CXX=clang++-8 /path/to/configure \
29 --enable-fuzzing --enable-asan --enable-ubsan
33 make qemu-fuzz-i386
[all …]
|
| /qemu/.gitlab-ci.d/custom-runners/ |
| H A D | ubuntu-22.04-aarch64.yml | 1 # All ubuntu-22.04 jobs should run successfully in an environment
2 # setup by the scripts/ci/setup/ubuntu/build-environment.yml task
5 ubuntu-22.04-aarch64-all-linux-static:
10 - ubuntu_22.04
11 - aarch64
13 - if: '$CI_PROJECT_NAMESPACE == "qemu-project" && $CI_COMMIT_BRANCH =~ /^staging/'
14 - if: "$AARCH64_RUNNER_AVAILABLE"
16 - mkdir build
17 - cd build
18 # Disable -static-pie due to build error with system libc:
[all …]
|
| /qemu/hw/ppc/ |
| H A D | spapr_pci_vfio.c | 4 * Copyright (c) 2011-2014 Alexey Kardashevskiy, IBM Corporation.
12 * but WITHOUT ANY WARRANTY; without even the implied warranty of
24 #include "hw/pci-host/spapr.h"
27 #include "hw/vfio/vfio-container.h"
28 #include "qemu/error-report.h"
38 * As of 2016-03-04 (linux-4.5) the host kernel EEH/VFIO in vfio_eeh_container_ok()
42 * iterate across all groups in the container, without any logic in vfio_eeh_container_ok()
52 if (QLIST_EMPTY(&container->group_list)) { in vfio_eeh_container_ok()
56 if (QLIST_NEXT(QLIST_FIRST(&container->group_list), container_next)) { in vfio_eeh_container_ok()
74 return -EPERM; in vfio_eeh_container_op()
[all …]
|
| /qemu/docs/about/ |
| H A D | removed-features.rst | 10 --------------------------------------
12 ``-hdachs`` (removed in 2.12)
15 The geometry defined by ``-hdachs c,h,s,t`` should now be specified via
16 ``-device ide-hd,drive=dr,cyls=c,heads=h,secs=s,bios-chs-trans=t``
17 (together with ``-drive if=none,id=dr,...``).
19 ``-net channel`` (removed in 2.12)
22 This option has been replaced by ``-net user,guestfwd=...``.
24 ``-net dump`` (removed in 2.12)
27 ``-net dump[,vlan=n][,file=filename][,len=maxlen]`` has been replaced by
28 ``-object filter-dump,id=id,netdev=dev[,file=filename][,maxlen=maxlen]``.
[all …]
|
| /qemu/system/ |
| H A D | bootdevice.c | 8 * in the Software without restriction, including without limitation the rights
16 * THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
29 #include "qemu/error-report.h"
31 #include "hw/qdev-core.h"
73 void validate_bootdevices(const char *devices, Error **errp) in validate_bootdevices() argument
79 for (p = devices; *p != '\0'; p++) { in validate_bootdevices()
80 /* Allowed boot devices are: in validate_bootdevices()
81 * a-b: floppy disk drives in validate_bootdevices()
82 * c-f: IDE disk drives in validate_bootdevices()
83 * g-m: machine implementation dependent drives in validate_bootdevices()
[all …]
|
| /qemu/hw/block/ |
| H A D | pflash_cfi01.c | 13 * but WITHOUT ANY WARRANTY; without even the implied warranty of
24 * - flash read
25 * - flash write
26 * - flash ID read
27 * - sector erase
28 * - CFI queries
42 #include "hw/qdev-properties.h"
43 #include "hw/qdev-properties-system.h"
44 #include "system/block-backend.h"
46 #include "qemu/error-report.h"
[all …]
|
| /qemu/docs/specs/ |
| H A D | ppc-spapr-xive.rst | 8 directly to virtual processors without hypervisor assistance.
13 - *Legacy Compatibility Mode*
16 functionality to PAPR+ Version 2.7. This is the default mode
20 - *XIVE native exploitation mode*
34 ---------------
37 property ``ibm,arch-vec-5-platform-support`` in byte 23 and the OS
38 Selection for XIVE is indicated in the ``ibm,architecture-vec-5``
43 ``ic-mode`` which can be set on the command line. It can take the
45 default mode. ``dual`` means that both modes XICS **and** XIVE are
53 ---------------
[all …]
|
| /qemu/hw/i386/xen/ |
| H A D | xen_platform.c | 4 * Copyright (c) 2003-2004 Intel Corp.
9 * in the Software without restriction, including without limitation the rights
17 * THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
34 #include "system/block-backend.h"
35 #include "qemu/error-report.h"
74 #define TYPE_XEN_PLATFORM "xen-platform"
82 if (val == '\n' || s->log_buffer_off == sizeof(s->log_buffer) - 1) { in OBJECT_DECLARE_SIMPLE_TYPE()
84 s->log_buffer[s->log_buffer_off] = 0; in OBJECT_DECLARE_SIMPLE_TYPE()
85 trace_xen_platform_log(s->log_buffer); in OBJECT_DECLARE_SIMPLE_TYPE()
86 s->log_buffer_off = 0; in OBJECT_DECLARE_SIMPLE_TYPE()
[all …]
|
| /qemu/ |
| H A D | qemu-options.hx | 14 "-h or -help display this help and exit\n", QEMU_ARCH_ALL)
16 ``-h``
21 "-version display version information and exit\n", QEMU_ARCH_ALL)
23 ``-version``
28 "-machine [type=]name[,prop[=value][,...]]\n"
29 " selects emulated machine ('-machine help' for list)\n"
31 " supported accelerators are kvm, xen, hvf, nvmm, whpx or tcg (default: tcg)\n"
32 " vmport=on|off|auto controls emulation of vmport (default: auto)\n"
33 " dump-guest-core=on|off include guest memory in a core dump (default=on)\n"
34 " mem-merge=on|off controls memory merge support (default: on)\n"
[all …]
|