From: Kevin Wolf <kwolf@redhat.com>
To: Jeff Cody <jcody@redhat.com>
Cc: qemu-devel@nongnu.org, stefanha@redhat.com
Subject: Re: [Qemu-devel] [PATCH v3 2/3] block: qemu-iotests for vhdx, read sample dynamic image
Date: Fri, 27 Sep 2013 11:14:55 +0200 [thread overview]
Message-ID: <20130927091455.GA2440@dhcp-200-207.str.redhat.com> (raw)
In-Reply-To: <f6c072bfb4476b11d6ce568fb05407080eb2fac0.1380110346.git.jcody@redhat.com>
Am 25.09.2013 um 14:12 hat Jeff Cody geschrieben:
> This adds the VHDX format to the qemu-iotests format, and adds
> a read test. The test reads from an existing sample image, that
> was created with Hyper-V under Windwos Server 2012.
>
> The image file is a 1GB dynamic image, with 32MB blocks.
>
> The pattern 0xa5 exists from 0MB-33MB (past a block size boundary)
>
> The pattern 0x96 exists from 33MB-66MB (past another block boundary,
> and leaving a partial blank block)
>
> From 66MB-1024MB, all reads should return 0.
>
> Although 1GB dynamic image with 66MB of data, the bzip2'ed image
> file size is only 874 bytes.
>
> Signed-off-by: Jeff Cody <jcody@redhat.com>
> Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
> diff --git a/tests/qemu-iotests/064.out b/tests/qemu-iotests/064.out
> new file mode 100644
> index 0000000..b9e8e4a
> --- /dev/null
> +++ b/tests/qemu-iotests/064.out
> @@ -0,0 +1,14 @@
> +QA output created by 064
> +
> +=== Verify pattern 0xa5, 0 - 33MB ===
> +read 34603008/34603008 bytes at offset 0
> +33 MiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
> +
> +=== Verify pattern 0x96, 33M - 66M ===
> +read 34603008/34603008 bytes at offset 34603008
> +33 MiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
> +
> +=== Verify pattern 0x00, 66M - 1024M ===
> +read 1004535808/1004535808 bytes at offset 69206016
> +958 MiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
> +*** done
Doesn't work for me. Am I missing patches that need to be applied first?
064 1s ... [11:09:58] [11:09:59] - output mismatch (see 064.out.bad)
--- 064.out 2013-09-27 11:00:37.077677734 +0200
+++ 064.out.bad 2013-09-27 11:09:59.704298133 +0200
@@ -1,14 +1,14 @@
QA output created by 064
=== Verify pattern 0xa5, 0 - 33MB ===
-read 34603008/34603008 bytes at offset 0
-33 MiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
+qemu-io: can't open device /home/kwolf/source/qemu/tests/qemu-iotests/scratch/iotest-dynamic-1G.vhdx: Could not open '/home/kwolf/source/qemu/tests/qemu-iotests/scratch/iotest-dynamic-1G.vhdx': Operation not supported
+no file open, try 'help open'
=== Verify pattern 0x96, 33M - 66M ===
-read 34603008/34603008 bytes at offset 34603008
-33 MiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
+qemu-io: can't open device /home/kwolf/source/qemu/tests/qemu-iotests/scratch/iotest-dynamic-1G.vhdx: Could not open '/home/kwolf/source/qemu/tests/qemu-iotests/scratch/iotest-dynamic-1G.vhdx': Operation not supported
+no file open, try 'help open'
=== Verify pattern 0x00, 66M - 1024M ===
-read 1004535808/1004535808 bytes at offset 69206016
-958 MiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
+qemu-io: can't open device /home/kwolf/source/qemu/tests/qemu-iotests/scratch/iotest-dynamic-1G.vhdx: Could not open '/home/kwolf/source/qemu/tests/qemu-iotests/scratch/iotest-dynamic-1G.vhdx': Operation not supported
+no file open, try 'help open'
*** done
Kevin
next prev parent reply other threads:[~2013-09-27 9:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-25 12:12 [Qemu-devel] [PATCH v3 0/3] qemu-iotests with sample images, vhdx test, cleanup Jeff Cody
2013-09-25 12:12 ` [Qemu-devel] [PATCH v3 1/3] block: qemu-iotests - add basic ability to use binary sample images Jeff Cody
2013-09-25 12:12 ` [Qemu-devel] [PATCH v3 2/3] block: qemu-iotests for vhdx, read sample dynamic image Jeff Cody
2013-09-27 2:31 ` Fam Zheng
2013-09-27 9:14 ` Kevin Wolf [this message]
2013-09-27 11:35 ` Jeff Cody
2013-09-25 12:12 ` [Qemu-devel] [PATCH v3 3/3] block: qemu-iotests - quote $TEST_IMG* and $TEST_DIR usage Jeff Cody
2013-09-27 9:15 ` [Qemu-devel] [PATCH v3 0/3] qemu-iotests with sample images, vhdx test, cleanup Kevin Wolf
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130927091455.GA2440@dhcp-200-207.str.redhat.com \
--to=kwolf@redhat.com \
--cc=jcody@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).