| /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
33 [QEMU.NTAMD64]
99 QEMU="QEMU"
100 QEMU-PCI_SERIAL_1_PORT="1x QEMU PCI Serial Card"
101 QEMU-PCI_SERIAL_2_PORT="2x QEMU PCI Serial Card"
[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/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.
71 QEMU process on the host.
97 the QEMU process can then begin invoking host system calls.
112 The fundamental isolation mechanism is that QEMU processes must run as
116 unprivileged QEMU process access to host devices without running QEMU as root.
124 needed by QEMU.
130 resources unavailable to QEMU. A namespaced QEMU process is restricted to only
[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)
79 (QEMU)
84 (QEMU) query-cpus-fast
117 (QEMU)
124 (QEMU) device_del id=cpu-2
134 (QEMU)
[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 | barrier.rst | 1 QEMU Barrier Client
4 Generally, mouse and keyboard are grabbed through the QEMU video
12 The QEMU Barrier client avoids this by implementing directly the Barrier
13 protocol into QEMU.
19 This protocol is enabled by adding an input-barrier object to QEMU.
28 The object can be added on the QEMU command line, for instance with::
39 If the Barrier server is stopped QEMU needs to be reconnected manually,
|
| /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/openbmc/poky/documentation/dev-manual/ |
| H A D | qemu.rst | 4 Using the Quick EMUlator (QEMU)
10 EMUlator (QEMU) and other QEMU information helpful for development
29 implementation of QEMU.
40 Running QEMU
43 To use QEMU, you need to have QEMU installed and initialized as well as
47 #. *Install QEMU:* QEMU is made available with the Yocto Project a
80 QEMU.
228 QEMU CPU Compatibility Under KVM
248 QEMU Performance
272 on the QEMU emulator:
[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/tests/tcg/multiarch/ |
| H A D | Makefile.target | 29 $(call run-test,$<, $(QEMU) $(QEMU_OPTS) $<)
63 --qemu $(QEMU) --qargs "$(QEMU_OPTS)" \
70 --qemu $(QEMU) --qargs "$(QEMU_OPTS)" \
77 --qemu $(QEMU) --qargs "$(QEMU_OPTS)" \
84 --qemu $(QEMU) --qargs "$(QEMU_OPTS)" \
91 --qemu $(QEMU) --qargs "$(QEMU_OPTS)" \
98 --qemu $(QEMU) --qargs "$(QEMU_OPTS)" \
105 --qemu $(QEMU) --qargs "$(QEMU_OPTS)" \
112 --qemu $(QEMU) --qargs "$(QEMU_OPTS)" \
119 --qemu $(QEMU) --qargs "$(QEMU_OPTS)" \
[all …]
|
| /openbmc/qemu/ |
| 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
|
| 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
30 QEMU as a whole is released under the GNU General Public License,
50 of other UNIX targets. The simple steps to build QEMU are:
85 the QEMU website:
90 The QEMU website is also maintained under source control.
134 The QEMU project uses GitLab issues to track bugs. Bugs
[all …]
|
| /openbmc/qemu/docs/specs/ |
| 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
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
119 QEMU writes Output Data (based on the offset in the page):
125 4092 bytes, the DSM result filled by QEMU
152 | 5 QEMU | | 4 QEMU | | 3. QEMU |
[all …]
|
| 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
57 kernel, KVM will advertise the XIVE capability to QEMU or not.
100 xive QEMU error(3) QEMU error(3) QEMU error(3)
121 dual (default) XIVE emul.(1) XIVE emul. QEMU error (2)
122 xive XIVE emul.(1) XIVE emul. QEMU error (2)
130 QEMU/KVM incompatibility due to device destruction in reset. QEMU fails
145 dual (default) QEMU error(4) XICS emul. QEMU error(4)
146 xive QEMU error(3) QEMU error(3) QEMU error(3)
[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/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/ |
| H A D | multi-process.rst | 1 Multi-process QEMU
30 QEMU services
40 A multi-process QEMU
43 A multi-process QEMU involves separating QEMU services into separate
74 QEMU device emulation
162 QEMU on cache misses, and in turn receiving flush requests from QEMU
213 backends that QEMU has.
234 communication with QEMU
257 QEMU command line
350 or ports. The QEMU device emulation code uses QEMU's memory region
[all …]
|
| /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
52 libcanokey-qemu is required to use CanoKey QEMU.
78 Using CanoKey QEMU
91 afterwards CanoKey QEMU would just read this file.
96 and find CanoKey QEMU there:
101 Bus 001 Device 002: ID 20a0:42d4 Clay Logic CanoKey QEMU
[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
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
85 example QEMU virtual ethernet cards or virtual Host ethernet devices
[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
40 (Live QEMU)
77 QEMU block layer supports.
161 (QEMU)
313 (QEMU) query-block-jobs
461 (QEMU) query-block-jobs
603 (QEMU) query-block-jobs
696 And start the destination QEMU (we already have the source QEMU running
789 (QEMU) cont
927 (QEMU) quit
[all …]
|
| /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.
22 URI, which will typically be a file. After quitting QEMU, the user
23 resumes by running QEMU with the ``-incoming`` option. Because the
32 software before restarting QEMU and resuming the VM. Further, if
38 ``guest-suspend-ram`` command to the QEMU guest agent. The agent
60 * Quit when QEMU reaches the postmigrate state.
63 * Start QEMU with the ``-incoming defer`` option.
[all …]
|
| /openbmc/qemu/docs/about/ |
| H A D | index.rst | 2 About QEMU
5 QEMU is a generic and open source machine emulator and virtualizer.
7 QEMU can be used in several different ways. The most common is for
14 The second supported way to use QEMU is :ref:`User Mode Emulation`,
15 where QEMU can launch processes compiled for one CPU on another CPU.
18 QEMU also provides a number of standalone :ref:`command line
|