From: Pavel Fedin <p.fedin@samsung.com>
To: 'QEMU' <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Live migration sequence
Date: Thu, 08 Oct 2015 14:39:35 +0300 [thread overview]
Message-ID: <008b01d101be$0228d720$067a8560$@samsung.com> (raw)
Hello!
I would like to clarify, what is the exact live migration sequence in qemu?
I mean - there are pre_save and post_load callbacks for VMState structures. Is there any determined
order of calling them related to memory contents migration? In other words, is there any guarantee
that pre_save is called before RAM migrates, and post_load is called after RAM migrates?
The answer to this question is important for developing vITS live migration, where i have to dump
internal ITS state into in-memory tables before the migration starts, and then get it back in cache
on destination.
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia
next reply other threads:[~2015-10-08 11:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-08 11:39 Pavel Fedin [this message]
2015-10-09 15:29 ` [Qemu-devel] Live migration sequence Dr. David Alan Gilbert
2015-10-13 10:06 ` Pavel Fedin
2015-10-13 11:05 ` Dr. David Alan Gilbert
2015-10-13 12:02 ` Pavel Fedin
2015-10-13 12:04 ` Peter Maydell
2015-10-13 12:41 ` Pavel Fedin
2015-10-16 7:24 ` Pavel Fedin
2015-10-16 17:11 ` Dr. David Alan Gilbert
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='008b01d101be$0228d720$067a8560$@samsung.com' \
--to=p.fedin@samsung.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).