* [Qemu-devel] Failing iotests in v2.3.0-rc2 / master
@ 2015-04-11 3:41 Andreas Färber
2015-04-11 14:33 ` Andreas Färber
` (2 more replies)
0 siblings, 3 replies; 12+ messages in thread
From: Andreas Färber @ 2015-04-11 3:41 UTC (permalink / raw)
To: qemu-devel; +Cc: Kevin Wolf, Peter Maydell, Jeff Cody, Stefan Hajnoczi
Hi,
001 seems to hang for -qcow (or is not reasonably "quick": >5 min).
033 is failing for -vhdx.
(Note that `make check-block` only tests -qcow2, so didn't uncover
either of them.)
Given a failing test, am I seeing correctly that there is no command
line option to skip this one failing test? -x seems to be for groups only.
Regards,
Andreas
$ ./check -v -T -qcow -g quick
[...]
001 6s ... [05:12:39]
$ ./check -v -T -vhdx -g quick
[...]
033 1s ... [04:06:09] [04:06:11] - output mismatch (see 033.out.bad)
--- /home/andreas/QEMU/qemu/tests/qemu-iotests/033.out 2015-04-08
20:19:11.947290578 +0200
+++ 033.out.bad 2015-04-11 04:06:11.939300375 +0200
@@ -2,52 +2,46 @@
Formatting 'TEST_DIR/t.IMGFMT', fmt=IMGFMT size=134217728
== preparing image ==
-wrote 1024/1024 bytes at offset 512
-1 KiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
-wrote 1536/1536 bytes at offset 131072
-1.500 KiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
-wrote 131072/131072 bytes at offset 1024
-128 KiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
+write failed: Operation not supported
+write failed: Operation not supported
+write failed: Operation not supported
== verifying patterns (1) ==
+Pattern verification failed at offset 512, 512 bytes
read 512/512 bytes at offset 512
512 bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
read 131072/131072 bytes at offset 1024
128 KiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
+Pattern verification failed at offset 132096, 512 bytes
read 512/512 bytes at offset 132096
512 bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
== rewriting zeroes ==
-wrote 65536/65536 bytes at offset 65536
-64 KiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
-wrote 65536/65536 bytes at offset 65536
-64 KiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
+write failed: Operation not supported
+write failed: Operation not supported
== verifying patterns (2) ==
read 131072/131072 bytes at offset 1024
128 KiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
== preparing image ==
-wrote 1024/1024 bytes at offset 512
-1 KiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
-wrote 1536/1536 bytes at offset 131072
-1.500 KiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
-wrote 131072/131072 bytes at offset 1024
-128 KiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
+write failed: Operation not supported
+write failed: Operation not supported
+write failed: Operation not supported
== verifying patterns (1) ==
+Pattern verification failed at offset 512, 512 bytes
read 512/512 bytes at offset 512
512 bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
read 131072/131072 bytes at offset 1024
128 KiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
+Pattern verification failed at offset 132096, 512 bytes
read 512/512 bytes at offset 132096
512 bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
== rewriting zeroes ==
-wrote 65536/65536 bytes at offset 65536
-64 KiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
-wrote 65536/65536 bytes at offset 65536
-64 KiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
+write failed: Operation not supported
+write failed: Operation not supported
== verifying patterns (2) ==
read 131072/131072 bytes at offset 1024
[...]
Not run: 017 018 019 020 024 025 027 028 029 031 034 035 036 037 038 039
042 045 046 047 048 050 053 054 058 059 060 062 063 065 066 067 068 069
071 073 074 075 077 078 081 082 084 086 087 088 089 090 092 094 095 098
101 102 103 107 108 110 111 113 114 116 123 128 130
Failures: 033
Failed 1 of 19 tests
--
SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Jennifer Guild, Dilip Upmanyu,
Graham Norton; HRB 21284 (AG Nürnberg)
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [Qemu-devel] Failing iotests in v2.3.0-rc2 / master
2015-04-11 3:41 [Qemu-devel] Failing iotests in v2.3.0-rc2 / master Andreas Färber
@ 2015-04-11 14:33 ` Andreas Färber
2015-04-13 16:42 ` Paolo Bonzini
2015-04-13 15:29 ` John Snow
2015-04-14 9:57 ` Kevin Wolf
2 siblings, 1 reply; 12+ messages in thread
From: Andreas Färber @ 2015-04-11 14:33 UTC (permalink / raw)
To: qemu-devel
Cc: Kevin Wolf, Peter Maydell, Jeff Cody, qemu-ppc, Stefan Hajnoczi
Am 11.04.2015 um 05:41 schrieb Andreas Färber:
> Hi,
>
> 001 seems to hang for -qcow (or is not reasonably "quick": >5 min).
>
> 033 is failing for -vhdx.
067 is failing for -qcow2 on ppc64 (no $QEMU_PROG => qemu-system-ppc64).
Seems to hang after the below output.
Andreas
$ tests/qemu-iotests-quick.sh
[...]
[ 477s] 067 [14:16:53] [14:16:54] - output mismatch (see
067.out.bad)
[ 477s] ---
/usr/src/packages/BUILD/qemu-2.3.0-rc2/tests/qemu-iotests/067.out
2015-04-02 22:10:37.000000000 +0000
[ 477s] +++ 067.out.bad 2015-04-11 14:16:54.200000003 +0000
[ 477s] @@ -60,7 +60,7 @@
[ 477s] },
[ 477s] {
[ 477s] "io-status": "ok",
[ 477s] - "device": "ide1-cd0",
[ 477s] + "device": "scsi0-cd2",
[ 477s] "locked": false,
[ 477s] "removable": true,
[ 477s] "tray_open": false,
[ 477s] @@ -83,7 +83,9 @@
[ 477s] ]
[ 477s] }
[ 477s] {
[ 477s] - "return": {
[ 477s] + "error": {
[ 477s] + "class": "GenericError",
[ 477s] + "desc": "Bus 'pci.0' does not support hotplugging"
[ 477s] }
[ 477s] }
[ 477s] {
[ 477s] @@ -95,34 +97,58 @@
[ 477s] "seconds": TIMESTAMP,
[ 477s] "microseconds": TIMESTAMP
[ 477s] },
[ 477s] - "event": "DEVICE_DELETED",
[ 477s] - "data": {
[ 477s] - "path": "/machine/peripheral/virtio0/virtio-backend"
[ 477s] - }
[ 477s] + "event": "RESET"
[ 477s] }
[ 477s] {
[ 477s] - "timestamp": {
[ 477s] - "seconds": TIMESTAMP,
[ 477s] - "microseconds": TIMESTAMP
[ 477s] - },
[ 477s] - "event": "DEVICE_DELETED",
[ 477s] + "return": [
[ 477s] + {
[ 477s] + "io-status": "ok",
[ 477s] + "device": "disk",
[ 477s] + "locked": false,
[ 477s] + "removable": false,
[ 477s] + "inserted": {
[ 477s] + "iops_rd": 0,
[ 477s] + "detect_zeroes": "off",
[ 477s] + "image": {
[ 477s] + "virtual-size": 134217728,
[ 477s] + "filename": "TEST_DIR/t.qcow2",
[ 477s] + "cluster-size": 65536,
[ 477s] + "format": "qcow2",
[ 477s] + "actual-size": SIZE,
[ 477s] + "format-specific": {
[ 477s] + "type": "qcow2",
[ 477s] "data": {
[ 477s] - "device": "virtio0",
[ 477s] - "path": "/machine/peripheral/virtio0"
[ 477s] - }
[ 477s] + "compat": "1.1",
[ 477s] + "lazy-refcounts": false,
[ 477s] + "refcount-bits": 16,
[ 477s] + "corrupt": false
[ 477s] }
[ 477s] -{
[ 477s] - "timestamp": {
[ 477s] - "seconds": TIMESTAMP,
[ 477s] - "microseconds": TIMESTAMP
[ 477s] },
[ 477s] - "event": "RESET"
[ 477s] -}
[ 477s] -{
[ 477s] - "return": [
[ 477s] + "dirty-flag": false
[ 477s] + },
[ 477s] + "iops_wr": 0,
[ 477s] + "ro": false,
[ 477s] + "backing_file_depth": 0,
[ 477s] + "drv": "qcow2",
[ 477s] + "iops": 0,
[ 477s] + "bps_wr": 0,
[ 477s] + "write_threshold": 0,
[ 477s] + "encrypted": false,
[ 477s] + "bps": 0,
[ 477s] + "bps_rd": 0,
[ 477s] + "cache": {
[ 477s] + "no-flush": false,
[ 477s] + "direct": false,
[ 477s] + "writeback": true
[ 477s] + },
[ 477s] + "file": "TEST_DIR/t.qcow2",
[ 477s] + "encryption_key_missing": false
[ 477s] + },
[ 477s] + "type": "unknown"
[ 477s] + },
[ 477s] {
[ 477s] "io-status": "ok",
[ 477s] - "device": "ide1-cd0",
[ 477s] + "device": "scsi0-cd2",
[ 477s] "locked": false,
[ 477s] "removable": true,
[ 477s] "tray_open": false,
[ 477s] @@ -162,18 +188,7 @@
[ 477s] },
[ 477s] "event": "DEVICE_TRAY_MOVED",
[ 477s] "data": {
[ 477s] - "device": "ide1-cd0",
[ 477s] - "tray-open": true
[ 477s] - }
[ 477s] -}
[ 477s] -{
[ 477s] - "timestamp": {
[ 477s] - "seconds": TIMESTAMP,
[ 477s] - "microseconds": TIMESTAMP
[ 477s] - },
[ 477s] - "event": "DEVICE_TRAY_MOVED",
[ 477s] - "data": {
[ 477s] - "device": "floppy0",
[ 477s] + "device": "scsi0-cd2",
[ 477s] "tray-open": true
[ 477s] }
[ 477s] }
[ 477s] @@ -238,7 +253,7 @@
[ 477s] },
[ 477s] {
[ 477s] "io-status": "ok",
[ 477s] - "device": "ide1-cd0",
[ 477s] + "device": "scsi0-cd2",
[ 477s] "locked": false,
[ 477s] "removable": true,
[ 477s] "tray_open": false,
[ 477s] @@ -261,11 +276,15 @@
[ 477s] ]
[ 477s] }
[ 477s] {
[ 477s] - "return": {
[ 477s] + "error": {
[ 477s] + "class": "GenericError",
[ 477s] + "desc": "Bus 'pci.0' does not support hotplugging"
[ 477s] }
[ 477s] }
[ 477s] {
[ 477s] - "return": {
[ 477s] + "error": {
[ 477s] + "class": "DeviceNotFound",
[ 477s] + "desc": "Device 'virtio0' not found"
[ 477s] }
[ 477s] }
[ 477s] {
[ 477s] @@ -277,34 +296,58 @@
[ 477s] "seconds": TIMESTAMP,
[ 477s] "microseconds": TIMESTAMP
[ 477s] },
[ 477s] - "event": "DEVICE_DELETED",
[ 477s] - "data": {
[ 477s] - "path": "/machine/peripheral/virtio0/virtio-backend"
[ 477s] - }
[ 477s] + "event": "RESET"
[ 477s] }
[ 477s] {
[ 477s] - "timestamp": {
[ 477s] - "seconds": TIMESTAMP,
[ 477s] - "microseconds": TIMESTAMP
[ 477s] - },
[ 477s] - "event": "DEVICE_DELETED",
[ 477s] + "return": [
[ 477s] + {
[ 477s] + "device": "disk",
[ 477s] + "locked": false,
[ 477s] + "removable": true,
[ 477s] + "inserted": {
[ 477s] + "iops_rd": 0,
[ 477s] + "detect_zeroes": "off",
[ 477s] + "image": {
[ 477s] + "virtual-size": 134217728,
[ 477s] + "filename": "TEST_DIR/t.qcow2",
[ 477s] + "cluster-size": 65536,
[ 477s] + "format": "qcow2",
[ 477s] + "actual-size": SIZE,
[ 477s] + "format-specific": {
[ 477s] + "type": "qcow2",
[ 477s] "data": {
[ 477s] - "device": "virtio0",
[ 477s] - "path": "/machine/peripheral/virtio0"
[ 477s] - }
[ 477s] + "compat": "1.1",
[ 477s] + "lazy-refcounts": false,
[ 477s] + "refcount-bits": 16,
[ 477s] + "corrupt": false
[ 477s] }
[ 477s] -{
[ 477s] - "timestamp": {
[ 477s] - "seconds": TIMESTAMP,
[ 477s] - "microseconds": TIMESTAMP
[ 477s] },
[ 477s] - "event": "RESET"
[ 477s] -}
[ 477s] -{
[ 477s] - "return": [
[ 477s] + "dirty-flag": false
[ 477s] + },
[ 477s] + "iops_wr": 0,
[ 477s] + "ro": false,
[ 477s] + "backing_file_depth": 0,
[ 477s] + "drv": "qcow2",
[ 477s] + "iops": 0,
[ 477s] + "bps_wr": 0,
[ 477s] + "write_threshold": 0,
[ 477s] + "encrypted": false,
[ 477s] + "bps": 0,
[ 477s] + "bps_rd": 0,
[ 477s] + "cache": {
[ 477s] + "no-flush": false,
[ 477s] + "direct": false,
[ 477s] + "writeback": true
[ 477s] + },
[ 477s] + "file": "TEST_DIR/t.qcow2",
[ 477s] + "encryption_key_missing": false
[ 477s] + },
[ 477s] + "tray_open": false,
[ 477s] + "type": "unknown"
[ 477s] + },
[ 477s] {
[ 477s] "io-status": "ok",
[ 477s] - "device": "ide1-cd0",
[ 477s] + "device": "scsi0-cd2",
[ 477s] "locked": false,
[ 477s] "removable": true,
[ 477s] "tray_open": false,
[ 477s] @@ -344,18 +387,7 @@
[ 477s] },
[ 477s] "event": "DEVICE_TRAY_MOVED",
[ 477s] "data": {
[ 477s] - "device": "ide1-cd0",
[ 477s] - "tray-open": true
[ 477s] - }
[ 477s] -}
[ 477s] -{
[ 477s] - "timestamp": {
[ 477s] - "seconds": TIMESTAMP,
[ 477s] - "microseconds": TIMESTAMP
[ 477s] - },
[ 477s] - "event": "DEVICE_TRAY_MOVED",
[ 477s] - "data": {
[ 477s] - "device": "floppy0",
[ 477s] + "device": "scsi0-cd2",
[ 477s] "tray-open": true
[ 477s] }
[ 477s] }
[ 477s] @@ -378,7 +410,7 @@
[ 477s] "return": [
[ 477s] {
[ 477s] "io-status": "ok",
[ 477s] - "device": "ide1-cd0",
[ 477s] + "device": "scsi0-cd2",
[ 477s] "locked": false,
[ 477s] "removable": true,
[ 477s] "tray_open": false,
[ 477s] @@ -446,11 +478,15 @@
[ 477s] ]
[ 477s] }
[ 477s] {
[ 477s] - "return": {
[ 477s] + "error": {
[ 477s] + "class": "GenericError",
[ 477s] + "desc": "Bus 'pci.0' does not support hotplugging"
[ 477s] }
[ 477s] }
[ 477s] {
[ 477s] - "return": {
[ 477s] + "error": {
[ 477s] + "class": "DeviceNotFound",
[ 477s] + "desc": "Device 'virtio0' not found"
[ 477s] }
[ 477s] }
[ 477s] {
[ 477s] @@ -462,34 +498,13 @@
[ 477s] "seconds": TIMESTAMP,
[ 477s] "microseconds": TIMESTAMP
[ 477s] },
[ 477s] - "event": "DEVICE_DELETED",
[ 477s] - "data": {
[ 477s] - "path": "/machine/peripheral/virtio0/virtio-backend"
[ 477s] - }
[ 477s] -}
[ 477s] -{
[ 477s] - "timestamp": {
[ 477s] - "seconds": TIMESTAMP,
[ 477s] - "microseconds": TIMESTAMP
[ 477s] - },
[ 477s] - "event": "DEVICE_DELETED",
[ 477s] - "data": {
[ 477s] - "device": "virtio0",
[ 477s] - "path": "/machine/peripheral/virtio0"
[ 477s] - }
[ 477s] -}
[ 477s] -{
[ 477s] - "timestamp": {
[ 477s] - "seconds": TIMESTAMP,
[ 477s] - "microseconds": TIMESTAMP
[ 477s] - },
[ 477s] "event": "RESET"
[ 477s] }
[ 477s] {
[ 477s] "return": [
[ 477s] {
[ 477s] "io-status": "ok",
[ 477s] - "device": "ide1-cd0",
[ 477s] + "device": "scsi0-cd2",
[ 477s] "locked": false,
[ 477s] "removable": true,
[ 477s] "tray_open": false,
[ 477s] @@ -508,6 +523,51 @@
[ 477s] "removable": true,
[ 477s] "tray_open": false,
[ 477s] "type": "unknown"
[ 477s] + },
[ 477s] + {
[ 477s] + "device": "disk",
[ 477s] + "locked": false,
[ 477s] + "removable": true,
[ 477s] + "inserted": {
[ 477s] + "iops_rd": 0,
[ 477s] + "detect_zeroes": "off",
[ 477s] + "image": {
[ 477s] + "virtual-size": 134217728,
[ 477s] + "filename": "TEST_DIR/t.qcow2",
[ 477s] + "cluster-size": 65536,
[ 477s] + "format": "qcow2",
[ 477s] + "actual-size": SIZE,
[ 477s] + "format-specific": {
[ 477s] + "type": "qcow2",
[ 477s] + "data": {
[ 477s] + "compat": "1.1",
[ 477s] + "lazy-refcounts": false,
[ 477s] + "refcount-bits": 16,
[ 477s] + "corrupt": false
[ 477s] + }
[ 477s] + },
[ 477s] + "dirty-flag": false
[ 477s] + },
[ 477s] + "iops_wr": 0,
[ 477s] + "ro": false,
[ 477s] + "backing_file_depth": 0,
[ 477s] + "drv": "qcow2",
[ 477s] + "iops": 0,
[ 477s] + "bps_wr": 0,
[ 477s] + "write_threshold": 0,
[ 477s] + "encrypted": false,
[ 477s] + "bps": 0,
[ 477s] + "bps_rd": 0,
[ 477s] + "cache": {
[ 477s] + "no-flush": false,
[ 477s] + "direct": false,
[ 477s] + "writeback": true
[ 477s] + },
[ 477s] + "file": "TEST_DIR/t.qcow2",
[ 477s] + "encryption_key_missing": false
[ 477s] + },
[ 477s] + "tray_open": false,
[ 477s] + "type": "unknown"
[ 477s] }
[ 477s] ]
[ 477s] }
[ 477s] @@ -529,18 +589,7 @@
[ 477s] },
[ 477s] "event": "DEVICE_TRAY_MOVED",
[ 477s] "data": {
[ 477s] - "device": "ide1-cd0",
[ 477s] - "tray-open": true
[ 477s] - }
[ 477s] -}
[ 477s] -{
[ 477s] - "timestamp": {
[ 477s] - "seconds": TIMESTAMP,
[ 477s] - "microseconds": TIMESTAMP
[ 477s] - },
[ 477s] - "event": "DEVICE_TRAY_MOVED",
[ 477s] - "data": {
[ 477s] - "device": "floppy0",
[ 477s] + "device": "scsi0-cd2",
[ 477s] "tray-open": true
[ 477s] }
[ 477s] }
[ 477s] @@ -564,7 +613,7 @@
[ 477s] "return": [
[ 477s] {
[ 477s] "io-status": "ok",
[ 477s] - "device": "ide1-cd0",
[ 477s] + "device": "scsi0-cd2",
[ 477s] "locked": false,
[ 477s] "removable": true,
[ 477s] "tray_open": false,
[ 477s] @@ -632,11 +681,15 @@
[ 477s] ]
[ 477s] }
[ 477s] {
[ 477s] - "return": {
[ 477s] + "error": {
[ 477s] + "class": "GenericError",
[ 477s] + "desc": "Bus 'pci.0' does not support hotplugging"
[ 477s] }
[ 477s] }
[ 477s] {
[ 477s] - "return": {
[ 477s] + "error": {
[ 477s] + "class": "DeviceNotFound",
[ 477s] + "desc": "Device 'virtio0' not found"
[ 477s] }
[ 477s] }
[ 477s] {
[ 477s] @@ -648,34 +701,13 @@
[ 477s] "seconds": TIMESTAMP,
[ 477s] "microseconds": TIMESTAMP
[ 477s] },
[ 477s] - "event": "DEVICE_DELETED",
[ 477s] - "data": {
[ 477s] - "path": "/machine/peripheral/virtio0/virtio-backend"
[ 477s] - }
[ 477s] -}
[ 477s] -{
[ 477s] - "timestamp": {
[ 477s] - "seconds": TIMESTAMP,
[ 477s] - "microseconds": TIMESTAMP
[ 477s] - },
[ 477s] - "event": "DEVICE_DELETED",
[ 477s] - "data": {
[ 477s] - "device": "virtio0",
[ 477s] - "path": "/machine/peripheral/virtio0"
[ 477s] - }
[ 477s] -}
[ 477s] -{
[ 477s] - "timestamp": {
[ 477s] - "seconds": TIMESTAMP,
[ 477s] - "microseconds": TIMESTAMP
[ 477s] - },
[ 477s] "event": "RESET"
[ 477s] }
[ 477s] {
[ 477s] "return": [
[ 477s] {
[ 477s] "io-status": "ok",
[ 477s] - "device": "ide1-cd0",
[ 477s] + "device": "scsi0-cd2",
[ 477s] "locked": false,
[ 477s] "removable": true,
[ 477s] "tray_open": false,
[ 477s] @@ -696,7 +728,6 @@
[ 477s] "type": "unknown"
[ 477s] },
[ 477s] {
[ 477s] - "io-status": "ok",
[ 477s] "device": "disk",
[ 477s] "locked": false,
[ 477s] "removable": true,
[ 477s] @@ -761,18 +792,7 @@
[ 477s] },
[ 477s] "event": "DEVICE_TRAY_MOVED",
[ 477s] "data": {
[ 477s] - "device": "ide1-cd0",
[ 477s] - "tray-open": true
[ 477s] - }
[ 477s] -}
[ 477s] -{
[ 477s] - "timestamp": {
[ 477s] - "seconds": TIMESTAMP,
[ 477s] - "microseconds": TIMESTAMP
[ 477s] - },
[ 477s] - "event": "DEVICE_TRAY_MOVED",
[ 477s] - "data": {
[ 477s] - "device": "floppy0",
[ 477s] + "device": "scsi0-cd2",
[ 477s] "tray-open": true
[ 477s] }
[ 477s] }
--
SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Jennifer Guild, Dilip Upmanyu,
Graham Norton; HRB 21284 (AG Nürnberg)
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [Qemu-devel] Failing iotests in v2.3.0-rc2 / master
2015-04-11 3:41 [Qemu-devel] Failing iotests in v2.3.0-rc2 / master Andreas Färber
2015-04-11 14:33 ` Andreas Färber
@ 2015-04-13 15:29 ` John Snow
2015-04-13 17:03 ` Andreas Färber
2015-04-14 9:57 ` Kevin Wolf
2 siblings, 1 reply; 12+ messages in thread
From: John Snow @ 2015-04-13 15:29 UTC (permalink / raw)
To: Andreas Färber, qemu-devel
Cc: Kevin Wolf, Peter Maydell, Jeff Cody, Stefan Hajnoczi
On 04/10/2015 11:41 PM, Andreas Färber wrote:
> Hi,
>
> 001 seems to hang for -qcow (or is not reasonably "quick": >5 min).
>
I assume this was a one-off and you cannot reproduce it reliably.
Do you have any data on what call it might have hung on?
> 033 is failing for -vhdx.
>
> (Note that `make check-block` only tests -qcow2, so didn't uncover
> either of them.)
>
> Given a failing test, am I seeing correctly that there is no command
> line option to skip this one failing test? -x seems to be for groups only.
>
> Regards,
> Andreas
>
> $ ./check -v -T -qcow -g quick
> [...]
> 001 6s ... [05:12:39]
>
> $ ./check -v -T -vhdx -g quick
> [...]
> 033 1s ... [04:06:09] [04:06:11] - output mismatch (see 033.out.bad)
> --- /home/andreas/QEMU/qemu/tests/qemu-iotests/033.out 2015-04-08
> 20:19:11.947290578 +0200
> +++ 033.out.bad 2015-04-11 04:06:11.939300375 +0200
> @@ -2,52 +2,46 @@
> Formatting 'TEST_DIR/t.IMGFMT', fmt=IMGFMT size=134217728
>
> == preparing image ==
> -wrote 1024/1024 bytes at offset 512
> -1 KiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
> -wrote 1536/1536 bytes at offset 131072
> -1.500 KiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
> -wrote 131072/131072 bytes at offset 1024
> -128 KiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
> +write failed: Operation not supported
> +write failed: Operation not supported
> +write failed: Operation not supported
>
> == verifying patterns (1) ==
> +Pattern verification failed at offset 512, 512 bytes
> read 512/512 bytes at offset 512
> 512 bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
> read 131072/131072 bytes at offset 1024
> 128 KiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
> +Pattern verification failed at offset 132096, 512 bytes
> read 512/512 bytes at offset 132096
> 512 bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
>
> == rewriting zeroes ==
> -wrote 65536/65536 bytes at offset 65536
> -64 KiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
> -wrote 65536/65536 bytes at offset 65536
> -64 KiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
> +write failed: Operation not supported
> +write failed: Operation not supported
>
> == verifying patterns (2) ==
> read 131072/131072 bytes at offset 1024
> 128 KiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
>
> == preparing image ==
> -wrote 1024/1024 bytes at offset 512
> -1 KiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
> -wrote 1536/1536 bytes at offset 131072
> -1.500 KiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
> -wrote 131072/131072 bytes at offset 1024
> -128 KiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
> +write failed: Operation not supported
> +write failed: Operation not supported
> +write failed: Operation not supported
>
> == verifying patterns (1) ==
> +Pattern verification failed at offset 512, 512 bytes
> read 512/512 bytes at offset 512
> 512 bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
> read 131072/131072 bytes at offset 1024
> 128 KiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
> +Pattern verification failed at offset 132096, 512 bytes
> read 512/512 bytes at offset 132096
> 512 bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
>
> == rewriting zeroes ==
> -wrote 65536/65536 bytes at offset 65536
> -64 KiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
> -wrote 65536/65536 bytes at offset 65536
> -64 KiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
> +write failed: Operation not supported
> +write failed: Operation not supported
>
> == verifying patterns (2) ==
> read 131072/131072 bytes at offset 1024
> [...]
> Not run: 017 018 019 020 024 025 027 028 029 031 034 035 036 037 038 039
> 042 045 046 047 048 050 053 054 058 059 060 062 063 065 066 067 068 069
> 071 073 074 075 077 078 081 082 084 086 087 088 089 090 092 094 095 098
> 101 102 103 107 108 110 111 113 114 116 123 128 130
> Failures: 033
> Failed 1 of 19 tests
>
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [Qemu-devel] Failing iotests in v2.3.0-rc2 / master
2015-04-11 14:33 ` Andreas Färber
@ 2015-04-13 16:42 ` Paolo Bonzini
0 siblings, 0 replies; 12+ messages in thread
From: Paolo Bonzini @ 2015-04-13 16:42 UTC (permalink / raw)
To: Andreas Färber, qemu-devel
Cc: Kevin Wolf, Peter Maydell, Jeff Cody, qemu-ppc, Stefan Hajnoczi
On 11/04/2015 16:33, Andreas Färber wrote:
> 067 is failing for -qcow2 on ppc64 (no $QEMU_PROG => qemu-system-ppc64).
> Seems to hang after the below output.
It really needs a PC machine, it seems.
Paolo
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [Qemu-devel] Failing iotests in v2.3.0-rc2 / master
2015-04-13 15:29 ` John Snow
@ 2015-04-13 17:03 ` Andreas Färber
0 siblings, 0 replies; 12+ messages in thread
From: Andreas Färber @ 2015-04-13 17:03 UTC (permalink / raw)
To: John Snow, qemu-devel
Cc: Kevin Wolf, Peter Maydell, Jeff Cody, Stefan Hajnoczi
Am 13.04.2015 um 17:29 schrieb John Snow:
> On 04/10/2015 11:41 PM, Andreas Färber wrote:
>> Hi,
>>
>> 001 seems to hang for -qcow (or is not reasonably "quick": >5 min).
>>
>
> I assume this was a one-off and you cannot reproduce it reliably.
No, I could reproduce it both locally and in our build service.
Note that this is about -qcow, not -qcow2.
Andreas
--
SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Jennifer Guild, Dilip Upmanyu,
Graham Norton; HRB 21284 (AG Nürnberg)
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [Qemu-devel] Failing iotests in v2.3.0-rc2 / master
2015-04-11 3:41 [Qemu-devel] Failing iotests in v2.3.0-rc2 / master Andreas Färber
2015-04-11 14:33 ` Andreas Färber
2015-04-13 15:29 ` John Snow
@ 2015-04-14 9:57 ` Kevin Wolf
2015-04-15 4:53 ` Jeff Cody
2015-04-15 11:27 ` Jeff Cody
2 siblings, 2 replies; 12+ messages in thread
From: Kevin Wolf @ 2015-04-14 9:57 UTC (permalink / raw)
To: Andreas Färber; +Cc: Peter Maydell, Jeff Cody, qemu-devel, Stefan Hajnoczi
Am 11.04.2015 um 05:41 hat Andreas Färber geschrieben:
> Hi,
>
> 001 seems to hang for -qcow (or is not reasonably "quick": >5 min).
>
> 033 is failing for -vhdx.
>
> (Note that `make check-block` only tests -qcow2, so didn't uncover
> either of them.)
>
> Given a failing test, am I seeing correctly that there is no command
> line option to skip this one failing test? -x seems to be for groups only.
>
> Regards,
> Andreas
>
> $ ./check -v -T -qcow -g quick
> [...]
> 001 6s ... [05:12:39]
qcow1 is just really slow. 001 passes for me, after 202 seconds (that's
on my SSD, YMMV).
> $ ./check -v -T -vhdx -g quick
> [...]
> 033 1s ... [04:06:09] [04:06:11] - output mismatch (see 033.out.bad)
This seems to be because blkdebug doesn't implement .bdrv_truncate.
Currently the test case isn't suitable for VHDX, which uses explicit
bdrv_truncate() calls to grow the image file. I'll send a patch for
blkdebug to allow this.
However, it seems that there is another problem which causes assertion
failures when using VHDX over blkdebug. Jeff, does the following fix
make sense to you? (I think it does, but I don't understand yet why the
assertion failure is only triggered with blkdebug - or in other words:
"how could this ever work?")
Kevin
--- a/block/vhdx.c
+++ b/block/vhdx.c
@@ -1285,7 +1285,7 @@ static coroutine_fn int vhdx_co_writev(BlockDriverState *bs, int64_t sector_num,
iov2.iov_base = qemu_blockalign(bs, iov2.iov_len);
memset(iov2.iov_base, 0, iov2.iov_len);
qemu_iovec_concat_iov(&hd_qiov, &iov2, 1, 0,
- sinfo.block_offset);
+ iov2.iov_len);
sectors_to_write += iov2.iov_len >> BDRV_SECTOR_BITS;
}
}
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [Qemu-devel] Failing iotests in v2.3.0-rc2 / master
2015-04-14 9:57 ` Kevin Wolf
@ 2015-04-15 4:53 ` Jeff Cody
2015-04-15 9:26 ` Kevin Wolf
2015-04-15 11:27 ` Jeff Cody
1 sibling, 1 reply; 12+ messages in thread
From: Jeff Cody @ 2015-04-15 4:53 UTC (permalink / raw)
To: Kevin Wolf
Cc: Peter Maydell, Andreas Färber, Stefan Hajnoczi, qemu-devel
On Tue, Apr 14, 2015 at 11:57:35AM +0200, Kevin Wolf wrote:
> Am 11.04.2015 um 05:41 hat Andreas Färber geschrieben:
> > Hi,
> >
> > 001 seems to hang for -qcow (or is not reasonably "quick": >5 min).
> >
> > 033 is failing for -vhdx.
> >
> > (Note that `make check-block` only tests -qcow2, so didn't uncover
> > either of them.)
> >
> > Given a failing test, am I seeing correctly that there is no command
> > line option to skip this one failing test? -x seems to be for groups only.
> >
> > Regards,
> > Andreas
> >
> > $ ./check -v -T -qcow -g quick
> > [...]
> > 001 6s ... [05:12:39]
>
> qcow1 is just really slow. 001 passes for me, after 202 seconds (that's
> on my SSD, YMMV).
>
> > $ ./check -v -T -vhdx -g quick
> > [...]
> > 033 1s ... [04:06:09] [04:06:11] - output mismatch (see 033.out.bad)
>
> This seems to be because blkdebug doesn't implement .bdrv_truncate.
> Currently the test case isn't suitable for VHDX, which uses explicit
> bdrv_truncate() calls to grow the image file. I'll send a patch for
> blkdebug to allow this.
>
> However, it seems that there is another problem which causes assertion
> failures when using VHDX over blkdebug. Jeff, does the following fix
> make sense to you? (I think it does, but I don't understand yet why the
> assertion failure is only triggered with blkdebug - or in other words:
> "how could this ever work?")
>
> Kevin
Kevin,
Yes, looking at that fix it makes sense - we are wanting to pad the
back part of the block after the actual data with zeros. That back
length should be (block size - (bytes avail + block offset)), which is
iov2.iov_len.
There are two reasons I think we haven't seen this issue (it has been
hidden):
1.) If bs->file supports zero init, we don't do any of this
2.) This is done for the case when the existing BAT state is
PAYLOAD_BLOCK_ZERO. Until recently (commit 30af51c), we didn't
create VHDX files with blocks in the PAYLOAD_BLOCK_ZERO state.
So it has been a latent bug in a hitherto rarely (if ever) exercised
path.
Jeff
>
> --- a/block/vhdx.c
> +++ b/block/vhdx.c
> @@ -1285,7 +1285,7 @@ static coroutine_fn int vhdx_co_writev(BlockDriverState *bs, int64_t sector_num,
> iov2.iov_base = qemu_blockalign(bs, iov2.iov_len);
> memset(iov2.iov_base, 0, iov2.iov_len);
> qemu_iovec_concat_iov(&hd_qiov, &iov2, 1, 0,
> - sinfo.block_offset);
> + iov2.iov_len);
> sectors_to_write += iov2.iov_len >> BDRV_SECTOR_BITS;
> }
> }
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [Qemu-devel] Failing iotests in v2.3.0-rc2 / master
2015-04-15 4:53 ` Jeff Cody
@ 2015-04-15 9:26 ` Kevin Wolf
2015-04-15 9:34 ` Andreas Färber
0 siblings, 1 reply; 12+ messages in thread
From: Kevin Wolf @ 2015-04-15 9:26 UTC (permalink / raw)
To: Jeff Cody; +Cc: Peter Maydell, Andreas Färber, Stefan Hajnoczi, qemu-devel
Am 15.04.2015 um 06:53 hat Jeff Cody geschrieben:
> On Tue, Apr 14, 2015 at 11:57:35AM +0200, Kevin Wolf wrote:
> > Am 11.04.2015 um 05:41 hat Andreas Färber geschrieben:
> > > Hi,
> > >
> > > 001 seems to hang for -qcow (or is not reasonably "quick": >5 min).
> > >
> > > 033 is failing for -vhdx.
> > >
> > > (Note that `make check-block` only tests -qcow2, so didn't uncover
> > > either of them.)
> > >
> > > Given a failing test, am I seeing correctly that there is no command
> > > line option to skip this one failing test? -x seems to be for groups only.
> > >
> > > Regards,
> > > Andreas
> > >
> > > $ ./check -v -T -qcow -g quick
> > > [...]
> > > 001 6s ... [05:12:39]
> >
> > qcow1 is just really slow. 001 passes for me, after 202 seconds (that's
> > on my SSD, YMMV).
> >
> > > $ ./check -v -T -vhdx -g quick
> > > [...]
> > > 033 1s ... [04:06:09] [04:06:11] - output mismatch (see 033.out.bad)
> >
> > This seems to be because blkdebug doesn't implement .bdrv_truncate.
> > Currently the test case isn't suitable for VHDX, which uses explicit
> > bdrv_truncate() calls to grow the image file. I'll send a patch for
> > blkdebug to allow this.
> >
> > However, it seems that there is another problem which causes assertion
> > failures when using VHDX over blkdebug. Jeff, does the following fix
> > make sense to you? (I think it does, but I don't understand yet why the
> > assertion failure is only triggered with blkdebug - or in other words:
> > "how could this ever work?")
> >
> > Kevin
>
> Kevin,
>
> Yes, looking at that fix it makes sense - we are wanting to pad the
> back part of the block after the actual data with zeros. That back
> length should be (block size - (bytes avail + block offset)), which is
> iov2.iov_len.
>
> There are two reasons I think we haven't seen this issue (it has been
> hidden):
>
> 1.) If bs->file supports zero init, we don't do any of this
I see. file does and blkdebug doesn't, so that's the crucial difference.
> 2.) This is done for the case when the existing BAT state is
> PAYLOAD_BLOCK_ZERO. Until recently (commit 30af51c), we didn't
> create VHDX files with blocks in the PAYLOAD_BLOCK_ZERO state.
Right, I wasn't aware of this either any more.
> So it has been a latent bug in a hitherto rarely (if ever) exercised
> path.
Thanks for your explanation, it's clear to me now what's going on. I'll
send out the patches (for both blkdebug and vhdx) right away. You can
either pick up the vhdx one, or just give your Acked-by and then I'll
merge it through my block tree.
Kevin
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [Qemu-devel] Failing iotests in v2.3.0-rc2 / master
2015-04-15 9:26 ` Kevin Wolf
@ 2015-04-15 9:34 ` Andreas Färber
2015-04-15 9:47 ` Kevin Wolf
0 siblings, 1 reply; 12+ messages in thread
From: Andreas Färber @ 2015-04-15 9:34 UTC (permalink / raw)
To: Kevin Wolf, Jeff Cody; +Cc: Peter Maydell, qemu-devel, Stefan Hajnoczi
Am 15.04.2015 um 11:26 schrieb Kevin Wolf:
> Am 15.04.2015 um 06:53 hat Jeff Cody geschrieben:
>> On Tue, Apr 14, 2015 at 11:57:35AM +0200, Kevin Wolf wrote:
>>> Am 11.04.2015 um 05:41 hat Andreas Färber geschrieben:
>>>> Hi,
>>>>
>>>> 001 seems to hang for -qcow (or is not reasonably "quick": >5 min).
>>>>
>>>> 033 is failing for -vhdx.
>>>>
>>>> (Note that `make check-block` only tests -qcow2, so didn't uncover
>>>> either of them.)
>>>>
>>>> Given a failing test, am I seeing correctly that there is no command
>>>> line option to skip this one failing test? -x seems to be for groups only.
>>>>
>>>> Regards,
>>>> Andreas
>>>>
>>>> $ ./check -v -T -qcow -g quick
>>>> [...]
>>>> 001 6s ... [05:12:39]
>>>
>>> qcow1 is just really slow. 001 passes for me, after 202 seconds (that's
>>> on my SSD, YMMV).
>>>
>>>> $ ./check -v -T -vhdx -g quick
>>>> [...]
>>>> 033 1s ... [04:06:09] [04:06:11] - output mismatch (see 033.out.bad)
>>>
>>> This seems to be because blkdebug doesn't implement .bdrv_truncate.
>>> Currently the test case isn't suitable for VHDX, which uses explicit
>>> bdrv_truncate() calls to grow the image file. I'll send a patch for
>>> blkdebug to allow this.
>>>
>>> However, it seems that there is another problem which causes assertion
>>> failures when using VHDX over blkdebug. Jeff, does the following fix
>>> make sense to you? (I think it does, but I don't understand yet why the
>>> assertion failure is only triggered with blkdebug - or in other words:
>>> "how could this ever work?")
>>>
>>> Kevin
>>
>> Kevin,
>>
>> Yes, looking at that fix it makes sense - we are wanting to pad the
>> back part of the block after the actual data with zeros. That back
>> length should be (block size - (bytes avail + block offset)), which is
>> iov2.iov_len.
>>
>> There are two reasons I think we haven't seen this issue (it has been
>> hidden):
>>
>> 1.) If bs->file supports zero init, we don't do any of this
>
> I see. file does and blkdebug doesn't, so that's the crucial difference.
>
>> 2.) This is done for the case when the existing BAT state is
>> PAYLOAD_BLOCK_ZERO. Until recently (commit 30af51c), we didn't
>> create VHDX files with blocks in the PAYLOAD_BLOCK_ZERO state.
>
> Right, I wasn't aware of this either any more.
>
>> So it has been a latent bug in a hitherto rarely (if ever) exercised
>> path.
>
> Thanks for your explanation, it's clear to me now what's going on. I'll
> send out the patches (for both blkdebug and vhdx) right away. You can
> either pick up the vhdx one, or just give your Acked-by and then I'll
> merge it through my block tree.
Might 059 (?) failure for -vmdk be another symptom of the same issue?
Thanks,
Andreas
--
SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Jennifer Guild, Dilip Upmanyu,
Graham Norton; HRB 21284 (AG Nürnberg)
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [Qemu-devel] Failing iotests in v2.3.0-rc2 / master
2015-04-15 9:34 ` Andreas Färber
@ 2015-04-15 9:47 ` Kevin Wolf
2015-04-15 9:54 ` Andreas Färber
0 siblings, 1 reply; 12+ messages in thread
From: Kevin Wolf @ 2015-04-15 9:47 UTC (permalink / raw)
To: Andreas Färber; +Cc: Peter Maydell, Jeff Cody, qemu-devel, Stefan Hajnoczi
Am 15.04.2015 um 11:34 hat Andreas Färber geschrieben:
> Am 15.04.2015 um 11:26 schrieb Kevin Wolf:
> > Am 15.04.2015 um 06:53 hat Jeff Cody geschrieben:
> >> On Tue, Apr 14, 2015 at 11:57:35AM +0200, Kevin Wolf wrote:
> >>> Am 11.04.2015 um 05:41 hat Andreas Färber geschrieben:
> >>>> Hi,
> >>>>
> >>>> 001 seems to hang for -qcow (or is not reasonably "quick": >5 min).
> >>>>
> >>>> 033 is failing for -vhdx.
> >>>>
> >>>> (Note that `make check-block` only tests -qcow2, so didn't uncover
> >>>> either of them.)
> >>>>
> >>>> Given a failing test, am I seeing correctly that there is no command
> >>>> line option to skip this one failing test? -x seems to be for groups only.
> >>>>
> >>>> Regards,
> >>>> Andreas
> >>>>
> >>>> $ ./check -v -T -qcow -g quick
> >>>> [...]
> >>>> 001 6s ... [05:12:39]
> >>>
> >>> qcow1 is just really slow. 001 passes for me, after 202 seconds (that's
> >>> on my SSD, YMMV).
> >>>
> >>>> $ ./check -v -T -vhdx -g quick
> >>>> [...]
> >>>> 033 1s ... [04:06:09] [04:06:11] - output mismatch (see 033.out.bad)
> >>>
> >>> This seems to be because blkdebug doesn't implement .bdrv_truncate.
> >>> Currently the test case isn't suitable for VHDX, which uses explicit
> >>> bdrv_truncate() calls to grow the image file. I'll send a patch for
> >>> blkdebug to allow this.
> >>>
> >>> However, it seems that there is another problem which causes assertion
> >>> failures when using VHDX over blkdebug. Jeff, does the following fix
> >>> make sense to you? (I think it does, but I don't understand yet why the
> >>> assertion failure is only triggered with blkdebug - or in other words:
> >>> "how could this ever work?")
> >>>
> >>> Kevin
> >>
> >> Kevin,
> >>
> >> Yes, looking at that fix it makes sense - we are wanting to pad the
> >> back part of the block after the actual data with zeros. That back
> >> length should be (block size - (bytes avail + block offset)), which is
> >> iov2.iov_len.
> >>
> >> There are two reasons I think we haven't seen this issue (it has been
> >> hidden):
> >>
> >> 1.) If bs->file supports zero init, we don't do any of this
> >
> > I see. file does and blkdebug doesn't, so that's the crucial difference.
> >
> >> 2.) This is done for the case when the existing BAT state is
> >> PAYLOAD_BLOCK_ZERO. Until recently (commit 30af51c), we didn't
> >> create VHDX files with blocks in the PAYLOAD_BLOCK_ZERO state.
> >
> > Right, I wasn't aware of this either any more.
> >
> >> So it has been a latent bug in a hitherto rarely (if ever) exercised
> >> path.
> >
> > Thanks for your explanation, it's clear to me now what's going on. I'll
> > send out the patches (for both blkdebug and vhdx) right away. You can
> > either pick up the vhdx one, or just give your Acked-by and then I'll
> > merge it through my block tree.
>
> Might 059 (?) failure for -vmdk be another symptom of the same issue?
059 passes for me with vmdk. If it fails for you, can you please paste
the output diff?
Kevin
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [Qemu-devel] Failing iotests in v2.3.0-rc2 / master
2015-04-15 9:47 ` Kevin Wolf
@ 2015-04-15 9:54 ` Andreas Färber
0 siblings, 0 replies; 12+ messages in thread
From: Andreas Färber @ 2015-04-15 9:54 UTC (permalink / raw)
To: Kevin Wolf
Cc: Peter Maydell, Jeff Cody, qemu-devel, Stefan Hajnoczi,
Bruce Rogers
Am 15.04.2015 um 11:47 schrieb Kevin Wolf:
> Am 15.04.2015 um 11:34 hat Andreas Färber geschrieben:
>> Am 15.04.2015 um 11:26 schrieb Kevin Wolf:
>>> Am 15.04.2015 um 06:53 hat Jeff Cody geschrieben:
>>>> On Tue, Apr 14, 2015 at 11:57:35AM +0200, Kevin Wolf wrote:
>>>>> Am 11.04.2015 um 05:41 hat Andreas Färber geschrieben:
>>>>>> Hi,
>>>>>>
>>>>>> 001 seems to hang for -qcow (or is not reasonably "quick": >5 min).
>>>>>>
>>>>>> 033 is failing for -vhdx.
>>>>>>
>>>>>> (Note that `make check-block` only tests -qcow2, so didn't uncover
>>>>>> either of them.)
>>>>>>
>>>>>> Given a failing test, am I seeing correctly that there is no command
>>>>>> line option to skip this one failing test? -x seems to be for groups only.
>>>>>>
>>>>>> Regards,
>>>>>> Andreas
>>>>>>
>>>>>> $ ./check -v -T -qcow -g quick
>>>>>> [...]
>>>>>> 001 6s ... [05:12:39]
>>>>>
>>>>> qcow1 is just really slow. 001 passes for me, after 202 seconds (that's
>>>>> on my SSD, YMMV).
>>>>>
>>>>>> $ ./check -v -T -vhdx -g quick
>>>>>> [...]
>>>>>> 033 1s ... [04:06:09] [04:06:11] - output mismatch (see 033.out.bad)
>>>>>
>>>>> This seems to be because blkdebug doesn't implement .bdrv_truncate.
>>>>> Currently the test case isn't suitable for VHDX, which uses explicit
>>>>> bdrv_truncate() calls to grow the image file. I'll send a patch for
>>>>> blkdebug to allow this.
>>>>>
>>>>> However, it seems that there is another problem which causes assertion
>>>>> failures when using VHDX over blkdebug. Jeff, does the following fix
>>>>> make sense to you? (I think it does, but I don't understand yet why the
>>>>> assertion failure is only triggered with blkdebug - or in other words:
>>>>> "how could this ever work?")
>>>>>
>>>>> Kevin
>>>>
>>>> Kevin,
>>>>
>>>> Yes, looking at that fix it makes sense - we are wanting to pad the
>>>> back part of the block after the actual data with zeros. That back
>>>> length should be (block size - (bytes avail + block offset)), which is
>>>> iov2.iov_len.
>>>>
>>>> There are two reasons I think we haven't seen this issue (it has been
>>>> hidden):
>>>>
>>>> 1.) If bs->file supports zero init, we don't do any of this
>>>
>>> I see. file does and blkdebug doesn't, so that's the crucial difference.
>>>
>>>> 2.) This is done for the case when the existing BAT state is
>>>> PAYLOAD_BLOCK_ZERO. Until recently (commit 30af51c), we didn't
>>>> create VHDX files with blocks in the PAYLOAD_BLOCK_ZERO state.
>>>
>>> Right, I wasn't aware of this either any more.
>>>
>>>> So it has been a latent bug in a hitherto rarely (if ever) exercised
>>>> path.
>>>
>>> Thanks for your explanation, it's clear to me now what's going on. I'll
>>> send out the patches (for both blkdebug and vhdx) right away. You can
>>> either pick up the vhdx one, or just give your Acked-by and then I'll
>>> merge it through my block tree.
>>
>> Might 059 (?) failure for -vmdk be another symptom of the same issue?
>
> 059 passes for me with vmdk. If it fails for you, can you please paste
> the output diff?
With v2.3.0-rc3:
-raw:
[ 1714s] 005 [02:45:31] [02:45:31] - output mismatch (see
005.out.bad)
[ 1714s] ---
/home/abuild/rpmbuild/BUILD/qemu-2.3.0-rc3/tests/qemu-iotests/005.out
2015-04-13 18:34:01.000000000 +0000
[ 1714s] +++ 005.out.bad 2015-04-15 02:45:31.540000000 +0000
[ 1714s] @@ -1,13 +1,12 @@
[ 1714s] QA output created by 005
[ 1714s]
[ 1714s] creating large image
[ 1714s] +qemu-img: TEST_DIR/t.IMGFMT: The image size is too large for
file format 'IMGFMT'
[ 1714s] Formatting 'TEST_DIR/t.IMGFMT', fmt=IMGFMT size=5368709120000
[ 1714s]
[ 1714s] small read
[ 1714s] -read 4096/4096 bytes at offset 1024
[ 1714s] -4 KiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
[ 1714s] +read failed: Input/output error
[ 1714s]
[ 1714s] small write
[ 1714s] -wrote 4096/4096 bytes at offset 8192
[ 1714s] -4 KiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
[ 1714s] +write failed: Input/output error
[ 1714s] *** done
-qcow2:
[ 1867s] 028 [02:47:55] [02:48:04] - output mismatch (see
028.out.bad)
[ 1867s] ---
/home/abuild/rpmbuild/BUILD/qemu-2.3.0-rc3/tests/qemu-iotests/028.out
2015-04-13 18:34:01.000000000 +0000
[ 1867s] +++ 028.out.bad 2015-04-15 02:48:04.908000000 +0000
[ 1867s] @@ -473,6 +473,14 @@
[ 1867s] (qemu)
i^[[K^[[Din^[[K^[[D^[[Dinf^[[K^[[D^[[D^[[Dinfo^[[K^[[D^[[D^[[D^[[Dinfo
^[[K^[[D^[[D^[[D^[[D^[[Dinfo b^[[K^[[D^[[D^[[D^[[D^[[D^[[Dinfo
bl^[[K^[[D^[[D^[[D^[[D^[[D^[[D^[[Dinfo
blo^[[K^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[Dinfo bloc^[[K^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[Dinfo block^[[K^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[Dinfo
block-^[[K^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[Dinfo
block-j^[[K^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[Dinfo block-jo^[[K^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[Dinfo
block-job^[[K^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[Dinfo block-jobs^[[K
[ 1867s] Type backup, device disk: Completed 0 of 4294968832 bytes,
speed limit 0 bytes/s
[ 1867s]
i^[[K^[[Din^[[K^[[D^[[Dinf^[[K^[[D^[[D^[[Dinfo^[[K^[[D^[[D^[[D^[[Dinfo
^[[K^[[D^[[D^[[D^[[D^[[Dinfo b^[[K^[[D^[[D^[[D^[[D^[[D^[[Dinfo
bl^[[K^[[D^[[D^[[D^[[D^[[D^[[D^[[Dinfo
blo^[[K^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[Dinfo bloc^[[K^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[Dinfo block^[[K^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[Dinfo
block-^[[K^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[Dinfo
block-j^[[K^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[Dinfo block-jo^[[K^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[Dinfo
block-job^[[K^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[Dinfo block-jobs^[[K
[ 1867s] +Type backup, device disk: Completed 0 of 4294968832 bytes,
speed limit 0 bytes/s
[ 1867s]
+i^[[K^[[Din^[[K^[[D^[[Dinf^[[K^[[D^[[D^[[Dinfo^[[K^[[D^[[D^[[D^[[Dinfo
^[[K^[[D^[[D^[[D^[[D^[[Dinfo b^[[K^[[D^[[D^[[D^[[D^[[D^[[Dinfo
bl^[[K^[[D^[[D^[[D^[[D^[[D^[[D^[[Dinfo
blo^[[K^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[Dinfo bloc^[[K^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[Dinfo block^[[K^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[Dinfo
block-^[[K^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[Dinfo
block-j^[[K^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[Dinfo block-jo^[[K^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[Dinfo
block-job^[[K^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[Dinfo block-jobs^[[K
[ 1867s] +Type backup, device disk: Completed 0 of 4294968832 bytes,
speed limit 0 bytes/s
[ 1867s]
+i^[[K^[[Din^[[K^[[D^[[Dinf^[[K^[[D^[[D^[[Dinfo^[[K^[[D^[[D^[[D^[[Dinfo
^[[K^[[D^[[D^[[D^[[D^[[Dinfo b^[[K^[[D^[[D^[[D^[[D^[[D^[[Dinfo
bl^[[K^[[D^[[D^[[D^[[D^[[D^[[D^[[Dinfo
blo^[[K^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[Dinfo bloc^[[K^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[Dinfo block^[[K^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[Dinfo
block-^[[K^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[Dinfo
block-j^[[K^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[Dinfo block-jo^[[K^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[Dinfo
block-job^[[K^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[Dinfo block-jobs^[[K
[ 1867s] +Type backup, device disk: Completed 0 of 4294968832 bytes,
speed limit 0 bytes/s
[ 1867s]
+i^[[K^[[Din^[[K^[[D^[[Dinf^[[K^[[D^[[D^[[Dinfo^[[K^[[D^[[D^[[D^[[Dinfo
^[[K^[[D^[[D^[[D^[[D^[[Dinfo b^[[K^[[D^[[D^[[D^[[D^[[D^[[Dinfo
bl^[[K^[[D^[[D^[[D^[[D^[[D^[[D^[[Dinfo
blo^[[K^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[Dinfo bloc^[[K^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[Dinfo block^[[K^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[Dinfo
block-^[[K^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[Dinfo
block-j^[[K^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[Dinfo block-jo^[[K^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[Dinfo
block-job^[[K^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[Dinfo block-jobs^[[K
[ 1867s] +Type backup, device disk: Completed 131072 of 4294968832
bytes, speed limit 0 bytes/s
[ 1867s]
+i^[[K^[[Din^[[K^[[D^[[Dinf^[[K^[[D^[[D^[[Dinfo^[[K^[[D^[[D^[[D^[[Dinfo
^[[K^[[D^[[D^[[D^[[D^[[Dinfo b^[[K^[[D^[[D^[[D^[[D^[[D^[[Dinfo
bl^[[K^[[D^[[D^[[D^[[D^[[D^[[D^[[Dinfo
blo^[[K^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[Dinfo bloc^[[K^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[Dinfo block^[[K^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[Dinfo
block-^[[K^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[Dinfo
block-j^[[K^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[Dinfo block-jo^[[K^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[Dinfo
block-job^[[K^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[Dinfo block-jobs^[[K
[ 1867s] No active jobs
[ 1867s] === IO: pattern 195
[ 1867s] read 512/512 bytes at offset 3221194240
-qed:
[ 1946s] 028 [02:49:13] [02:49:23] - output mismatch (see
028.out.bad)
[ 1946s] ---
/home/abuild/rpmbuild/BUILD/qemu-2.3.0-rc3/tests/qemu-iotests/028.out
2015-04-13 18:34:01.000000000 +0000
[ 1946s] +++ 028.out.bad 2015-04-15 02:49:23.444000000 +0000
[ 1946s] @@ -473,6 +473,14 @@
[ 1946s] (qemu)
i^[[K^[[Din^[[K^[[D^[[Dinf^[[K^[[D^[[D^[[Dinfo^[[K^[[D^[[D^[[D^[[Dinfo
^[[K^[[D^[[D^[[D^[[D^[[Dinfo b^[[K^[[D^[[D^[[D^[[D^[[D^[[Dinfo
bl^[[K^[[D^[[D^[[D^[[D^[[D^[[D^[[Dinfo
blo^[[K^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[Dinfo bloc^[[K^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[Dinfo block^[[K^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[Dinfo
block-^[[K^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[Dinfo
block-j^[[K^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[Dinfo block-jo^[[K^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[Dinfo
block-job^[[K^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[Dinfo block-jobs^[[K
[ 1946s] Type backup, device disk: Completed 0 of 4294968832 bytes,
speed limit 0 bytes/s
[ 1946s]
i^[[K^[[Din^[[K^[[D^[[Dinf^[[K^[[D^[[D^[[Dinfo^[[K^[[D^[[D^[[D^[[Dinfo
^[[K^[[D^[[D^[[D^[[D^[[Dinfo b^[[K^[[D^[[D^[[D^[[D^[[D^[[Dinfo
bl^[[K^[[D^[[D^[[D^[[D^[[D^[[D^[[Dinfo
blo^[[K^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[Dinfo bloc^[[K^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[Dinfo block^[[K^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[Dinfo
block-^[[K^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[Dinfo
block-j^[[K^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[Dinfo block-jo^[[K^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[Dinfo
block-job^[[K^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[Dinfo block-jobs^[[K
[ 1946s] +Type backup, device disk: Completed 0 of 4294968832 bytes,
speed limit 0 bytes/s
[ 1946s]
+i^[[K^[[Din^[[K^[[D^[[Dinf^[[K^[[D^[[D^[[Dinfo^[[K^[[D^[[D^[[D^[[Dinfo
^[[K^[[D^[[D^[[D^[[D^[[Dinfo b^[[K^[[D^[[D^[[D^[[D^[[D^[[Dinfo
bl^[[K^[[D^[[D^[[D^[[D^[[D^[[D^[[Dinfo
blo^[[K^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[Dinfo bloc^[[K^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[Dinfo block^[[K^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[Dinfo
block-^[[K^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[Dinfo
block-j^[[K^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[Dinfo block-jo^[[K^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[Dinfo
block-job^[[K^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[Dinfo block-jobs^[[K
[ 1946s] +Type backup, device disk: Completed 0 of 4294968832 bytes,
speed limit 0 bytes/s
[ 1946s]
+i^[[K^[[Din^[[K^[[D^[[Dinf^[[K^[[D^[[D^[[Dinfo^[[K^[[D^[[D^[[D^[[Dinfo
^[[K^[[D^[[D^[[D^[[D^[[Dinfo b^[[K^[[D^[[D^[[D^[[D^[[D^[[Dinfo
bl^[[K^[[D^[[D^[[D^[[D^[[D^[[D^[[Dinfo
blo^[[K^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[Dinfo bloc^[[K^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[Dinfo block^[[K^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[Dinfo
block-^[[K^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[Dinfo
block-j^[[K^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[Dinfo block-jo^[[K^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[Dinfo
block-job^[[K^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[Dinfo block-jobs^[[K
[ 1946s] +Type backup, device disk: Completed 0 of 4294968832 bytes,
speed limit 0 bytes/s
[ 1946s]
+i^[[K^[[Din^[[K^[[D^[[Dinf^[[K^[[D^[[D^[[Dinfo^[[K^[[D^[[D^[[D^[[Dinfo
^[[K^[[D^[[D^[[D^[[D^[[Dinfo b^[[K^[[D^[[D^[[D^[[D^[[D^[[Dinfo
bl^[[K^[[D^[[D^[[D^[[D^[[D^[[D^[[Dinfo
blo^[[K^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[Dinfo bloc^[[K^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[Dinfo block^[[K^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[Dinfo
block-^[[K^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[Dinfo
block-j^[[K^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[Dinfo block-jo^[[K^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[Dinfo
block-job^[[K^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[Dinfo block-jobs^[[K
[ 1946s] +Type backup, device disk: Completed 131072 of 4294968832
bytes, speed limit 0 bytes/s
[ 1946s]
+i^[[K^[[Din^[[K^[[D^[[Dinf^[[K^[[D^[[D^[[Dinfo^[[K^[[D^[[D^[[D^[[Dinfo
^[[K^[[D^[[D^[[D^[[D^[[Dinfo b^[[K^[[D^[[D^[[D^[[D^[[D^[[Dinfo
bl^[[K^[[D^[[D^[[D^[[D^[[D^[[D^[[Dinfo
blo^[[K^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[Dinfo bloc^[[K^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[Dinfo block^[[K^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[Dinfo
block-^[[K^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[Dinfo
block-j^[[K^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[Dinfo block-jo^[[K^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[Dinfo
block-job^[[K^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[Dinfo block-jobs^[[K
[ 1946s] No active jobs
[ 1946s] === IO: pattern 195
[ 1946s] read 512/512 bytes at offset 3221194240
-vmdk:
[ 2125s] 059 [02:52:18] [02:52:22] - output mismatch (see
059.out.bad)
[ 2125s] ---
/home/abuild/rpmbuild/BUILD/qemu-2.3.0-rc3/tests/qemu-iotests/059.out
2015-04-13 18:34:01.000000000 +0000
[ 2125s] +++ 059.out.bad 2015-04-15 02:52:22.364000000 +0000
[ 2125s] @@ -2264,76 +2264,14 @@
[ 2125s] 512 bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
[ 2125s]
[ 2125s] === Testing 4TB monolithicFlat creation and IO ===
[ 2125s] +qemu-img: TEST_DIR/iotest-version3.IMGFMT: Could not truncate
file: File too large
[ 2125s] Formatting 'TEST_DIR/iotest-version3.IMGFMT', fmt=IMGFMT
size=4398046511104
[ 2125s] image: TEST_DIR/iotest-version3.IMGFMT
[ 2125s] file format: IMGFMT
[ 2125s] -virtual size: 4.0T (4398046511104 bytes)
[ 2125s] -wrote 512/512 bytes at offset 966367641600
[ 2125s] -512 bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
[ 2125s] -e100000000: 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a
................
[ 2125s] -e100000010: 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a
................
[ 2125s] -e100000020: 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a
................
[ 2125s] -e100000030: 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a
................
[ 2125s] -e100000040: 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a
................
[ 2125s] -e100000050: 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a
................
[ 2125s] -e100000060: 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a
................
[ 2125s] -e100000070: 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a
................
[ 2125s] -e100000080: 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a
................
[ 2125s] -e100000090: 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a
................
[ 2125s] -e1000000a0: 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a
................
[ 2125s] -e1000000b0: 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a
................
[ 2125s] -e1000000c0: 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a
................
[ 2125s] -e1000000d0: 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a
................
[ 2125s] -e1000000e0: 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a
................
[ 2125s] -e1000000f0: 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a
................
[ 2125s] -e100000100: 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a
................
[ 2125s] -e100000110: 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a
................
[ 2125s] -e100000120: 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a
................
[ 2125s] -e100000130: 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a
................
[ 2125s] -e100000140: 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a
................
[ 2125s] -e100000150: 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a
................
[ 2125s] -e100000160: 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a
................
[ 2125s] -e100000170: 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a
................
[ 2125s] -e100000180: 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a
................
[ 2125s] -e100000190: 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a
................
[ 2125s] -e1000001a0: 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a
................
[ 2125s] -e1000001b0: 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a
................
[ 2125s] -e1000001c0: 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a
................
[ 2125s] -e1000001d0: 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a
................
[ 2125s] -e1000001e0: 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a
................
[ 2125s] -e1000001f0: 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a 0a
................
[ 2125s] -e100000200: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
................
[ 2125s] -e100000210: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
................
[ 2125s] -e100000220: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
................
[ 2125s] -e100000230: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
................
[ 2125s] -e100000240: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
................
[ 2125s] -e100000250: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
................
[ 2125s] -e100000260: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
................
[ 2125s] -e100000270: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
................
[ 2125s] -e100000280: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
................
[ 2125s] -e100000290: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
................
[ 2125s] -e1000002a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
................
[ 2125s] -e1000002b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
................
[ 2125s] -e1000002c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
................
[ 2125s] -e1000002d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
................
[ 2125s] -e1000002e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
................
[ 2125s] -e1000002f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
................
[ 2125s] -e100000300: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
................
[ 2125s] -e100000310: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
................
[ 2125s] -e100000320: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
................
[ 2125s] -e100000330: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
................
[ 2125s] -e100000340: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
................
[ 2125s] -e100000350: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
................
[ 2125s] -e100000360: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
................
[ 2125s] -e100000370: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
................
[ 2125s] -e100000380: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
................
[ 2125s] -e100000390: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
................
[ 2125s] -e1000003a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
................
[ 2125s] -e1000003b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
................
[ 2125s] -e1000003c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
................
[ 2125s] -e1000003d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
................
[ 2125s] -e1000003e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
................
[ 2125s] -e1000003f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
................
[ 2125s] -read 1024/1024 bytes at offset 966367641600
[ 2125s] -1 KiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
[ 2125s] +virtual size: 16G (17179869184 bytes)
[ 2125s] +cluster_size: 65536
[ 2125s] +qemu-io: can't open device
/home/abuild/rpmbuild/BUILD/qemu-2.3.0-rc3/tests/qemu-iotests/scratch/iotest-version3.vmdk:
VMDK version 3 must be read only
[ 2125s] +no file open, try 'help open'
[ 2125s] +qemu-io: can't open device
/home/abuild/rpmbuild/BUILD/qemu-2.3.0-rc3/tests/qemu-iotests/scratch/iotest-version3.vmdk:
VMDK version 3 must be read only
[ 2125s] +no file open, try 'help open'
[ 2125s] *** done
https://build.opensuse.org/build/Virtualization/openSUSE_Factory/x86_64/qemu-testsuite/_log
Regards,
Andreas
--
SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Jennifer Guild, Dilip Upmanyu,
Graham Norton; HRB 21284 (AG Nürnberg)
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [Qemu-devel] Failing iotests in v2.3.0-rc2 / master
2015-04-14 9:57 ` Kevin Wolf
2015-04-15 4:53 ` Jeff Cody
@ 2015-04-15 11:27 ` Jeff Cody
1 sibling, 0 replies; 12+ messages in thread
From: Jeff Cody @ 2015-04-15 11:27 UTC (permalink / raw)
To: Kevin Wolf
Cc: Peter Maydell, Andreas Färber, Stefan Hajnoczi, qemu-devel
On Tue, Apr 14, 2015 at 11:57:35AM +0200, Kevin Wolf wrote:
[snip]
> --- a/block/vhdx.c
> +++ b/block/vhdx.c
> @@ -1285,7 +1285,7 @@ static coroutine_fn int vhdx_co_writev(BlockDriverState *bs, int64_t sector_num,
> iov2.iov_base = qemu_blockalign(bs, iov2.iov_len);
> memset(iov2.iov_base, 0, iov2.iov_len);
> qemu_iovec_concat_iov(&hd_qiov, &iov2, 1, 0,
> - sinfo.block_offset);
> + iov2.iov_len);
> sectors_to_write += iov2.iov_len >> BDRV_SECTOR_BITS;
> }
> }
acked-by: Jeff Cody <jcody@redhat.com>
^ permalink raw reply [flat|nested] 12+ messages in thread
end of thread, other threads:[~2015-04-15 11:27 UTC | newest]
Thread overview: 12+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2015-04-11 3:41 [Qemu-devel] Failing iotests in v2.3.0-rc2 / master Andreas Färber
2015-04-11 14:33 ` Andreas Färber
2015-04-13 16:42 ` Paolo Bonzini
2015-04-13 15:29 ` John Snow
2015-04-13 17:03 ` Andreas Färber
2015-04-14 9:57 ` Kevin Wolf
2015-04-15 4:53 ` Jeff Cody
2015-04-15 9:26 ` Kevin Wolf
2015-04-15 9:34 ` Andreas Färber
2015-04-15 9:47 ` Kevin Wolf
2015-04-15 9:54 ` Andreas Färber
2015-04-15 11:27 ` Jeff Cody
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).