From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:42320) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1W9KuJ-0003V0-7b for qemu-devel@nongnu.org; Fri, 31 Jan 2014 15:41:48 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1W9KuI-00015m-91 for qemu-devel@nongnu.org; Fri, 31 Jan 2014 15:41:47 -0500 Received: from mail-oa0-x22c.google.com ([2607:f8b0:4003:c02::22c]:39258) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1W9KuI-00015i-1S for qemu-devel@nongnu.org; Fri, 31 Jan 2014 15:41:46 -0500 Received: by mail-oa0-f44.google.com with SMTP id g12so5792326oah.3 for ; Fri, 31 Jan 2014 12:41:45 -0800 (PST) MIME-Version: 1.0 In-Reply-To: <31A541D2-8EEA-419E-BCFE-995641A78866@kamp.de> References: <1391168333-11436-1-git-send-email-pl@kamp.de> <20140131160720.GC15009@stefanha-thinkpad.redhat.com> <31A541D2-8EEA-419E-BCFE-995641A78866@kamp.de> Date: Fri, 31 Jan 2014 21:41:44 +0100 Message-ID: From: Stefan Hajnoczi Content-Type: text/plain; charset=ISO-8859-1 Subject: Re: [Qemu-devel] [PATCHv8 0/5] block: add native support for NFS List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Peter Lieven Cc: Kevin Wolf , =?ISO-8859-1?Q?Beno=EEt_Canet?= , Fam Zheng , ronnie sahlberg , Jeff Cody , qemu-devel , Max Reitz , Orit Wasserman , Federico Simoncelli , Stefan Hajnoczi , Wenchao Xia On Fri, Jan 31, 2014 at 6:32 PM, Peter Lieven wrote: > > Am 31.01.2014 um 17:07 schrieb Stefan Hajnoczi : > >> 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