From: Ronen Hod <rhod@redhat.com>
To: Andrea Arcangeli <aarcange@redhat.com>
Cc: Jes Sorensen <Jes.Sorensen@redhat.com>,
Luiz Capitulino <lcapitulino@redhat.com>,
qemu-devel@nongnu.org, Michael Roth <mdroth@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] RFC: moving fsfreeze support from the userland guest agent to the guest kernel
Date: Sun, 07 Aug 2011 21:28:17 +0300 [thread overview]
Message-ID: <4E3ED941.5080601@redhat.com> (raw)
In-Reply-To: <20110727152457.GK18528@redhat.com>
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.
Ronen.
next prev parent reply other threads:[~2011-08-07 18:28 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-27 15:24 [Qemu-devel] RFC: moving fsfreeze support from the userland guest agent to the guest kernel Andrea Arcangeli
2011-07-27 16:07 ` Michael Roth
2011-07-27 16:40 ` Andrea Arcangeli
2011-07-28 8:54 ` Jes Sorensen
2011-07-28 15:26 ` Michael Roth
2011-07-27 16:34 ` Anthony Liguori
2011-07-27 16:50 ` Andrea Arcangeli
2011-07-27 18:36 ` Christoph Hellwig
2011-07-27 19:47 ` Andrea Arcangeli
2011-07-28 8:56 ` Jes Sorensen
2011-07-28 2:53 ` Fernando Luis Vázquez Cao
2011-07-28 8:03 ` Andrea Arcangeli
2011-07-28 15:11 ` Michael Roth
2011-07-29 0:29 ` Fernando Luis Vazquez Cao
2011-08-07 18:28 ` Ronen Hod [this message]
2011-08-08 13:26 ` Luiz Capitulino
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4E3ED941.5080601@redhat.com \
--to=rhod@redhat.com \
--cc=Jes.Sorensen@redhat.com \
--cc=aarcange@redhat.com \
--cc=lcapitulino@redhat.com \
--cc=mdroth@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).