| /qemu/.gitlab-ci.d/ |
| H A D | buildtest.yml | 4 build-system-alpine:
16 check-system-alpine:
25 avocado-system-alpine:
35 build-system-ubuntu:
47 check-system-ubuntu:
56 avocado-system-ubuntu:
66 build-system-debian:
79 check-system-debian:
110 build-system-fedora:
123 check-system-fedora:
[all …]
|
| H A D | crossbuilds.yml | 18 cross-arm64-system:
63 cross-mipsel-system:
77 cross-mips64el-system:
91 cross-ppc64el-system:
116 cross-riscv64-system:
132 cross-s390x-system:
162 cross-win64-system:
|
| /qemu/docs/system/ |
| H A D | target-mips.rst | 7 endian options, ``qemu-system-mips``, ``qemu-system-mipsel``
8 ``qemu-system-mips64`` and ``qemu-system-mips64el``. Five different
22 - Core board with MIPS 24Kf CPU and Galileo system controller
67 - Bonito64 system controller as North Bridge
99 Executable ``qemu-system-mipsel`` also covers simulation of 32-bit
100 nanoMIPS system in little endian mode:
104 Example of ``qemu-system-mipsel`` usage for nanoMIPS is shown below:
112 Start system emulation of Malta board with nanoMIPS I7200 CPU::
114 qemu-system-mipsel -cpu I7200 -kernel <kernel_image_file> \
|
| H A D | target-arm.rst | 7 ``qemu-system-aarch64`` executable to simulate a 64-bit Arm machine.
8 You can use either ``qemu-system-arm`` or ``qemu-system-aarch64``
10 work for ``qemu-system-arm`` will behave the same when used with
11 ``qemu-system-aarch64``.
16 are generally built into "system-on-chip" (SoC) designs created by
35 For QEMU's Arm system emulation, you must specify which board
40 operating system or firmware images intended to run on one machine
42 users who are used to the x86 world where every system looks like a
46 If you already have a system image or a kernel that works on hardware
52 boots on a system that QEMU does emulate.)
[all …]
|
| H A D | target-riscv.rst | 7 ``qemu-system-riscv64`` executable to simulate a 64-bit RISC-V machine,
8 ``qemu-system-riscv32`` executable to simulate a 32-bit RISC-V machine.
13 CPUs are generally built into "system-on-chip" (SoC) designs created by
25 For QEMU's RISC-V system emulation, you must specify which board
30 operating system or firmware images intended to run on one machine
32 users who are used to the x86 world where every system looks like a
36 If you already have a system image or a kernel that works on hardware
41 extract the file system and use that with a different kernel which
42 boots on a system that QEMU does emulate.)
58 ``qemu-system-riscv64 --machine help``, or
[all …]
|
| H A D | target-avr.rst | 6 Use the executable ``qemu-system-avr`` to emulate a AVR 8 bit based machine.
22 qemu-system-avr -machine mega2560 -bios demo.elf
26 qemu-system-avr -M mega2560 -bios demo.elf -nographic \
35 qemu-system-avr -machine mega2560 -bios demo.elf -s -S
48 qemu-system-avr -machine mega2560 -bios demo.elf -d in_asm
|
| H A D | target-rx.rst | 6 Use the executable ``qemu-system-rx`` to simulate RX target (GDB simulator).
19 Example of ``qemu-system-rx`` usage for RX is shown below:
25 qemu-system-rx -M gdbsim-r5f562n8 -bios <u-boot_image_file>
34 qemu-system-rx -M gdbsim-r5f562n8 \
|
| H A D | introduction.rst | 9 QEMU's system emulation provides a virtual model of a machine (CPU,
57 The flexible ``chardev`` system allows for handling IO from character
62 dynamically add and remove devices as well as introspect the system
72 system software images.
82 For a non-x86 system where we emulate a broad range of machine types,
85 the :ref:`system-targets-ref` section of the manual.
147 - How the system is displayed, how it is managed and controlled or
150 - How the system boots, via firmware or direct kernel boot.
160 $ qemu-system-aarch64 \
214 our system.
|
| H A D | target-openrisc.rst | 6 QEMU can emulate 32-bit OpenRISC CPUs using the ``qemu-system-or1k`` executable.
8 OpenRISC CPUs are generally built into "system-on-chip" (SoC) designs that run
20 For QEMU's OpenRISC system emulation, you must specify which board model you
32 If you already have a system image or a kernel that works on hardware and you
37 different kernel which boots on a system that QEMU does emulate.)
|
| /qemu/tests/multiboot/ |
| H A D | aout_kludge.out | 22 qemu-system-x86_64: invalid load_addr address
27 qemu-system-x86_64: invalid load_end_addr address
32 qemu-system-x86_64: invalid header_addr address
37 qemu-system-x86_64: invalid bss_end_addr address
42 qemu-system-x86_64: kernel does not fit in address space
|
| /qemu/target/loongarch/ |
| H A D | README | 14 …You can reference docs/system/loongarch/loongson3.rst to get the information about system emulatio…
33 3. Run LoongArch system basic command with loongarch-clfs-system.
37 …://github.com/loongson/build-tools/releases/download/2022.05.29/loongarch64-clfs-system-5.0.tar.bz2
39 tar -vxf loongarch64-clfs-system-5.0.tar.bz2 -C /opt/clfs
45 - Run LoongArch system basic command.
|
| /qemu/docs/devel/ |
| H A D | ci-definitions.rst.inc | 53 functionality and performance are achieved [4]_. Some or all system components
54 are integrated to create a complete system to be tested as a whole. System
56 transfer the right data at the right time across their interfaces. As system
58 to system testing [5]_. Note that, in some cases, system testing may require
62 On QEMU, system testing is represented by the 'check-avocado' target from
90 the unit, functional, system, and other tests.
94 1. System tests may depend on external software (operating system images,
97 the system being developed several times per day.
99 not be possible to run system tests in the developer’s private workspace.
100 There may be differences in hardware, operating system, or installed
[all …]
|
| H A D | s390-dasd-ipl.rst | 32 IPL2 is to find and load either the operating system or a small program that
34 the real operating system is loaded into memory and we are ready to hand
35 control over to the guest operating system. At this point the guest
36 operating system is entirely responsible for loading any more data it might
42 address points to the guest operating system code to execute at the end of
47 4. Start executing the guest operating system.
51 to start executing the operating system. This psw is loaded (via LPSW
52 instruction) causing control to be passed to the operating system code.
69 operating system from a DASD device:
134 system.
[all …]
|
| H A D | build-system.rst | 2 The QEMU build system architecture
6 QEMU build system. As with projects using GNU autotools, the QEMU build
7 system has two stages; first the developer runs the "configure" script
207 - System emulators - ``qemu-system-$ARCH``
278 The sourceset is only used for system emulators.
350 system/userspace emulation target
475 system.
478 Important files for the build system
511 file will influence the entire build system.
516 file will influence the entire build system.
[all …]
|
| /qemu/docs/system/devices/ |
| H A D | can.rst | 6 can be connected to host system CAN API (at this time only Linux
66 Example for qemu-system-x86_64::
76 Example for qemu-system-arm::
78 qemu-system-arm -cpu arm1176 -m 256 -M versatilepb \
88 The CAN interface of the host system has to be configured for proper
117 Linux system (SocketCAN used) and to both CTU CAN FD cores emulated
118 on the corresponding PCI card expects that host system CAN bus
121 qemu-system-x86_64 -enable-kvm -kernel /boot/vmlinuz-4.19.52+ \
131 Setup of CTU CAN FD controller in a guest Linux system::
160 in the guest system and next commands in the host system for basic CAN::
[all …]
|
| /qemu/docs/system/ppc/ |
| H A D | ppce500.rst | 31 the various devices in the system.
39 Both ``qemu-system-ppc`` and ``qemu-system-ppc64`` provide emulation for the
45 Additionally ``qemu-system-ppc64`` provides support for the following 64-bit
57 $ qemu-system-ppc64 -nographic -M ppce500 -cpu e6500
103 $ qemu-system-ppc64 -M ppce500 -cpu e5500 -smp 4 -m 2G \
117 $ qemu-system-ppc64 -M ppce500 -cpu e500mc -smp 4 -m 2G \
158 $ qemu-system-ppc64 -M ppce500 -smp 4 -m 2G \
170 Root file system on flash drive
179 $ qemu-system-ppc64 -M ppce500 -cpu e500mc -smp 4 -m 2G \
185 Alternatively, the root file system can also reside on an emulated SD card
[all …]
|
| /qemu/tests/tcg/i386/ |
| H A D | README | 10 The Linux system call modify_ldt() is used to create x86 selectors
13 The Linux system call vm86() is used to test vm86 emulation.
30 This program tests various Linux system calls. It is used to verify
31 that the system call parameters are correctly converted between target
|
| /qemu/docs/system/openrisc/ |
| H A D | or1k-sim.rst | 22 $ qemu-system-or1k -cpu or1220 -M or1k-sim -nographic \
31 drivers for the or1ksim machine. If you would like to run an SMP system
40 in the system.
43 system.
|
| /qemu/docs/system/riscv/ |
| H A D | virt.rst | 36 the various devices in the system. Guest software should discover the devices
67 $ qemu-system-riscv64 \
79 $ qemu-system-riscv64 \
137 $ qemu-system-riscv64 -M virt -smp 4 -m 2G \
156 Replace ``qemu-system-riscv64`` with ``qemu-system-riscv32`` in the command
176 $ qemu-system-riscv64 -M virt -smp 4 -m 2G \
194 $ qemu-system-riscv64 -M virt -smp 4 -m 2G \
200 riscv32_spl_defconfig builds, and replace ``qemu-system-riscv64`` with
201 ``qemu-system-riscv32`` in the command lines above to boot the 32-bit U-Boot.
219 $ qemu-system-riscv64 \
|
| /qemu/hw/timer/ |
| H A D | trace-events | 15 slavio_timer_mem_writel_mode_invalid(void) "not system timer"
81 sse_counter_control_read(uint64_t offset, uint64_t data, unsigned size) "SSE system counter control…
82 sse_counter_control_write(uint64_t offset, uint64_t data, unsigned size) "SSE system counter contro…
83 sse_counter_status_read(uint64_t offset, uint64_t data, unsigned size) "SSE system counter status f…
84 sse_counter_status_write(uint64_t offset, uint64_t data, unsigned size) "SSE system counter status …
85 sse_counter_reset(void) "SSE system counter: reset"
88 sse_timer_read(uint64_t offset, uint64_t data, unsigned size) "SSE system timer read: offset 0x%" P…
89 sse_timer_write(uint64_t offset, uint64_t data, unsigned size) "SSE system timer write: offset 0x%"…
90 sse_timer_reset(void) "SSE system timer: reset"
|
| /qemu/docs/tools/ |
| H A D | qemu-pr-helper.rst | 19 the operating system restricts sending these commands to unprivileged
28 started as a system service, and you should read the QEMU manual
64 is created in the system runtime state directory, for example
70 the system runtime state directory, for example
|
| /qemu/docs/system/s390x/ |
| H A D | pcidevices.rst | 15 qemu-system-s390x ... \
27 operating system.
32 qemu-system-s390x ... \
|
| /qemu/ |
| H A D | pythondeps.toml | 10 # - accepted: accepted versions when using a system package
12 # if a system package is not found; if not specified,
18 # presence of 'sphinx' in the system.
|
| /qemu/docs/specs/ |
| H A D | ppc-spapr-uv-hcalls.rst | 5 On PPC64 systems supporting Protected Execution Facility (PEF), system memory
33 wrapped/encrypted using the public key of a trusted system which has the private
34 key stored in the system's TPM. An Ultravisor will use this hcall to
35 unwrap/unseal the symmetric key using the system's TPM device or a TPM Resource
39 host system boot. All sensitive in and out values will be encrypted using the
|
| /qemu/docs/system/arm/ |
| H A D | orangepi.rst | 50 to qemu-system-arm.
62 This option can be used in case the target operating system driver uses a different
70 The above machine-specific options can be specified in qemu-system-arm
75 $ qemu-system-arm -M orangepi-pc -sd mycard.img \
111 $ qemu-system-arm -M orangepi-pc -nic user -nographic \
148 $ qemu-system-arm -M orangepi-pc -nic user -nographic \
169 $ qemu-system-arm -M orangepi-pc -nic user -nographic \
196 $ qemu-system-arm -M orangepi-pc -nic user -nographic \
211 The NetBSD operating system also includes support for Allwinner H3 based boards,
213 board and provides a fully working system with serial console, networking and storage.
[all …]
|