From: Stefan Hajnoczi <stefanha@gmail.com>
To: Thomas Knauth <thomas.knauth@googlemail.com>
Cc: Bohdan Trach <bohdan.trach@mailbox.tu-dresden.de>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] feature proposal: checkpoint-assisted migration
Date: Wed, 15 Apr 2015 10:54:05 +0100 [thread overview]
Message-ID: <20150415095405.GE16656@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <CABhLV02pWDDjd=a8vJXmVc_1vv2wu9YJ7koVP51KeD3mSjmiMg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1036 bytes --]
On Tue, Apr 14, 2015 at 01:20:33PM +0200, Thomas Knauth wrote:
> In the course of our research we implemented a prototype of this
> feature within kvm/qemu. We would like to contribute it to mainline,
> but it needs cleanup and proper testing. As is the nature with
> research prototypes, the code is ugly and not well integrated with the
> existing kvm/qemu codebase. To avoid confusion and irritation, I want
> to mention that I have little experience in contributing to large
> open-source projects. So if I violate some unwritten protocol or best
> practises, please be patient.
Guidelines for contributing patches are here:
http://qemu-project.org/Contribute/SubmitAPatch
Regarding the idea, it sounds like it could be beneficial for some
migration use cases. I've thought about an rsync approach for disk
images, and that is similar to your idea for RAM. There are image file
formats that keep generation counts for regions of the disk image,
making it quick to find out which regions have changed between two
images.
Stefan
[-- Attachment #2: Type: application/pgp-signature, Size: 473 bytes --]
prev parent reply other threads:[~2015-04-15 9:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-14 11:20 [Qemu-devel] feature proposal: checkpoint-assisted migration Thomas Knauth
2015-04-14 18:43 ` Dr. David Alan Gilbert
2015-04-15 9:54 ` Stefan Hajnoczi [this message]
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=20150415095405.GE16656@stefanha-thinkpad.redhat.com \
--to=stefanha@gmail.com \
--cc=bohdan.trach@mailbox.tu-dresden.de \
--cc=qemu-devel@nongnu.org \
--cc=thomas.knauth@googlemail.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).