| /qemu/tests/qemu-iotests/ |
| H A D | 060.out | 9 Data may be corrupted, or further writes to the image may corrupt it.
11 …t: Preventing invalid write on metadata (overlaps with active L1 table); further corruption events…
37 Data may be corrupted, or further writes to the image may corrupt it.
39 …pt: Preventing invalid write on metadata (overlaps with refcount block); further corruption events…
70 Data may be corrupted, or further writes to the image may corrupt it.
75 … Preventing invalid write on metadata (overlaps with inactive L2 table); further corruption events…
110 …t: Preventing invalid write on metadata (overlaps with active L2 table); further corruption events…
121 …rupt: Preventing invalid write on metadata (overlaps with qcow2_header); further corruption events…
129 qcow2: Marking image as corrupt: L2 table offset 0x42a00 unaligned (L1 index: 0); further corruptio…
134 qcow2: Marking image as corrupt: L2 table offset 0x42a00 unaligned (L1 index: 0); further corruptio…
[all …]
|
| H A D | 039.out | 20 Data may be corrupted, or further writes to the image may corrupt it.
88 Data may be corrupted, or further writes to the image may corrupt it.
|
| H A D | 271.out | 458 …rrupt: Invalid cluster entry found (L2 offset: 0x40000, L2 index: 0x1); further corruption events…
473 …corrupt: Invalid cluster entry found (L2 offset: 0x40000, L2 index: 0); further corruption events…
480 …rrupt: Invalid cluster entry found (L2 offset: 0x40000, L2 index: 0x1); further corruption events…
503 …orrupt: Invalid cluster entry found (L2 offset: 0x40000, L2 index: 0x1); further corruption events…
518 … corrupt: Invalid cluster entry found (L2 offset: 0x40000, L2 index: 0); further corruption events…
525 …orrupt: Invalid cluster entry found (L2 offset: 0x40000, L2 index: 0x1); further corruption events…
556 Data may be corrupted, or further writes to the image may corrupt it.
557 …r allocation offset 0x50200 unaligned (L2 offset: 0x40000, L2 index: 0); further corruption events…
|
| H A D | 080.out | 80 Data may be corrupted, or further writes to the image may corrupt it.
103 Data may be corrupted, or further writes to the image may corrupt it.
|
| H A D | README | 15 additional options to test further image formats or I/O methods.
|
| H A D | 305.out | 14 qcow2: Marking image as corrupt: Refblock offset 0x20600 unaligned (reftable index: 0x1); further c…
|
| H A D | 138.out | 11 Data may be corrupted, or further writes to the image may corrupt it.
|
| H A D | 248 | 61 # drop other cached events, to not interfere with further wait for 'running'
|
| /qemu/tests/qtest/libqos/ |
| H A D | virtio-9p-client.h | 116 /* if requestOnly was set: request object for further processing */
138 /* if requestOnly was set: request object for further processing */
165 /* if requestOnly was set: request object for further processing */
191 /* if requestOnly was set: request object for further processing */
213 /* if requestOnly was set: request object for further processing */
243 /* if requestOnly was set: request object for further processing */
270 /* if requestOnly was set: request object for further processing */
296 /* if requestOnly was set: request object for further processing */
318 /* if requestOnly was set: request object for further processing */
351 /* if requestOnly was set: request object for further processing */
[all …]
|
| /qemu/docs/specs/ |
| H A D | vmcoreinfo.rst | 26 Only full write (of 16 bytes) are considered valid for further
29 A write of 0 in ``guest_format`` will disable further processing of
|
| /qemu/include/system/ |
| H A D | rtc.h | 36 * will be one hour further ahead than the current RTC time).
53 * a timestamp one hour further ahead than the current RTC time
|
| /qemu/docs/devel/ |
| H A D | conflict-resolution.rst | 13 after that fails to escalate further. This approach gives people more
36 seek further information, or will make a determination on next steps.
|
| /qemu/docs/system/devices/ |
| H A D | virtio-gpu.rst | 31 **Interfaces:** QEMU further categorizes virtio-gpu device variants based
38 user can further pick between MMIO or PCI. For MMIO, the user can suffix
|
| /qemu/docs/interop/ |
| H A D | live-block-operations.rst | 92 (c) the streamed file remains valid -- i.e. further
94 ``block-stream`` section further below for more
114 no more further overlays can be created based on
115 them. Refer the ``block-commit`` section further
147 ``node-name`` to each further disk image created (either via
322 and can now be (optionally) discarded, or retained to create further
395 ``BLOCK_JOB_COMPLETED`` event will be issued, and no further action is
403 The intermediate image [B] is invalid (as in: no more further
971 completed, and no further action is required.
|
| /qemu/rust/qemu-api/src/ |
| H A D | error.rs | 150 /// checked further at the Rust↔C boundary.
165 /// checked further at the Rust↔C boundary.
185 /// checked further at the Rust↔C boundary.
211 /// checked further at the Rust↔C boundary.
|
| /qemu/.gitlab/issue_templates/ |
| H A D | feature_request.md | 12 further by the community.
|
| /qemu/include/qemu/ |
| H A D | memfd.h | 13 #define F_SEAL_SEAL 0x0001 /* prevent further seals from being set */
|
| /qemu/migration/ |
| H A D | tls.h | 40 /* Whether the QIO channel requires further TLS handshake? */
|
| /qemu/linux-headers/asm-generic/ |
| H A D | hugetlb_encode.h | 6 * Without further specification, these system calls will use the
|
| /qemu/docs/devel/testing/ |
| H A D | ci-jobs.rst.inc | 13 For further information about how to set these variables, please refer to::
29 For further information about how to set these variables, please refer to::
|
| /qemu/include/net/ |
| H A D | filter.h | 25 * size: filter stolen this packet, we stop pass this packet further
|
| /qemu/tests/qemu-iotests/tests/ |
| H A D | copy-before-write | 166 Guest write succeed, but further snapshot-read fails, as snapshot is
179 Guest write fails, but snapshot-access continues working and further
|
| /qemu/hw/timer/ |
| H A D | xilinx_timer.c | 121 /* Further decoding to address a specific timers reg. */ in timer_read()
174 /* Further decoding to address a specific timers reg. */ in timer_write()
|
| /qemu/common-user/host/riscv/ |
| H A D | safe-syscall.inc.S | 24 * second one the system call number (as a 'long'), and all further
|
| /qemu/common-user/host/aarch64/ |
| H A D | safe-syscall.inc.S | 23 * second one the system call number (as a 'long'), and all further
|