From: Eric Blake <eblake@redhat.com>
To: Max Reitz <mreitz@redhat.com>, qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>,
"open list:Block layer core" <qemu-block@nongnu.org>
Subject: Re: [PATCH v3 2/4] iotests: Switch nbd tests to use Unix rather than TCP
Date: Mon, 18 Nov 2019 16:36:09 -0600 [thread overview]
Message-ID: <d1a92f5b-b752-747e-cb2c-f98ffb26d53a@redhat.com> (raw)
In-Reply-To: <aa6a8693-da5d-d12f-1dd9-ee98691c3b52@redhat.com>
On 11/18/19 4:18 PM, Eric Blake wrote:
>>
>> If anything, I'm inclined to use $SOCK_DIR/nbd.raw to indicate that
>> the NBD client sees raw format, regardless of the format in use by the
>> server, to leave the door open for $SOCK_DIR/nbd.qcow2 when we finally
>> are happy to test qcow2 format over NBD.
>
> Naming the socket $SOCK_DIR/nbd.raw means that filters tend to rename it
> to $SOCK_DIR/nbd.IMGFMT before my attempt to rename everything to
> TEST_DIR/t.IMGFMT. So I'm now leaning towards just naming the socket
> $SOCK_DIR/nbd and leave it at that.
>
>>
>> Or stick to just $SOCK_DIR/nbd hard-coded everywhere, and quit trying
>> to use $IMGFMT in the socket name, to make all the usage consistent.
In order to get my NBD 4.2-rc2 pull request out, I'll be squashing this
in (having tested that my usual iotest configurations still pass)::
diff --git i/tests/qemu-iotests/common.rc w/tests/qemu-iotests/common.rc
index f772dcb67322..0cc8acc9edd2 100644
--- i/tests/qemu-iotests/common.rc
+++ w/tests/qemu-iotests/common.rc
@@ -217,7 +217,7 @@ if [ "$IMGOPTSSYNTAX" = "true" ]; then
TEST_IMG="$DRIVER,file.filename=$TEST_DIR/t.$IMGFMT"
elif [ "$IMGPROTO" = "nbd" ]; then
TEST_IMG_FILE=$TEST_DIR/t.$IMGFMT
-
TEST_IMG="$DRIVER,file.driver=nbd,file.type=unix,file.path=$SOCKDIR/$IMGFMT"
+
TEST_IMG="$DRIVER,file.driver=nbd,file.type=unix,file.path=$SOCKDIR/nbd"
elif [ "$IMGPROTO" = "ssh" ]; then
TEST_IMG_FILE=$TEST_DIR/t.$IMGFMT
TEST_IMG="$DRIVER,file.driver=ssh,file.host=127.0.0.1,file.path=$TEST_IMG_FILE"
@@ -349,7 +349,10 @@ _make_test_img()
fi
) | _filter_img_create
- # Start an NBD server on the image file, which is what we'll be
talking to
+ # Start an NBD server on the image file, which is what we'll be
talking to.
+ # Once NBD gains resize support, we may also want to use -f raw at the
+ # server and interpret format over NBD, but for now, the format is
+ # interpreted at the server and raw data sent over NBD.
if [ $IMGPROTO = "nbd" ]; then
# Pass a sufficiently high number to -e that should be enough
for all
# tests
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3226
Virtualization: qemu.org | libvirt.org
next prev parent reply other threads:[~2019-11-18 22:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-14 21:34 [PATCH v3 for-4.2 0/4] tests: More iotest 223 improvements Eric Blake
2019-11-14 21:34 ` [PATCH v3 1/4] iotests: Fix 173 Eric Blake
2019-11-14 21:34 ` [PATCH v3 2/4] iotests: Switch nbd tests to use Unix rather than TCP Eric Blake
2019-11-18 17:29 ` Max Reitz
2019-11-18 17:42 ` Eric Blake
2019-11-18 17:57 ` Eric Blake
2019-11-18 18:44 ` Max Reitz
2019-11-18 22:18 ` Eric Blake
2019-11-18 22:36 ` Eric Blake [this message]
2019-11-14 21:34 ` [PATCH v3 3/4] iotests: Include QMP input in .out files Eric Blake
2019-11-18 17:37 ` Max Reitz
2019-11-14 21:34 ` [PATCH v3 4/4] tests: More iotest 223 improvements Eric Blake
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=d1a92f5b-b752-747e-cb2c-f98ffb26d53a@redhat.com \
--to=eblake@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
/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).