Searched +full:crash +full:- +full:test +full:- +full:debian (Results 1 – 4 of 4) sorted by relevance
| /qemu/.gitlab-ci.d/ |
| H A D | buildtest.yml | 2 - 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 …]
|
| /qemu/docs/devel/testing/ |
| H A D | blkverify.rst | 5 ------------
7 This document describes how to use the ``blkverify`` protocol to test that a block
10 It is difficult to test and debug block drivers against real guests. Often
11 processes inside the guest will crash because corrupt sectors were read as part
20 ------------
22 The ``blkverify`` protocol has two child block devices, the "test" device and the
27 contents to the "test" image. The idea is that the "raw" device will handle
29 reference for comparison against the "test" device.
36 -------
40 $ ./qemu-io -c 'read -v 0 512' raw.img
[all …]
|
| /qemu/docs/system/ |
| H A D | qemu-block-drivers.rst.inc | 5 any of the tools (like ``qemu-img``). This includes the preferred formats
10 ``qemu-img create`` and ``qemu-img convert`` using the ``-o`` option.
13 .. program:: image-formats
20 space. Use ``qemu-img info`` to know the real size used by the
21 image or ``ls -ls`` on Unix/Linux.
34 .. program:: image-formats
51 zero clusters, which allow efficient copy-on-read for sparse images.
69 use to unlock the LUKS key slot is given by the ``encrypt.key-secret``
73 If this is set to ``aes``, the image is encrypted with 128-bit AES-CBC.
74 The encryption key is given by the ``encrypt.key-secret`` parameter.
[all …]
|
| /qemu/docs/about/ |
| H A D | deprecated.rst | 21 for pre-existing VM deployments. They should be scheduled for updating to a
23 should exclusively use a non-deprecated machine type, with use of the most
24 recent version highly recommended. Non-versioned machine types follow the
31 --------------------------------------
33 Short-form boolean options (since 6.0)
43 The replacement for the ``nodelay`` short-form boolean option is ``nodelay=on``
50 command-line less readable, especially when the argument itself consist of a
51 name and a value, e.g. ``-plugin plugin_name,arg="arg_name=arg_value"``.
52 Therefore, the usage of ``arg`` is redundant. Single-word arguments are treated
53 as short-form boolean values, and passed to plugins as ``arg_name=on``.
[all …]
|