Max,
Since you once fixed VMDK with the json descriptor filename, could you take a
look at the error:
$ ./check -vmdk -o "subformat=monolithicFlat" 033
033 - output mismatch (see 033.out.bad)
--- /home/fam/qemu/tests/qemu-iotests/033.out 2015-05-05 10:52:50.524378312
+0800
+++ 033.out.bad 2015-05-05 17:38:36.147369924 +0800
@@ -2,54 +2,36 @@
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)
+qemu-io: can't open device blkdebug::/tmp/qemu-iotests/t.vmdk: Cannot use
relative extent paths with VMDK descriptor file 'json:{"image": {"driver":
"file", "filename": "/tmp/qemu-iotests/t.vmdk"}, "driver": "blkdebug", "align":
"512"}'
+qemu-io: can't open device blkdebug::/tmp/qemu-iotests/t.vmdk: Cannot use
relative extent paths with VMDK descriptor file 'json:{"image": {"driver":
"file", "filename": "/tmp/qemu-iotests/t.vmdk"}, "driver": "blkdebug", "align":
"512"}'
+qemu-io: can't open device blkdebug::/tmp/qemu-iotests/t.vmdk: Cannot use
relative extent paths with VMDK descriptor file 'json:{"image": {"driver":
"file", "filename": "/tmp/qemu-iotests/t.vmdk"}, "driver": "blkdebug", "align":
"512"}'
...
I'm not sure what's the best fix here. It's possible to dig out
bs->file->file->filename in this case, but I'm not sure what's the rule of this
filename mystery.
Fam
