From: "Daniel P. Berrange" <berrange@redhat.com>
To: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
Cc: Aditya Bhardwaj <adityaform@gmail.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Where is the VM live migration code?
Date: Wed, 2 Aug 2017 13:53:41 +0100 [thread overview]
Message-ID: <20170802125341.GQ4098@redhat.com> (raw)
In-Reply-To: <20170802124943.GA2380@work-vm>
On Wed, Aug 02, 2017 at 01:49:44PM +0100, Dr. David Alan Gilbert wrote:
> * Aditya Bhardwaj (adityaform@gmail.com) wrote:
> > My lab setup is: 3 HP Servers each of 4 GB RAM. Server 1 and Server 2:
> > installed with Virtualization using KVM on Redhat 6.5 System. On top of
> > this I am using libvirtd for managing virtual machines. NFS server is
> > installed on Server 3 for shared disk image. VM migration is working
> > correctly. Now i need to do some changes in "migration.c" but did not find
> > any source code of KVM-QEMU migration.
> >
> > Where I can find the migration source code for KVM-QEMU. All are requested
> > to help me for this issue.
>
> Migration is quite big - so take a step back first and understand how
> a migration works before diving into the code too far.
> First I'd suggest going for something newer than 6.5 - it has a very
> very old QEMU on it; If you can upgrade to a 7.x it'll make your life a
> lot easier for building and working with current code.
>
> The current QEMU has a whole migration/ subdirectory with quite a bit of
> code, and there's also some kernel code that helps, and code in
> individual devices.
>
> Then there's also the code in libvirt that drives it.
>
> A lot of code - so the trick is to figure out what you want to change
> and then find the right place.
Might also be worth while to explain what problem with live migration
you are looking to solve, as it may well be that it has already been
examined / worked on by someone else, or people might have design
suggestions to avoid you wasting time down dead-ends.
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2017-08-02 12:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-02 10:55 [Qemu-devel] Where is the VM live migration code? 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 [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-08-02 10:54 Aditya Bhardwaj
2014-11-18 0:10 Jidong Xiao
2014-11-18 1:29 ` Zhang Haoyu
2014-11-18 1:40 ` Jidong Xiao
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=20170802125341.GQ4098@redhat.com \
--to=berrange@redhat.com \
--cc=adityaform@gmail.com \
--cc=dgilbert@redhat.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).