From: Anthony Liguori <anthony@codemonkey.ws>
To: Ayal Baron <abaron@redhat.com>
Cc: chrisw@redhat.com, kvm@vger.kernel.org,
Juan Quintela <quintela@redhat.com>,
dlaor@redhat.com, qemu-devel@nongnu.org,
Chris Wright <chrisw@sous-sol.org>,
"Venkateswararao Jujjuri (JV)" <jvrao@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] Re: KVM call agenda for Oct 19
Date: Tue, 19 Oct 2010 16:19:17 -0500 [thread overview]
Message-ID: <4CBE0B55.6020208@codemonkey.ws> (raw)
In-Reply-To: <1642827860.79861287521845369.JavaMail.root@zmail07.collab.prod.int.phx2.redhat.com>
On 10/19/2010 03:57 PM, Ayal Baron wrote:
>> Yeah, concurrent is a little trickier. Simple solution is for a
>> management tool to just do a stop + multiple snapshots + cont. It's
>> equivalent to what we'd do if we don't do it aio which is probably how
>>
>> we'd do the first implementation.
>>
>> But in the long term, I think the most elegant solution would be to
>> expose the freeze api via QMP and let a management tool freeze
>> multiple
>> devices, then start taking snapshots, then unfreeze them when all
>> snapshots are complete.
>>
>> Regards,
>>
>> Anthony Liguori
>>
> qemu should call the freeze as part of the process (for all of the relevant devices) then take the snapshots then thaw.
>
Yeah, I'm not opposed to us providing simpler interfaces in addition to
or in lieu of lower level interfaces.
Regards,
Anthony Liguori
next prev parent reply other threads:[~2010-10-19 21:19 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <512838278.79671287521779658.JavaMail.root@zmail07.collab.prod.int.phx2.redhat.com>
2010-10-19 20:57 ` [Qemu-devel] Re: KVM call agenda for Oct 19 Ayal Baron
2010-10-19 21:19 ` Anthony Liguori [this message]
[not found] <314565543.45891287507100965.JavaMail.root@zmail07.collab.prod.int.phx2.redhat.com>
2010-10-19 16:54 ` Ayal Baron
2010-10-19 17:09 ` Anthony Liguori
2010-10-20 9:18 ` Kevin Wolf
2010-10-20 9:41 ` Ayal Baron
2010-10-20 13:05 ` Anthony Liguori
2010-10-18 15:43 [Qemu-devel] " Juan Quintela
2010-10-19 2:11 ` [Qemu-devel] " Chris Wright
2010-10-19 12:48 ` Dor Laor
2010-10-19 12:55 ` Avi Kivity
2010-10-19 12:58 ` Dor Laor
2010-10-19 13:03 ` Avi Kivity
2010-10-19 13:18 ` Anthony Liguori
2010-10-19 13:22 ` Anthony Liguori
2010-10-19 13:27 ` Avi Kivity
2010-10-19 13:33 ` Anthony Liguori
2010-10-19 13:38 ` Stefan Hajnoczi
2010-10-19 13:55 ` Avi Kivity
2010-10-19 13:28 ` Anthony Liguori
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=4CBE0B55.6020208@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=abaron@redhat.com \
--cc=chrisw@redhat.com \
--cc=chrisw@sous-sol.org \
--cc=dlaor@redhat.com \
--cc=jvrao@linux.vnet.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
/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).