From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:42103) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YpaKs-0002JC-3c for qemu-devel@nongnu.org; Tue, 05 May 2015 06:44:23 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YpaKo-0002Lf-2V for qemu-devel@nongnu.org; Tue, 05 May 2015 06:44:22 -0400 Received: from mx1.redhat.com ([209.132.183.28]:55653) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YpaKn-0002LZ-Rp for qemu-devel@nongnu.org; Tue, 05 May 2015 06:44:18 -0400 Received: from int-mx09.intmail.prod.int.phx2.redhat.com (int-mx09.intmail.prod.int.phx2.redhat.com [10.5.11.22]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id t45AiHnL027113 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL) for ; Tue, 5 May 2015 06:44:17 -0400 Date: Tue, 5 May 2015 18:44:15 +0800 From: Fam Zheng Message-ID: <20150505104415.GB9322@ad.nay.redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Subject: [Qemu-devel] blkdebug and VMDK (iotests 033 failure on monolithicFlat) List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org, mreitz@redhat.com Cc: kwolf@redhat.com, stefanha@redhat.com 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