Home
last modified time | relevance | path

Searched +full:kvm +full:- +full:build (Results 1 – 25 of 79) sorted by relevance

1234

/qemu/docs/about/
H A Dbuild-platforms.rst1 .. _Supported-build-platforms:
3 Supported build platforms
7 platforms. This appendix outlines which platforms are the major build
25 support for those backports, unless the feature is auto-detectable in a
32 You can find how to install build dependencies for different systems on the
33 :ref:`setup-build-env` page.
36 ----------------------------
40 .. list-table::
41 :header-rows: 1
43 * - CPU Architecture
[all …]
H A Dindex.rst1 ----------
3 ----------
11 hypervisor such as KVM, Xen or Hypervisor.Framework to allow the
19 utilities<Tools>`, such as the ``qemu-img`` disk image utility that
25 build-platforms
28 removed-features
/qemu/.gitlab-ci.d/
H A Dcrossbuild-template.yml3 stage: build
7 - ccache
12 - source scripts/ci/gitlab-ci-section
13 - section_start setup "Pre-script setup"
14 - JOBS=$(expr $(nproc) + 1)
15 - cat /packages.txt
16 - section_end setup
18 - export CCACHE_BASEDIR="$(pwd)"
19 - export CCACHE_DIR="$CCACHE_BASEDIR/ccache"
20 - export CCACHE_MAXSIZE="500M"
[all …]
H A Dbuildtest.yml2 - local: '/.gitlab-ci.d/buildtest-template.yml'
4 build-system-alpine:
6 - .native_build_job_template
7 - .native_build_artifact_template
9 - job: amd64-alpine-container
12 TARGETS: avr-softmmu loongarch64-softmmu mips64-softmmu mipsel-softmmu
13 MAKE_CHECK_ARGS: check-build
14 CONFIGURE_ARGS: --enable-docs --enable-trace-backends=log,simple,syslog
16 check-system-alpine:
19 - job: build-system-alpine
[all …]
H A Dcrossbuilds.yml2 - local: '/.gitlab-ci.d/crossbuild-template.yml'
4 cross-armhf-user:
7 job: armhf-debian-cross-container
9 IMAGE: debian-armhf-cross
11 cross-arm64-system:
14 job: arm64-debian-cross-container
16 IMAGE: debian-arm64-cross
18 cross-arm64-user:
21 job: arm64-debian-cross-container
23 IMAGE: debian-arm64-cross
[all …]
/qemu/target/s390x/kvm/
H A Dmeson.build4 'kvm.c',
5 'stsi-topology.c'
14 # - we build on s390x
15 # - we build the system emulation for s390x (qemu-system-s390x)
16 # - KVM is enabled
17 # - the linker supports --s390-pgste
18 if host_machine.cpu_family() == 's390x' and cc.has_link_argument('-Wl,--s390-pgste')
20 if_true: declare_dependency(link_args: ['-Wl,--s390-pgste']))
/qemu/
H A D.patchew.yml1 ---
91 {% elif test == "docker-mingw@fedora" or test == "docker-quick@centos8" or test == "asan" %}
94 This series failed the {{ test }} build test. Please find the testing commands and
104 This series failed build test on {{test}} host. Please find the details below.
115 ---
117 Please send your feedback to patchew-devel@redhat.com
126 time make docker-test-debug@fedora TARGET_LIST=x86_64-softmmu J=14 NETWORK=1
127 docker-quick@centos8:
133 time make docker-test-quick@centos8 SHOW_ENV=1 J=14 NETWORK=1
140 git rev-parse base > /dev/null || exit 0
[all …]
H A D.travis.yml5 - gcc
9 # - OS name (currently only linux)
10 # - OS distribution (e.g. "jammy" for Linux)
11 # - Names and values of visible environment variables set in .travis.yml or Settings panel
19 # $ travis encrypt -r "qemu/qemu" "irc.oftc.net#qemu"
23- secure: "F7GDRgjuOo5IUyRLqSkmDL7kvdU4UcH3Lm/W2db2JnDHTGCqgEdaYEYKciyCLZ57vOTsTsOgesN8iUT7hNHBd1K…
30 - SRC_DIR=".."
31 - BUILD_DIR="build"
32 - BASE_CONFIG="--disable-docs --disable-tools"
33 - TEST_BUILD_CMD=""
[all …]
H A Dmeson_options.txt1 # These options do not correspond to a --enable/--disable-* option
3 # scripts/meson-buildoptions.py's SKIP_OPTIONS constant too.
9 option('qemu_firmwarepath', type : 'array', value : ['share/qemu-firmware'],
12 description: 'use specified string as sub-version of the package')
25 …description: 'set block driver read-write whitelist (by default affects only QEMU, not tools like …
27 …description: 'set block driver read-only whitelist (by default affects only QEMU, not tools like q…
28 option('interp_prefix', type : 'string', value : '/usr/gnemul/qemu-%M',
33 description: 'fuzzing engine library for OSS-Fuzz')
40 # Everything else can be set via --enable/--disable-* option
42 # here make sure to run "make update-buildoptions".
[all …]
/qemu/docs/system/i386/
H A Dhyperv.rst1 Hyper-V Enlightenments
6 -----------
8 In some cases when implementing a hardware interface in software is slow, KVM
11 It may, however, be hard-to-impossible to add support for these interfaces to
14 KVM on x86 implements Hyper-V Enlightenments for Windows guests. These features
15 make Windows and Hyper-V guests think they're running on top of a Hyper-V
16 compatible hypervisor and use Hyper-V specific features.
20 -----
22 No Hyper-V enlightenments are enabled by default by either KVM or QEMU. In
25 .. parsed-literal::
[all …]
H A Damd-memory-encryption.rst6 SEV is an extension to the AMD-V architecture which supports running encrypted
7 virtual machines (VMs) under the control of KVM. Encrypted VMs have their pages
15 AMD secure processor (AMD-SP), which is present in AMD SOCs. Firmware running
16 inside the AMD-SP provides commands to support a common VM lifecycle. This
21 Secure Encrypted Virtualization - Encrypted State (SEV-ES) builds on the SEV
28 Launching (SEV and SEV-ES)
29 --------------------------
38 For a SEV-ES guest, the ``LAUNCH_UPDATE_VMSA`` command is also used to encrypt the
43 its public Diffie-Hellman key (PDH) and session parameters. These inputs
44 should be treated as a binary blob and must be passed as-is to the SEV firmware.
[all …]
/qemu/bsd-user/
H A Dmeson.build10 'bsd-mem.c',
11 'bsd-proc.c',
16 'plugin-api.c',
24 kvm = cc.find_library('kvm', required: true) build
25 bsd_user_ss.add(elf, procstat, kvm)
27 # Pull in the OS-specific build glue, if any
/qemu/docs/devel/
H A Dtracing.rst19 $ qemu --trace "memory_region_ops_*" ...
25 ``./configure --enable-trace-backends=BACKENDS`` was not explicitly specified.
27 Multiple patterns can be specified by repeating the ``--trace`` option::
29 $ qemu --trace "kvm_*" --trace "virtio_*" ...
32 file to avoid long command-line options::
36 $ qemu --trace events=/tmp/events ...
41 Sub-directory setup
42 -------------------
45 "trace-events" file. All directories which contain "trace-events" files must be
46 listed in the "trace_events_subdirs" variable in the top level meson.build
[all …]
H A Dcodebase.rst12 ----------
15 `MAINTAINERS <https://gitlab.com/qemu-project/qemu/-/blob/master/MAINTAINERS>`_
20 - `Accelerators<Accelerators>`
21 - Block devices and `disk images<disk images>` support
22 - `CI<ci>` and `Tests<testing>`
23 - `Devices<device-emulation>` & Board models
24 - `Documentation <documentation-root>`
25 - `GDB support<GDB usage>`
26 - :ref:`Migration<migration>`
27 - `Monitor<QEMU monitor>`
[all …]
H A Dkconfig.rst13 SCSI adapters. Arm, s390 and x86 boards can all present a virtio-blk
21 QEMU uses a simple domain-specific language to describe the dependencies
30 * users can easily build reduced versions of QEMU that support only a subset
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/``
48 --------------------
78 include it for clarity and future-proofing. After ``bool`` the following
136 ------------------------------------
179 a video card might specify ``select EDID`` if it needs to build EDID
[all …]
/qemu/docs/devel/testing/
H A Dmain.rst7 everything from unit testing and exercising specific sub-systems all
9 tests you can run ``make check-help`` from either the source or build
13 the meson build system so can be run directly from the build tree,
16 [./pyvenv/bin/]meson test --suite qemu:softfloat
38 -------------------------
49 Different sub-types of "make check" tests will be explained below.
51 Before running tests, it is best to build QEMU programs first. Some tests
55 .. _unit-tests:
68 In QEMU, unit tests can be invoked with ``make check-unit``. They are
76 1. Create a new source file. For example, ``tests/unit/foo-test.c``.
[all …]
/qemu/docs/system/riscv/
H A Dvirt.rst8 real-world hardware.
11 -----------------
17 * Platform-Level Interrupt Controller (PLIC)
22 * 8 virtio-mmio transport devices
31 ----------------------------------
34 which it passes to the guest, if there is no ``-dtb`` option. This provides
39 If users want to provide their own DTB, they can use the ``-dtb`` option.
42 * The number of subnodes of the /cpus node should match QEMU's ``-smp`` option
43 * The /memory reg size should match QEMU’s selected ram_size via ``-m``
48 ------------
[all …]
/qemu/qapi/
H A Dmisc-i386.json1 # -*- Mode: Python -*-
4 # SPDX-License-Identifier: GPL-2.0-or-later
7 # @rtc-reset-reinjection:
11 # for example QEMU guest agent's guest-set-time command.
19 # .. qmp-example::
21 # -> { "execute": "rtc-reset-reinjection" }
22 # <- { "return": {} }
24 { 'command': 'rtc-reset-reinjection' }
29 # An enumeration of SEV state information used during @query-sev.
33 # @launch-update: The guest is currently being launched; plaintext
[all …]
/qemu/tests/vm/
H A DMakefile.include3 # Hack to allow running in an unconfigured build tree
9 VM_VENV = check-venv
12 .PHONY: vm-build-all vm-clean-all
14 EFI_AARCH64 = $(wildcard $(BUILD_DIR)/pc-bios/edk2-aarch64-code.fd)
24 HOST_ARCH = $(shell uname -m)
31 IMAGES_DIR := $(HOME)/.cache/qemu-vm/images
37 HAVE_PYTHON_YAML = $(shell $(PYTHON) -c "import yaml" 2> /dev/null && echo yes)
40 # 'vm-help' target was historically named 'vm-test'
41 vm-help vm-test:
42 @echo "vm-help: Test QEMU in preconfigured virtual machines"
[all …]
H A Daarch64vm.py11 # the COPYING file in the top-level directory.
20 # This works for both kvm and tcg.
23 'machine' : "virt,gic-version=max",
32 DEFAULT_CONFIG = {'kvm' : {'cpu' : "host",
33 'machine' : "virt,gic-version=host"},
34 'tcg' : {'cpu' : "cortex-a57",
55 "To continue with the current build of QEMU, "\
63 config.update(DEFAULT_CONFIG['kvm'])
81 sys.stderr.write("*** please check --efi-aarch64 argument or "\
82 "install qemu-efi-aarch64 package\n")
[all …]
H A Dbasevm.py4 # Copyright 2017-2019 Red Hat Inc.
11 # the COPYING file in the top-level directory.
62 'block' : "-drive file={},if=none,id=drive0,cache=writeback "\
63 "-device virtio-blk,drive=drive0,bootindex=0",
64 'scsi' : "-device virtio-scsi-device,id=scsi "\
65 "-drive file={},format=raw,if=none,id=hd0 "\
66 "-device scsi-hd,drive=hd0,bootindex=0",
111 self._tmpdir = os.path.realpath(tempfile.mkdtemp(prefix="vm-test-",
133 os.path.join(os.path.expanduser("~/.cache/qemu-vm"),
141 netdev = "user,id=vnet,hostfwd=:127.0.0.1:{}-:22"
[all …]
/qemu/tests/functional/
H A Dtest_x86_64_kvm_xen.py3 # KVM Xen guest functional tests
12 # SPDX-License-Identifier: GPL-2.0-or-later
26 # Fetch assets from the kvm-xen-guest subdir of my shared test
28 # build instructions for how they where assembled.
31 'path=%2Fkvm-xen-guest&files=bzImage'),
36 'path=%2Fkvm-xen-guest&files=rootfs.ext4'),
41 self.require_accelerator("kvm")
46 self.vm.add_args("-accel", "kvm,xen-version=0x4000a,kernel-irqchip=split")
47 self.vm.add_args("-smp", "2")
53 self.vm.add_args('-kernel', self.kernel_path,
[all …]
/qemu/docs/devel/migration/
H A Dqpl-compression.rst4 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 Duadk-compression.rst4 UADK is a general-purpose user space accelerator framework that uses shared
8 UADK includes Unified/User-space-access-intended Accelerator Framework (UACCE),
24 different character devices with UACCE by using kernel-mode drivers of the
25 vendors. A user can access the hardware accelerators by performing user-mode
30 +----------------------------------+
32 +----+------------------------+----+
35 +-------+--------+ +-------+-------+
37 +-------+--------+ +-------+-------+
41 | +--------+------+
43 | +-+-------------+
[all …]
/qemu/docs/system/ppc/
H A Dpowernv.rst4 PowerNV (as Non-Virtualized) is the "bare metal" platform using the
6 be used as an hypervisor OS, running KVM guests, or simply as a host
16 -----------------
24 * Simple OCC is an on-chip micro-controller used for power management tasks.
30 ---------------
44 --------
49 GitHub <https://github.com/open-power>`_.
52 `OpenPOWER <https://github.com/open-power/op-build/releases/>`__ site.
58 ---------------------------
60 KVM acceleration in Linux Power hosts is provided by the kvm-hv and
[all …]

1234