From: "Zhang Haoyu" <zhanghy@sangfor.com>
To: "Jidong Xiao" <jidong.xiao@gmail.com>, KVM <kvm@vger.kernel.org>,
qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Where is the VM live migration code?
Date: Tue, 18 Nov 2014 09:29:16 +0800 [thread overview]
Message-ID: <201411180929134821865@sangfor.com> (raw)
In-Reply-To: CAG4AFWYOPTgG1+iAn-tg61xGRh2tJr4HE=YmnwYs=q4w0drrPA@mail.gmail.com
> Hi,
>
> I saw this page:
>
> http://www.linux-kvm.org/page/Migration.
>
> It looks like Migration is a feature provided by KVM? But when I look
> at the Linux kernel source code, i.e., virt/kvm, and arch/x86/kvm, I
> don't see the code for this migration feature.
>
Most of live migration code is in qemu migration.c, savevm.c, arch_init.c,
block-migration.c, and the other devices's save/load handler, .etc,
only log/sync dirty page implemented in kernel.
You can read the most important function migration_thread(),
process_incoming_migration_co().
> So I wonder where is the source code for the live migration? Is it
>purely implemented in user space? Because I see there are the
> following files in the qemu source code:
>
> migration.c migration-exec.c migration-fd.c migration-rdma.c
> migration-tcp.c migration-unix.c
>
> If I wish to understand the implementation of migration in Qemu/KVM,
> are these above files the ones I should read? Thanks.
>
> -Jidong
next prev parent reply other threads:[~2014-11-18 1:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-18 0:10 [Qemu-devel] Where is the VM live migration code? Jidong Xiao
2014-11-18 1:29 ` Zhang Haoyu [this message]
2014-11-18 1:40 ` Jidong Xiao
-- strict thread matches above, loose matches on Subject: below --
2017-08-02 10:54 Aditya Bhardwaj
2017-08-02 10:55 Aditya Bhardwaj
2017-08-02 12:18 ` Daniel P. Berrange
2017-08-02 12:33 ` Eric Blake
2017-08-02 12:49 ` Dr. David Alan Gilbert
2017-08-02 12:53 ` Daniel P. Berrange
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=201411180929134821865@sangfor.com \
--to=zhanghy@sangfor.com \
--cc=jidong.xiao@gmail.com \
--cc=kvm@vger.kernel.org \
--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).