From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:40226) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VtFDQ-00058O-1T for qemu-devel@nongnu.org; Wed, 18 Dec 2013 06:23:03 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VtFDM-0000X9-7a for qemu-devel@nongnu.org; Wed, 18 Dec 2013 06:22:59 -0500 Received: from mx1.redhat.com ([209.132.183.28]:58603) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VtFDL-0000X4-U0 for qemu-devel@nongnu.org; Wed, 18 Dec 2013 06:22:56 -0500 Message-ID: <52B185A7.1000603@redhat.com> Date: Wed, 18 Dec 2013 13:23:19 +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> <15C7BD2F-CFA0-47C0-9DF9-EFFBB71A987A@kamp.de> In-Reply-To: <15C7BD2F-CFA0-47C0-9DF9-EFFBB71A987A@kamp.de> Content-Type: text/plain; charset=ISO-8859-1; 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: Peter Lieven Cc: "kwolf@redhat.com" , "famz@redhat.com" , "qemu-devel@nongnu.org" , "stefanha@redhat.com" , "pbonzini@redhat.com" On 12/18/2013 01:11 PM, Peter Lieven wrote: > > >> Am 18.12.2013 um 11:00 schrieb Orit Wasserman : >> >>> 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? > > the async you see in the libnfs calls refer to the async API. bdrv_flush will not return before the nfs server completes the request. > That great! Thanks, Orit > Peter > >> >> Orit >> >>>> >>>> Daniel >>>> -- >>>> |: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :| >>>> |: http://libvirt.org -o- http://virt-manager.org :| >>>> |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| >>>> |: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :| >>