qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: Fam Zheng <famz@redhat.com>
Cc: qemu-devel@nongnu.org, stefanha@redhat.com
Subject: Re: [Qemu-devel] [PATCH] qemu-iotests: Test subformats for vmdk
Date: Wed, 17 Apr 2013 15:06:35 +0200	[thread overview]
Message-ID: <20130417130634.GF3365@dhcp-200-207.str.redhat.com> (raw)
In-Reply-To: <1366203538-28104-1-git-send-email-famz@redhat.com>

Am 17.04.2013 um 14:58 hat Fam Zheng geschrieben:
> Added format options for testing vmdk subformats:
> 
>     $ ./check -h
>     Usage: ./check [options] [testlist]
> 
>     common options
>         -v          verbose
> 
>     check options
>         ...
>         -vpc                test vpc
>         -vmdk               test vmdk (identical to -vmdk-monolithicSparse)
>         -vmdk-monolithicSparse
>                             test vmdk monolithic sparse
>         -vmdk-monolithicFlat
>                             test vmdk monolithic flat
>         -vmdk-twoGbMaxExtentSparse
>                             test vmdk two gb splitted sparse
>         -vmdk-twoGbMaxExtentFlat
>                             test vmdk two gb splitted sparse
>         -rbd                test rbd
>         ...
> 
> Signed-off-by: Fam Zheng <famz@redhat.com>

Shouldn't -o be enough to cover all of this? For example, we're also
running qcow2 tests with -o compat=[0.10|1.1] and don't introduce a
separate option for each.

In practice, of course, the problem is that the non-default is rarely
run. Maybe we should add a tests/qemu-iotest-slow.sh that covers some
more combinations.

> @@ -124,6 +127,7 @@ _make_test_img()
>              -e "s# compat='[^']*'##g" \
>              -e "s# compat6=\\(on\\|off\\)##g" \
>              -e "s# static=\\(on\\|off\\)##g" \
> +            -e "s# subformat='[^']*'##g" \
>              -e "s# lazy_refcounts=\\(on\\|off\\)##g"
>  
>      # Start an NBD server on the image file, which is what we'll be talking to

This hunk we'll need in any case, of course.

Kevin

  reply	other threads:[~2013-04-17 13:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-17 12:58 [Qemu-devel] [PATCH] qemu-iotests: Test subformats for vmdk Fam Zheng
2013-04-17 13:06 ` Kevin Wolf [this message]
2013-04-18  2:26   ` Fam Zheng

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=20130417130634.GF3365@dhcp-200-207.str.redhat.com \
    --to=kwolf@redhat.com \
    --cc=famz@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).