| /openbmc/qemu/docs/ |
| H A D | qemupciserial.inf | 1 ; qemupciserial.inf for QEMU, based on MSPORTS.INF
21 Provider=%QEMU%
26 %QEMU%=QEMU,NTx86,NTAMD64
28 [QEMU.NTx86]
29 %QEMU-PCI_SERIAL_1_PORT%=ComPort_inst1, PCI\VEN_1B36&DEV_0002
30 %QEMU-PCI_SERIAL_2_PORT%=ComPort_inst2, PCI\VEN_1B36&DEV_0003
31 %QEMU-PCI_SERIAL_4_PORT%=ComPort_inst4, PCI\VEN_1B36&DEV_0004
33 [QEMU.NTAMD64]
34 %QEMU-PCI_SERIAL_1_PORT%=ComPort_inst1, PCI\VEN_1B36&DEV_0002
35 %QEMU-PCI_SERIAL_2_PORT%=ComPort_inst2, PCI\VEN_1B36&DEV_0003
[all …]
|
| H A D | spice-port-fqdn.txt | 7 The following fqdn names are reserved by the QEMU project:
10 QEMU human monitor
13 QEMU control monitor
16 QEMU virtual serial port
19 QEMU debug console
|
| /openbmc/qemu/tests/docker/dockerfiles/ |
| H A D | debian-bootstrap.pre | 100 QEMU=qemu-i386
103 QEMU=qemu-arm
106 QEMU=qemu-aarch64
109 QEMU=qemu-ppc
112 QEMU=qemu-ppc64le
115 QEMU=qemu-s390x
118 QEMU=qemu-${DEB_ARCH}
121 if [ ! -e "${BINFMT_DIR}/$QEMU" ]; then
122 echo "No binfmt_misc rule to run $QEMU, can't bootstrap" >&2
|
| /openbmc/openbmc/poky/documentation/dev-manual/ |
| H A D | qemu.rst | 4 Using the Quick EMUlator (QEMU)
7 The Yocto Project uses an implementation of the Quick EMUlator (QEMU)
10 EMUlator (QEMU) and other QEMU information helpful for development
16 Within the context of the Yocto Project, QEMU is an emulator and
19 QEMU is useful for running and testing images and applications on
21 Among other things, the Yocto Project uses QEMU to run automated Quality
26 This implementation is not the same as QEMU in general.
29 implementation of QEMU.
31 For official information and documentation on QEMU in general, see the
34 - `QEMU Website <https://wiki.qemu.org/Main_Page>`__\ *:* The official
[all …]
|
| /openbmc/qemu/docs/system/ |
| H A D | security.rst | 7 This chapter explains the security requirements that QEMU is designed to meet
8 and principles for securely deploying QEMU.
13 QEMU supports many different use cases, some of which have stricter security
50 QEMU to provide guest isolation or any security guarantees.
67 QEMU presents an attack surface to the guest in the form of emulated devices.
68 The guest must not be able to gain control of QEMU. Bugs in emulated devices
69 could allow malicious guests to gain code execution in QEMU. At this point the
71 QEMU process on the host.
82 the privileges necessary for its function. In the case of QEMU this means that
85 The QEMU process should not have access to any resources that are inaccessible
[all …]
|
| H A D | cpu-hotplug.rst | 11 (1) Launch QEMU as follows (note that the "maxcpus" is mandatory to
20 to connect to the just-launched QEMU::
24 (QEMU)
28 (QEMU) query-hotpluggable-cpus
56 (QEMU)
65 (QEMU) device_add id=cpu-2 driver=IvyBridge-IBRS-x86_64-cpu socket-id=0 core-id=1 thread-id=0
79 (QEMU)
84 (QEMU) query-cpus-fast
115 (QEMU)
122 (QEMU) device_del id=cpu-2
[all …]
|
| H A D | target-openrisc.rst | 6 QEMU can emulate 32-bit OpenRISC CPUs using the ``qemu-system-or1k`` executable.
10 (the original OpenRISC instruction level simulator) which QEMU supports. For
11 this reason QEMU does not need to support many different boards to support the
14 The OpenRISC CPU supported by QEMU is the ``or1200``, it supports an MMU and can
20 For QEMU's OpenRISC system emulation, you must specify which board model you
25 will boot on any of the QEMU machines. To do this one would compile all required
26 drivers into the kernel. This is possible because QEMU will create a device tree
27 structure that describes the QEMU machine and pass a pointer to the structure to
33 want to boot with QEMU, check whether QEMU lists that machine in its ``-machine
36 on QEMU. (You might be able to extract the filesystem and use that with a
[all …]
|
| H A D | multi-process.rst | 1 .. _Multi-process QEMU:
3 Multi-process QEMU
18 Multi-process QEMU requires an orchestrator to launch.
29 - It then launches QEMU and specifies the other socket as an option
34 - QEMU can enter remote process mode by using the "remote" machine
40 - The remaining options are no different from how one launches QEMU with
52 * QEMU:
54 - Since parts of the RAM are shared between QEMU & remote process, a
64 - Example commandline for QEMU is as follows:
|
| H A D | secrets.rst | 3 Providing secret data to QEMU
6 There are a variety of objects in QEMU which require secret data to be provided
10 QEMU has a general purpose mechanism for providing secret data to QEMU in a
31 For the convenience of people debugging / developing with QEMU, it is possible
68 format and have QEMU decode to get the raw bytes before use:
76 have its user/group ownership set to the same account that the QEMU process
78 the file should be labelled to only grant access to the specific QEMU process
101 real secret that can now be safely passed to QEMU inline as cipher text
119 The earlier mechanisms described are platform agnostic. If using QEMU on a Linux
120 host, it is further possible to pass secrets to QEMU using the Linux keyring:
[all …]
|
| /openbmc/qemu/tests/qemu-iotests/tests/ |
| H A D | write-zeroes-unmap | 54 | $QEMU -monitor stdio -drive if=none,file=$TEST_IMG,format=$IMGFMT \
64 | $QEMU -monitor stdio -drive if=none,file=$TEST_IMG,format=$IMGFMT \
75 | $QEMU -monitor stdio -drive if=none,file=$TEST_IMG,format=$IMGFMT \
85 | $QEMU -monitor stdio -drive if=none,file=$TEST_IMG,format=$IMGFMT,discard=off \
95 | $QEMU -monitor stdio -drive if=none,file=$TEST_IMG,format=$IMGFMT,detect-zeroes=on \
105 … | $QEMU -monitor stdio -drive if=none,file=$TEST_IMG,format=$IMGFMT,detect-zeroes=on,discard=on \
115 | $QEMU -monitor stdio -drive if=none,file=$TEST_IMG,format=$IMGFMT,discard=on \
125 | $QEMU -monitor stdio -drive if=none,file=$TEST_IMG,format=$IMGFMT,discard=on \
|
| /openbmc/qemu/tests/tcg/multiarch/ |
| H A D | Makefile.target | 29 $(call run-test,$<, $(QEMU) $(QEMU_OPTS) $<)
58 $(call run-test, test-mmap, $(QEMU) $<, $< (default))
66 --qemu $(QEMU) --qargs "$(QEMU_OPTS)" \
73 --qemu $(QEMU) --qargs "$(QEMU_OPTS)" \
80 --qemu $(QEMU) --qargs "$(QEMU_OPTS)" \
87 --qemu $(QEMU) --qargs "$(QEMU_OPTS)" \
94 --qemu $(QEMU) --qargs "$(QEMU_OPTS)" \
101 --qemu $(QEMU) --qargs "$(QEMU_OPTS)" \
108 --qemu $(QEMU) --qargs "$(QEMU_OPTS)" \
115 --qemu $(QEMU) --qargs "$(QEMU_OPTS)" \
[all …]
|
| /openbmc/qemu/python/ |
| H A D | PACKAGE.rst | 1 QEMU Python Tooling
4 This package provides QEMU tooling used by the QEMU project to build,
5 configure, and test QEMU. It is not a fully-fledged SDK and it is subject
13 facilities for launching and managing QEMU processes. Refer to each
22 the QEMU source tree. Contributions are welcome and follow the `QEMU
25 sending patches to the QEMU development mailing list.
31 Please report bugs on the `QEMU issue tracker
|
| /openbmc/qemu/docs/devel/ |
| H A D | multi-process.rst | 1 Multi-process QEMU
6 This is the design document for multi-process QEMU. It does not
15 QEMU is often used as the hypervisor for virtual machines running in the
22 QEMU can be susceptible to security attacks because it is a large,
24 Many of these features can be configured out of QEMU, but even a reduced
25 configuration QEMU has a large amount of code a guest can potentially
26 attack. Separating QEMU reduces the attack surface by aiding to
30 QEMU services
33 QEMU can be broadly described as providing three main services. One is a
40 A multi-process QEMU
[all …]
|
| /openbmc/qemu/docs/specs/ |
| H A D | ppc-spapr-xive.rst | 10 A QEMU ``pseries`` machine (which is PAPR compliant) using POWER9
18 It is also referred as *XICS* in QEMU.
36 QEMU advertises the supported interrupt modes in the device tree
56 and QEMU are also negotiated. Depending on the version of the host
57 kernel, KVM will advertise the XIVE capability to QEMU or not.
61 without XIVE KVM support, QEMU will use the emulated XIVE device as a
66 hypervisor will not advertise the KVM capability and QEMU will use the
100 xive QEMU error(3) QEMU error(3) QEMU error(3)
104 (3) QEMU fails at CAS with ``Guest requested unavailable interrupt
121 dual (default) XIVE emul.(1) XIVE emul. QEMU error (2)
[all …]
|
| H A D | acpi_nvdimm.rst | 1 QEMU<->ACPI BIOS NVDIMM interface
4 QEMU supports NVDIMM via ACPI. This document describes the basic concepts of
5 NVDIMM ACPI and the interface between QEMU and the ACPI BIOS.
79 QEMU NVDIMM Implementation
82 QEMU uses 4 bytes IO Port starting from 0x0a18 and a RAM-based memory page
86 QEMU uses BIOS Linker/loader feature to ask BIOS to allocate a memory
91 method and QEMU. If ACPI has control, this pages is owned by ACPI which
92 writes _DSM input data to it, otherwise, it is owned by QEMU which
100 The handle is completely QEMU internal thing, the values in
107 - 0x10000 is reserved for QEMU internal DSM function called on
[all …]
|
| H A D | acpi_hest_ghes.rst | 59 (1) QEMU generates the ACPI HEST table. This table goes in the current
63 (2) A new fw_cfg blob called "etc/hardware_errors" is introduced. QEMU
74 (4) QEMU generates the ACPI linker/loader script for the firmware. The
78 (5) QEMU generates N ADD_POINTER commands, which patch addresses in the
82 (6) QEMU generates N ADD_POINTER commands, which patch addresses in the
86 (7) QEMU generates N ADD_POINTER commands for the firmware, which patch
90 (8) QEMU defines a third and write-only fw_cfg blob which is called
92 the guest-side allocation addresses to QEMU. The "etc/hardware_errors_addr"
93 blob contains a 8-byte entry. QEMU generates a single WRITE_POINTER command
97 (9) When QEMU gets a SIGBUS from the kernel, QEMU writes CPER into corresponding
[all …]
|
| /openbmc/qemu/ |
| H A D | README.rst | 2 QEMU README
5 QEMU is a generic and open source machine & userspace emulator and
8 QEMU is capable of emulating a complete machine in software without any
10 it achieves very good performance. QEMU can also integrate with the Xen
12 hypervisor to manage the CPU. With hypervisor support, QEMU can achieve
13 near native performance for CPUs. When QEMU emulates CPUs directly it is
17 QEMU is also capable of providing userspace API virtualization for Linux
23 QEMU aims to fit into a variety of use cases. It can be invoked directly
30 QEMU as a whole is released under the GNU General Public License,
48 QEMU is multi-platform software intended to be buildable on all modern
[all …]
|
| H A D | LICENSE | 1 The QEMU distribution includes both the QEMU emulator and
6 The following points clarify the license of the QEMU emulator:
8 1) The QEMU emulator as a whole is released under the GNU General
11 2) Parts of the QEMU emulator have specific licenses which are compatible
25 4) QEMU is a trademark of Fabrice Bellard.
27 Fabrice Bellard and the QEMU team
|
| /openbmc/qemu/docs/system/devices/ |
| H A D | canokey.rst | 3 CanoKey QEMU
24 In QEMU, yet another CanoKey virt-card is implemented.
25 CanoKey QEMU exposes itself as a USB device to the guest OS.
31 CanoKey QEMU provides much convenience for debugging:
35 * CanoKey QEMU supports trace event thus event
36 * QEMU USB stack supports pcap thus USB packet between the guest
52 libcanokey-qemu is required to use CanoKey QEMU.
78 Using CanoKey QEMU
81 CanoKey QEMU stores all its data on a file of the host specified by the argument
91 afterwards CanoKey QEMU would just read this file.
[all …]
|
| H A D | net.rst | 6 QEMU can simulate several network cards (e.g. PCI or ISA cards on the PC
11 guest instances running in another QEMU process (e.g. by using the
17 This is the standard way to connect QEMU to a real network. QEMU adds a
37 TAP-Win32. But it is not included in standard QEMU for Windows, so you
45 option is specified), QEMU uses a completely user mode network stack
56 The QEMU VM behaves as if it was behind a firewall which blocks all
58 configure the network in the QEMU VM. The DHCP server assign addresses
63 10.0.2.x from the QEMU virtual DHCP server.
67 shall work, however. If you're using QEMU on Linux >= 3.0, it can use
83 QEMU can simulate several hubs. A hub can be thought of as a virtual
[all …]
|
| /openbmc/qemu/tests/qemu-iotests/ |
| H A D | 186.out | 7 QEMU X.Y.Z monitor - type 'help' for more information
15 QEMU X.Y.Z monitor - type 'help' for more information
23 QEMU X.Y.Z monitor - type 'help' for more information
31 QEMU X.Y.Z monitor - type 'help' for more information
39 QEMU X.Y.Z monitor - type 'help' for more information
47 QEMU X.Y.Z monitor - type 'help' for more information
58 QEMU X.Y.Z monitor - type 'help' for more information
66 QEMU X.Y.Z monitor - type 'help' for more information
74 QEMU X.Y.Z monitor - type 'help' for more information
82 QEMU X.Y.Z monitor - type 'help' for more information
[all …]
|
| /openbmc/qemu/docs/interop/ |
| H A D | live-block-operations.rst | 13 QEMU Block Layer currently (as of QEMU 2.9) supports four major kinds of
25 The file ``qapi/block-core.json`` in the QEMU source tree has the
26 canonical QEMU API (QAPI) schema documentation for the QMP
40 (Live QEMU)
50 [B]. And live QEMU is currently writing to image [B], consequently, it
77 QEMU block layer supports.
85 (a) QEMU rewrites the backing chain to remove
89 (b) the streamed file *itself* won't be removed by QEMU,
99 chain). Since QEMU 2.0, this includes "active ``block-commit``"
105 (a) QEMU rewrites the backing chain to remove reference
[all …]
|
| /openbmc/qemu/docs/about/ |
| H A D | build-platforms.rst | 6 QEMU aims to support building and executing on multiple host OS
9 minimum required versions of 3rd party software QEMU depends on. The
14 If a platform is not listed here, it does not imply that QEMU won't
21 support targets, QEMU considers only the version number, and assumes the
24 software in their distro, QEMU upstream code will not add explicit
57 Other host architectures are not supported. It is possible to build QEMU system
60 this is very slow and is not recommended for normal use. QEMU user emulation
94 of the Python runtime. While QEMU will initially aim to support the
98 option of the ``configure`` script to point QEMU to a supported
101 As of QEMU |version|, the minimum supported version of Python is 3.7.
[all …]
|
| /openbmc/u-boot/board/emulation/ |
| H A D | Kconfig | 11 bool "QEMU x86"
13 This is the QEMU emulated x86 board. U-Boot supports running
15 There are two types of x86 boards supported by QEMU which are
16 supported by U-Boot. They are via QEMU '-M pc', an i440FX/PIIX
20 bool "QEMU x86 64-bit"
22 This is the QEMU emulated x86 64-bit board. With this config
|
| /openbmc/qemu/docs/devel/migration/ |
| H A D | CPR.rst | 5 VM is migrated to a new QEMU instance on the same host. It is
7 that run the VM, such as QEMU or even the host kernel. At this time,
10 Because QEMU is restarted on the same host, with access to the same
13 guest block devices between quitting old QEMU and starting new QEMU.
21 In this mode, QEMU stops the VM, and writes VM state to the migration
22 URI, which will typically be a file. After quitting QEMU, the user
23 resumes by running QEMU with the ``-incoming`` option. Because the
24 old and new QEMU instances are not active concurrently, the URI cannot
32 software before restarting QEMU and resuming the VM. Further, if
34 then the user may reboot to a new host kernel before restarting QEMU.
[all …]
|