From: Stefan Hajnoczi <stefanha@gmail.com>
To: Peter Lieven <pl@kamp.de>
Cc: "Kevin Wolf" <kwolf@redhat.com>,
"Benoît Canet" <benoit.canet@irqsave.net>,
"Fam Zheng" <famz@redhat.com>,
"ronnie sahlberg" <ronniesahlberg@gmail.com>,
"Jeff Cody" <jcody@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>,
"Max Reitz" <mreitz@redhat.com>,
"Orit Wasserman" <owasserm@redhat.com>,
"Federico Simoncelli" <fsimonce@redhat.com>,
"Stefan Hajnoczi" <stefanha@redhat.com>,
"Wenchao Xia" <xiawenc@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] [PATCHv8 0/5] block: add native support for NFS
Date: Fri, 31 Jan 2014 21:41:44 +0100 [thread overview]
Message-ID: <CAJSP0QWk7J0XH5CxSB2ev4VR8YhBLJ-3KD+uPCXHivZGyLtmaA@mail.gmail.com> (raw)
In-Reply-To: <31A541D2-8EEA-419E-BCFE-995641A78866@kamp.de>
On Fri, Jan 31, 2014 at 6:32 PM, Peter Lieven <pl@kamp.de> wrote:
>
> Am 31.01.2014 um 17:07 schrieb Stefan Hajnoczi <stefanha@redhat.com>:
>
>> On Fri, Jan 31, 2014 at 12:38:48PM +0100, Peter Lieven wrote:
>>> This adds v6 of the NFS protocol driver + qemu-iotest adjustments.
>>>
>>> v7->v8:
>>> - bump libnfs requirement to 1.9.2
>>> - renamed NFSRPC->status to NFSRPC->ret [Benoit]
>>> - avoid double invocation of nfs_client_close in nfs_file_create [Benoit]
>>> - fixed error propagation in nfs_file_open [Benoit]
>>
>> I was able to create a qcow2 image and boot a VM successfully over NFS.
>
> This test is obviously new. It is not suitable for protocols other than file as it seems (as a lot
> of other tests). The file not found error looks like it and not a problem with the driver itself.
> I think it needs to be adjusted to work with file only for now.
I think you are right. Max is the author of the tests, he can confirm
that the -o file.file.filename= syntax he used and the blkverify
driver only support the file protocol for now.
Peter: Please send another revision that restricts protocol to 'file'
for these tests. It can be part of the patch that adjusts the other
test cases.
Stefan
next prev parent reply other threads:[~2014-01-31 20:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-31 11:38 [Qemu-devel] [PATCHv8 0/5] block: add native support for NFS Peter Lieven
2014-01-31 11:38 ` [Qemu-devel] [PATCHv8 1/5] " Peter Lieven
2014-01-31 11:38 ` [Qemu-devel] [PATCHv8 2/5] qemu-iotests: change _supported_proto to file for various tests Peter Lieven
2014-01-31 11:38 ` [Qemu-devel] [PATCHv8 3/5] qemu-iotests: enable support for NFS protocol Peter Lieven
2014-01-31 11:38 ` [Qemu-devel] [PATCHv8 4/5] qemu-iotests: enable test 016 and 025 to work with " Peter Lieven
2014-01-31 11:38 ` [Qemu-devel] [PATCHv8 5/5] qemu-iotests: blacklist test 020 for " Peter Lieven
2014-01-31 16:07 ` [Qemu-devel] [PATCHv8 0/5] block: add native support for NFS Stefan Hajnoczi
2014-01-31 17:32 ` Peter Lieven
2014-01-31 20:41 ` Stefan Hajnoczi [this message]
2014-01-31 20:46 ` Max Reitz
2014-02-02 17:41 ` 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=CAJSP0QWk7J0XH5CxSB2ev4VR8YhBLJ-3KD+uPCXHivZGyLtmaA@mail.gmail.com \
--to=stefanha@gmail.com \
--cc=benoit.canet@irqsave.net \
--cc=famz@redhat.com \
--cc=fsimonce@redhat.com \
--cc=jcody@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=owasserm@redhat.com \
--cc=pl@kamp.de \
--cc=qemu-devel@nongnu.org \
--cc=ronniesahlberg@gmail.com \
--cc=stefanha@redhat.com \
--cc=xiawenc@linux.vnet.ibm.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).