From: Eric Blake <eblake@redhat.com>
To: Peter Lieven <pl@kamp.de>, ronnie sahlberg <ronniesahlberg@gmail.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
"famz@redhat.com" <famz@redhat.com>,
Stefan Hajnoczi <stefanha@gmail.com>,
qemu-devel <qemu-devel@nongnu.org>,
Stefan Hajnoczi <stefanha@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [PATCHv2] block: add native support for NFS
Date: Tue, 17 Dec 2013 15:44:16 -0700 [thread overview]
Message-ID: <52B0D3C0.7060906@redhat.com> (raw)
In-Reply-To: <C85984CB-3C70-4D92-AC21-99D1FFFE1A06@kamp.de>
[-- Attachment #1: Type: text/plain, Size: 780 bytes --]
On 12/17/2013 03:36 PM, Peter Lieven wrote:
>
>
>> Am 17.12.2013 um 18:13 schrieb ronnie sahlberg <ronniesahlberg@gmail.com>:
>>
>>> On Tue, Dec 17, 2013 at 9:03 AM, Peter Lieven <pl@kamp.de> wrote:
>>> On 17.12.2013 17:47, Stefan Hajnoczi wrote:
>> ...
>>>> Which NFS protocol versions are supported by current libnfs?
>>>
>>> Will check that out. Ronnie?
>>
>> It uses NFS v3 only.
>
> should we use nfs3:// for the urls then?
Or maybe nfs://10.0.0.1/qemu-images/test.qcow2?protocol=3 (where
?protocol= is optional and defaults to 3, but could be expanded to
include 4 in the future, and that way the single nfs:// URI covers both
protocols).
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 621 bytes --]
next prev parent reply other threads:[~2013-12-17 22:44 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-17 9:15 [Qemu-devel] [PATCHv2] block: add native support for NFS Peter Lieven
2013-12-17 16:47 ` Stefan Hajnoczi
2013-12-17 17:03 ` Peter Lieven
2013-12-17 17:13 ` ronnie sahlberg
2013-12-17 22:36 ` Peter Lieven
2013-12-17 22:44 ` Eric Blake [this message]
2013-12-17 22:51 ` ronnie sahlberg
2013-12-17 22:56 ` Peter Lieven
2013-12-17 17:28 ` ronnie sahlberg
2013-12-17 23:00 ` Peter Lieven
2013-12-20 9:48 ` Peter Lieven
2013-12-20 12:19 ` Stefan Hajnoczi
2013-12-20 12:53 ` Peter Lieven
2013-12-20 13:57 ` Stefan Hajnoczi
2013-12-20 14:07 ` Peter Lieven
2013-12-20 14:38 ` Stefan Hajnoczi
2013-12-20 14:43 ` Peter Lieven
2013-12-20 15:03 ` ronnie sahlberg
2013-12-20 15:30 ` Stefan Hajnoczi
2013-12-20 15:49 ` Peter Lieven
2013-12-20 15:54 ` Stefan Hajnoczi
2013-12-20 15:57 ` Peter Lieven
2013-12-20 16:27 ` Stefan Hajnoczi
2014-01-03 10:35 ` Peter Lieven
2013-12-17 16:53 ` ronnie sahlberg
2013-12-17 22:57 ` Peter Lieven
2013-12-17 17:32 ` Daniel P. Berrange
2013-12-17 23:03 ` Peter Lieven
2013-12-18 9:30 ` Daniel P. Berrange
2013-12-18 10:00 ` Orit Wasserman
2013-12-18 10:18 ` Daniel P. Berrange
2013-12-18 10:24 ` Orit Wasserman
2013-12-18 10:38 ` Paolo Bonzini
2013-12-18 17:21 ` Peter Lieven
2013-12-19 14:31 ` Paolo Bonzini
2013-12-18 11:11 ` Peter Lieven
2013-12-18 11:23 ` Orit Wasserman
2013-12-18 14:42 ` ronnie sahlberg
2013-12-18 16:59 ` Peter Lieven
2013-12-18 17:33 ` ronnie sahlberg
2013-12-18 17:42 ` Peter Lieven
2013-12-18 17:50 ` ronnie sahlberg
2013-12-18 17:55 ` Peter Lieven
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=52B0D3C0.7060906@redhat.com \
--to=eblake@redhat.com \
--cc=famz@redhat.com \
--cc=kwolf@redhat.com \
--cc=pbonzini@redhat.com \
--cc=pl@kamp.de \
--cc=qemu-devel@nongnu.org \
--cc=ronniesahlberg@gmail.com \
--cc=stefanha@gmail.com \
--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).