From: John Snow <jsnow@redhat.com>
To: Eric Blake <eblake@redhat.com>, qemu-devel@nongnu.org
Cc: vsementsov@virtuozzo.com, qemu-block@nongnu.org
Subject: Re: [Qemu-devel] [Qemu-block] [PATCH] docs: Update preferred NBD device syntax
Date: Tue, 3 Sep 2019 14:50:15 -0400 [thread overview]
Message-ID: <9bde61cf-b4a7-fb11-7b8d-12cf8a2dc558@redhat.com> (raw)
In-Reply-To: <20190903145634.20237-1-eblake@redhat.com>
On 9/3/19 10:56 AM, Eric Blake wrote:
> Mention the preferred URI form, especially since NBD is trying to
> standardize that form: https://lists.debian.org/nbd/2019/06/msg00012.html
>
> Signed-off-by: Eric Blake <eblake@redhat.com>
> ---
> qemu-doc.texi | 16 +++++++++++-----
> 1 file changed, 11 insertions(+), 5 deletions(-)
>
> diff --git a/qemu-doc.texi b/qemu-doc.texi
> index 577d1e837640..c83fb347d77e 100644
> --- a/qemu-doc.texi
> +++ b/qemu-doc.texi
> @@ -297,7 +297,14 @@ qemu-system-i386 -drive file=iscsi://192.0.2.1/iqn.2001-04.com.example/1
>
> @item NBD
> QEMU supports NBD (Network Block Devices) both using TCP protocol as well
> -as Unix Domain Sockets.
> +as Unix Domain Sockets. With TCP, the default port is 10809.
>
> -Syntax for specifying a NBD device using TCP
> +Syntax for specifying a NBD device using TCP, in preferred URI form:
> +``nbd://<server-ip>[:<port>]/[<export>]''
> +
> +Syntax for specifying a NBD device using Unix Domain Sockets; remember
> +that '?' is a shell glob character and may need quoting:
> +``nbd+unix:///[<export>]?socket=<domain-socket>''
> +
> +Older syntax that is also recognized:
Deprecated officially, or no?
> ``nbd:<server-ip>:<port>[:exportname=<export>]''
>
> -Syntax for specifying a NBD device using Unix Domain Sockets
> ``nbd:unix:<domain-socket>[:exportname=<export>]''
>
> Example for TCP
> @example
> -qemu-system-i386 --drive file=nbd:192.0.2.1:30000
> +qemu-system-i386 --drive file=nbd://192.0.2.1:30000
> @end example
>
> Example for Unix Domain Sockets
> @example
> -qemu-system-i386 --drive file=nbd:unix:/tmp/nbd-socket
> +qemu-system-i386 --drive "file=nbd+unix:///?socket=/tmp/nbd-socket"
> @end example
>
> @item SSH
>
Reviewed-by: John Snow <jsnow@redhat.com>
next prev parent reply other threads:[~2019-09-03 18:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-03 14:56 [Qemu-devel] [PATCH] docs: Update preferred NBD device syntax Eric Blake
2019-09-03 18:50 ` John Snow [this message]
2019-09-03 19:02 ` [Qemu-devel] [Qemu-block] " Eric Blake
2019-09-03 19:06 ` John Snow
2019-09-04 8:18 ` Daniel P. Berrangé
2019-09-04 12:50 ` 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=9bde61cf-b4a7-fb11-7b8d-12cf8a2dc558@redhat.com \
--to=jsnow@redhat.com \
--cc=eblake@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=vsementsov@virtuozzo.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).