From: Tomer Margalit <tomermargalit@gmail.com>
To: qemu-devel@nongnu.org
Cc: scipioenterprises@yahoo.com, "Zaidenberg,
Nezer" <Nezer.Zaidenberg@edfenergy.com>,
Nezer Zaidenberg <nzaidenberg@mac.com>
Subject: [Qemu-devel] Asynchronously Mirroring a Virtual Machine
Date: Wed, 22 Dec 2010 14:43:21 +0200 [thread overview]
Message-ID: <AANLkTimTAXQQu2gMpX2+=4yeBHWphxybhHWL36SiZi3k@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1837 bytes --]
Hi,
I am a grad. student in Tel-Aviv university, and my theses is focused on
asynchronous mirroring.
I have already built asynchronous mirror software (which is composed of a
driver and a daemon), which works by setting up a virtual block device over
an existing one, and thus mirroring the existing one (asynchronously) to the
network using a window.
What I would like to add to it is the ability to asynchronously mirror a
(QEMU) VM as well, so that if the primary site crashes, the VM can be
restored (to the last stable point) immediately.
Since I want it to be as general as possible, I will not rely on my mirror,
but only on there being a virtual block device that is mirroring me (and
that has consistent writes (that is, if write A succeeded, and afterwards
write B succeeded, then if B is on the secondary site, then A must be there
too)), and that there is some kind of marking mechanism (so that I can mark
the last consistent state).
The reason I want to do this using QEMU is that it has live migration -
which is almost what I need.
Right now my plan is to treat the memory as a file, and put it and all the
vm images on the same mirroring block device.
Then, every minute or so, I will (stop the vm) sync the memory and disks,
and put a mark (where during the minute I will continue to write what I
can).
This sounds to me like doing a continuous "live migration", but never
actually moving the machine, and after finishing the migration on the side
that initiated it, not throwing away the dirty/clean pages (so that the
memory does not have to be moved completely again).
I would appreciate any direction and/or suggestions in this matter.
Also, I wondered where can I find some documentation about the whole
migration process - should I just read the code, or is there any document
about it?
Thanks,
Tomer
[-- Attachment #2: Type: text/html, Size: 2126 bytes --]
next reply other threads:[~2010-12-22 12:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-22 12:43 Tomer Margalit [this message]
2010-12-23 2:34 ` [Qemu-devel] Asynchronously Mirroring a Virtual Machine Stefan Hajnoczi
2010-12-23 17:34 ` Tomer Margalit
2010-12-23 23:44 ` Stefan Hajnoczi
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='AANLkTimTAXQQu2gMpX2+=4yeBHWphxybhHWL36SiZi3k@mail.gmail.com' \
--to=tomermargalit@gmail.com \
--cc=Nezer.Zaidenberg@edfenergy.com \
--cc=nzaidenberg@mac.com \
--cc=qemu-devel@nongnu.org \
--cc=scipioenterprises@yahoo.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).