All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: Fam Zheng <famcool@gmail.com>
Cc: Qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] vmdk fails qemu-iotest 019
Date: Wed, 08 Jun 2011 15:52:52 +0200	[thread overview]
Message-ID: <4DEF7EB4.9070602@redhat.com> (raw)
In-Reply-To: <BANLkTimkUHvsYcphRF_ja3E3MoAoQnAT0Q@mail.gmail.com>

Am 08.06.2011 15:29, schrieb Fam Zheng:
> Yes I noticed the failure, but it's trivial mismatch between `qemu-img
> create` output. The old test case has "cluster_size=65536" but I find
> the latest qemu-img omits this info, as the diff:
> 
> -Formatting 'TEST_DIR/t.IMGFMT', fmt=IMGFMT size=6442450944 cluster_size=65536
> +Formatting 'TEST_DIR/t.IMGFMT', fmt=IMGFMT size=6442450944
> 
> Is this your case too?

No, I get real errors, pattern mismatches:


[ Before this, there are some successful writes ]

Testing conversion with -B TEST_DIR/t.IMGFMT.base

Checking if backing clusters are allocated when they shouldn't

qemu-io> 0/128 sectors allocated at offset 1 MiB
qemu-io> qemu-io> 0/128 sectors allocated at offset 4.001 GiB
qemu-io> Reading

=== IO: pattern 42
qemu-io> Pattern verification failed at offset 0, 512 bytes
read 512/512 bytes at offset 0
512.000000 bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
qemu-io> Pattern verification failed at offset 1024, 512 bytes
read 512/512 bytes at offset 1024
512.000000 bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
qemu-io> Pattern verification failed at offset 2048, 512 bytes

[ More pattern verification errors follow ]

  reply	other threads:[~2011-06-08 13:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-08 13:16 [Qemu-devel] vmdk fails qemu-iotest 019 Kevin Wolf
2011-06-08 13:29 ` Fam Zheng
2011-06-08 13:52   ` Kevin Wolf [this message]
2011-06-08 14:17     ` Fam Zheng
2011-06-08 14:55       ` Kevin Wolf
2011-06-09  9:31         ` Stefan Hajnoczi

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=4DEF7EB4.9070602@redhat.com \
    --to=kwolf@redhat.com \
    --cc=Qemu-devel@nongnu.org \
    --cc=famcool@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.