From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:57843) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VtEIT-0002N3-6e for qemu-devel@nongnu.org; Wed, 18 Dec 2013 05:24:14 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VtEIQ-0000fb-FU for qemu-devel@nongnu.org; Wed, 18 Dec 2013 05:24:09 -0500 Received: from mx1.redhat.com ([209.132.183.28]:10843) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VtEIQ-0000fW-5Q for qemu-devel@nongnu.org; Wed, 18 Dec 2013 05:24:06 -0500 Message-ID: <52B177E1.6060802@redhat.com> Date: Wed, 18 Dec 2013 12:24:33 +0200 From: Orit Wasserman MIME-Version: 1.0 References: <1387271725-17060-1-git-send-email-pl@kamp.de> <20131217173202.GJ14832@redhat.com> <363AFFBF-8F24-4AC3-840F-481A523402B4@kamp.de> <52B17223.2070708@redhat.com> <20131218101818.GE16168@redhat.com> In-Reply-To: <20131218101818.GE16168@redhat.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCHv2] block: add native support for NFS List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Daniel P. Berrange" Cc: "kwolf@redhat.com" , "famz@redhat.com" , Peter Lieven , "qemu-devel@nongnu.org" , "stefanha@redhat.com" , "pbonzini@redhat.com" On 12/18/2013 12:18 PM, Daniel P. Berrange wrote: > On Wed, Dec 18, 2013 at 12:00:03PM +0200, Orit Wasserman wrote: >> On 12/18/2013 01:03 AM, Peter Lieven wrote: >>> >>> >>>> Am 17.12.2013 um 18:32 schrieb "Daniel P. Berrange" : >>>> >>>>> On Tue, Dec 17, 2013 at 10:15:25AM +0100, Peter Lieven wrote: >>>>> This patch adds native support for accessing images on NFS shares without >>>>> the requirement to actually mount the entire NFS share on the host. >>>>> >>>>> NFS Images can simply be specified by an url of the form: >>>>> nfs://// >>>>> >>>>> For example: >>>>> qemu-img create -f qcow2 nfs://10.0.0.1/qemu-images/test.qcow2 >>>> >>>> Does it support other config tunables, eg specifying which >>>> NFS version to use 2/3/4 ? If so will they be available as >>>> URI parameters in the obvious manner ? >>> >>> currently only v3 is supported by libnfs. what other tunables would you like to see? >>> >> >> For live migration we need the sync option (async ignores O_SYNC and O_DIRECT sadly), >> will it be supported? or will it be the default? > > Since this is bypassing the client kernel FS I/O layer question around > support of things like O_SYNC/O_DIRECT are not applicable. > so no live migration support? > Daniel >