From: Fam Zheng <famz@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: qemu-devel@nongnu.org, stefanha@redhat.com
Subject: Re: [Qemu-devel] [PATCH] qemu-iotests: Test subformats for vmdk
Date: Thu, 18 Apr 2013 10:26:15 +0800 [thread overview]
Message-ID: <20130418022615.GA23480@localhost.localdomain> (raw)
In-Reply-To: <20130417130634.GF3365@dhcp-200-207.str.redhat.com>
On Wed, 04/17 15:06, Kevin Wolf wrote:
> 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.
Agreed, OK.
>
> > @@ -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.
OK.
I'll include this later in with more VMDK tests.
--
Fam
prev parent reply other threads:[~2013-04-18 2:26 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
2013-04-18 2:26 ` Fam Zheng [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=20130418022615.GA23480@localhost.localdomain \
--to=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 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).