From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.186.70.92] (port=53531 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PkHDU-0003k9-42 for qemu-devel@nongnu.org; Tue, 01 Feb 2011 09:28:25 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1PkHDT-0006IJ-6v for qemu-devel@nongnu.org; Tue, 01 Feb 2011 09:28:24 -0500 Received: from mx1.redhat.com ([209.132.183.28]:1025) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1PkHDS-0006IC-WA for qemu-devel@nongnu.org; Tue, 01 Feb 2011 09:28:23 -0500 Message-ID: <4D481883.3060606@redhat.com> Date: Tue, 01 Feb 2011 15:28:19 +0100 From: Jes Sorensen MIME-Version: 1.0 Subject: Re: [Qemu-devel] [PATCH 0/2] virtagent - fsfreeze support References: <1296557928-30019-1-git-send-email-Jes.Sorensen@redhat.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Stefan Hajnoczi Cc: agl@us.ibm.com, qemu-devel@nongnu.org, mdroth@linux.vnet.ibm.com On 02/01/11 15:16, Stefan Hajnoczi wrote: > On Tue, Feb 1, 2011 at 10:58 AM, wrote: >> From: Jes Sorensen >> This is a first attempt to add fsfreeze support to virtagent. The idea >> is for the guest agent to walk the list of locally mounted file >> systems in the guest, and issuing an ioctl to freeze them. The host >> can then do a live snapshot of the guest, obtaining stable file >> systems. After the snapshot, the host then calls the thaw function in >> virtagent, which goes through the list of previously frozen file >> systems and unfreezes them. > > Any plans for a call-out to pre/post freeze and thaw scripts so that > applications can flush cached data to disk and brace themselves for > freeze? Michael and I were discussing this earlier, we need to add it somehow. It could be done as call-outs from the freeze call, or from separate agent calls. Cheers, Jes