From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:38887) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QqPrA-0006eJ-2l for qemu-devel@nongnu.org; Mon, 08 Aug 2011 09:27:01 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QqPr9-0005a5-3Q for qemu-devel@nongnu.org; Mon, 08 Aug 2011 09:27:00 -0400 Received: from mx1.redhat.com ([209.132.183.28]:50217) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QqPr8-0005Zt-IT for qemu-devel@nongnu.org; Mon, 08 Aug 2011 09:26:58 -0400 Date: Mon, 8 Aug 2011 10:26:54 -0300 From: Luiz Capitulino Message-ID: <20110808102654.56632542@doriath> In-Reply-To: <4E3ED941.5080601@redhat.com> References: <20110727152457.GK18528@redhat.com> <4E3ED941.5080601@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] RFC: moving fsfreeze support from the userland guest agent to the guest kernel List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Ronen Hod Cc: Andrea Arcangeli , Jes Sorensen , qemu-devel@nongnu.org, Michael Roth On Sun, 07 Aug 2011 21:28:17 +0300 Ronen Hod wrote: > Well, we want to support Microsoft's VSS, and that requires a guest > agent that communicates with all the "writers" (applications), waiting > for them to flush their app data in order to generate a consistent > app-level snapshot. The VSS platform does most of the work. > Still, at the bottom line, the agent's role is only to find the right > moment in time. This moment can be relayed back to libvirt, and from > there do it according to your suggestion, so that the guest agent does > not do the freeze, and it is actually not a mandatory component. I think this discussion has reached the point where patches will speak louder than words.