From: Max Reitz <mreitz@redhat.com>
To: Fam Zheng <famz@redhat.com>, qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>, Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] qemu-iotests: Skip 099 for VMDK subformats with desc file
Date: Wed, 03 Dec 2014 09:30:36 +0100 [thread overview]
Message-ID: <547ECA2C.8000107@redhat.com> (raw)
In-Reply-To: <1417571370-19495-1-git-send-email-famz@redhat.com>
On 2014-12-03 at 02:49, Fam Zheng wrote:
> VMDK extent parsing code doesn't handle the JSON file name, so the case
> fails for these subformats. Disabled them.
>
> Signed-off-by: Fam Zheng <famz@redhat.com>
> ---
> tests/qemu-iotests/099 | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/tests/qemu-iotests/099 b/tests/qemu-iotests/099
> index ffc7ea7..fb920fe 100755
> --- a/tests/qemu-iotests/099
> +++ b/tests/qemu-iotests/099
> @@ -44,7 +44,8 @@ trap "_cleanup; exit \$status" 0 1 2 3 15
> _supported_fmt qcow qcow2 qed vdi vhdx vmdk vpc
> _supported_proto file
> _supported_os Linux
> -
> +_unsupported_imgopts "subformat=monolithicFlat" "subformat=twoGbMaxExtentFlat" \
> + "subformat=twoGbMaxExtentSparse"
>
> function do_run_qemu()
> {
This is most certainly necessary, therefore: Thanks, applied to my
block-next tree:
https://github.com/XanClic/qemu/commits/block-next
However, as I said in our private email exchange, we need to fix the
error message, too.
$ qemu-img create -f vmdk -o subformat=monolithicFlat test.vmdk 64M
Formatting 'test.vmdk', fmt=vmdk size=67108864 compat6=off
subformat='monolithicFlat'
$ qemu-io -c 'open -o
file.driver=blkdebug,file.image.filename=test.vmdk,file.inject-error.0.event=read_aio'
qemu-io: can't open: Could not parse the JSON options
That's not very helpful. I'll send a patch for that.
Max
prev parent reply other threads:[~2014-12-03 8:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-03 1:49 [Qemu-devel] [PATCH] qemu-iotests: Skip 099 for VMDK subformats with desc file Fam Zheng
2014-12-03 8:30 ` Max Reitz [this message]
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=547ECA2C.8000107@redhat.com \
--to=mreitz@redhat.com \
--cc=famz@redhat.com \
--cc=kwolf@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 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.