qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Lieven <pl@kamp.de>
To: Ashijeet Acharya <ashijeetacharya@gmail.com>,
	Eric Blake <eblake@redhat.com>
Cc: Stefan Hajnoczi <stefanha@gmail.com>,
	Kevin Wolf <kwolf@redhat.com>,
	qemu-block@nongnu.org, jcody@redhat.com,
	QEMU Developers <qemu-devel@nongnu.org>,
	Max Reitz <mreitz@redhat.com>
Subject: Re: [Qemu-devel] [Qemu-block] block/nfs: Fine grained runtime options in nfs
Date: Tue, 18 Oct 2016 12:41:56 +0200	[thread overview]
Message-ID: <61e334e1-bfe5-7907-cad1-a490ec10f8da@kamp.de> (raw)
In-Reply-To: <CAC2QTZYoySpD+fVkk0gaaJy36D+3=DoYiYNLAj5Yum4pcAJXhw@mail.gmail.com>

Am 17.10.2016 um 21:34 schrieb Ashijeet Acharya:
> On Tue, Oct 18, 2016 at 12:59 AM, Eric Blake <eblake@redhat.com> wrote:
>> On 10/17/2016 01:00 PM, Ashijeet Acharya wrote:
>>
>>> One more relatively easy question though, will we include @port as an
>>> option in runtime_opts while converting NFS to use several
>>> runtime_opts? The reason I ask this because the uri syntax for NFS in
>>> QEMU looks like this:
>>>
>>>         nfs://<host>/<export>/<filename>[?param=value[&param2=value2[&...]]]
>> It's actually nfs://<host>[:port]/...
>>
>> so the URI syntax already supports port.
> But the commit message which added support for NFS had the uri which I
> mentioned above and the code for NFS does not make use of 'port'
> anywhere either, which is why I am a bit confused.

Hi Aschijeet,

don't worry there is no port number when connecting to an NFS server.
The portmapper always listens on port 111. So theoretically we could
specifiy a port in the URL but it is ignored.

BR,
Peter

  reply	other threads:[~2016-10-18 10:42 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-10  5:09 [Qemu-devel] block/nfs: Fine grained runtime options in nfs Ashijeet Acharya
2016-10-14 15:46 ` [Qemu-devel] [Qemu-block] " Stefan Hajnoczi
2016-10-17 18:00   ` Ashijeet Acharya
2016-10-17 19:29     ` Eric Blake
2016-10-17 19:34       ` Ashijeet Acharya
2016-10-18 10:41         ` Peter Lieven [this message]
2016-10-18 12:46           ` Ashijeet Acharya
2016-10-18 13:04             ` Kevin Wolf
2016-10-18 13:14               ` Ashijeet Acharya
2016-10-18 13:33                 ` Kevin Wolf
2016-10-18 13:49                   ` Eric Blake
2016-10-18 16:13                   ` Ashijeet Acharya
2016-10-18 16:18                     ` Ashijeet Acharya

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=61e334e1-bfe5-7907-cad1-a490ec10f8da@kamp.de \
    --to=pl@kamp.de \
    --cc=ashijeetacharya@gmail.com \
    --cc=eblake@redhat.com \
    --cc=jcody@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=mreitz@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@gmail.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).