From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:55228) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bwDfy-0005kq-OQ for qemu-devel@nongnu.org; Mon, 17 Oct 2016 15:34:23 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bwDfx-0005eT-VL for qemu-devel@nongnu.org; Mon, 17 Oct 2016 15:34:22 -0400 MIME-Version: 1.0 In-Reply-To: <98a190a0-007b-3a83-8b31-f24de6a95335@redhat.com> References: <20161014154639.GF3482@stefanha-x1.localdomain> <98a190a0-007b-3a83-8b31-f24de6a95335@redhat.com> From: Ashijeet Acharya Date: Tue, 18 Oct 2016 01:04:18 +0530 Message-ID: Content-Type: text/plain; charset=UTF-8 Subject: Re: [Qemu-devel] [Qemu-block] block/nfs: Fine grained runtime options in nfs List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Eric Blake Cc: Stefan Hajnoczi , Kevin Wolf , qemu-block@nongnu.org, jcody@redhat.com, pl@kamp.de, QEMU Developers , Max Reitz On Tue, Oct 18, 2016 at 12:59 AM, Eric Blake 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:////[?param=value[¶m2=value2[&...]]] > > It's actually nfs://[: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. Ashijeet > > -- > Eric Blake eblake redhat com +1-919-301-3266 > Libvirt virtualization library http://libvirt.org >