From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:38479) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TC2wS-0000Sq-47 for qemu-devel@nongnu.org; Thu, 13 Sep 2012 02:30:25 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1TC2wN-00076e-Tp for qemu-devel@nongnu.org; Thu, 13 Sep 2012 02:30:24 -0400 Received: from mail-we0-f173.google.com ([74.125.82.173]:40833) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TC2wN-00075y-N6 for qemu-devel@nongnu.org; Thu, 13 Sep 2012 02:30:19 -0400 Received: by weyz53 with SMTP id z53so1412307wey.4 for ; Wed, 12 Sep 2012 23:30:19 -0700 (PDT) Sender: Paolo Bonzini Message-ID: <50517D77.80903@redhat.com> Date: Thu, 13 Sep 2012 08:30:15 +0200 From: Paolo Bonzini MIME-Version: 1.0 References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] 'qemu-nbd' explicite flush to disk List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Mark Trumpold Cc: "qemu-devel@nongnu.org" Il 12/09/2012 23:28, Mark Trumpold ha scritto: > So, I've been experimenting with 'qemu-nbd --cache=writeback ..' > This nicely eliminates the 'checkpoint' issue; however, I have as > yet been unable to explicitely flush things to disk -- which I would like to > do just before a 'nilfs' snapshot. The Linux kernel driver for NBD does not support flushes. Patches were sent to the maintainer, but he never applied them. You can get them at http://thread.gmane.org/gmane.linux.drivers.nbd.general/1108 and try them. > Subsequently I've been trying to call 'bdrv_co_flush(bs)' directly, but I can't figure out how to dereference 'bs' for the call. > > I'm probably out in the weeds on this one. > Any guidance would be greatly appreciated. > > I am running: > qemu-1.2.0 > linux kernel 3.3.1 > > Thank you, > Mark Trumpold > > > Confidentiality Notice: The information contained in this electronic > e-mail and any accompanying attachment(s) is intended only for the use > of the intended recipient and is confidential and/or privileged. I doubt so, since this is a public mailing list. Paolo