From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: Pavel Butsykin <pbutsykin@virtuozzo.com>
Cc: qemu-devel@nongnu.org, quintela@redhat.com
Subject: Re: [Qemu-devel] [PATCH v2 0/3] migration capability to discard the migrated ram pages
Date: Tue, 7 Mar 2017 15:17:06 +0000 [thread overview]
Message-ID: <20170307151705.GH2869@work-vm> (raw)
In-Reply-To: <58BECEC2.7030705@virtuozzo.com>
* Pavel Butsykin (pbutsykin@virtuozzo.com) wrote:
> On 07.03.2017 17:46, Dr. David Alan Gilbert wrote:
> > * Pavel Butsykin (pbutsykin@virtuozzo.com) wrote:
> > > On 07.03.2017 16:56, Dr. David Alan Gilbert wrote:
> > > > * Pavel Butsykin (pbutsykin@virtuozzo.com) wrote:
> > > > > On 14.02.2017 17:02, Dr. David Alan Gilbert wrote:
> > > > > > Hi Pavel,
> > > > > > I was curious, having merged this, how you're using postcopy; do you switch
> > > > > > into postcopy mode immediately or wait until the first sync or what?
> > > > > > Do you find yourself in postcopy mode long enough that it's worth
> > > > > > doing the release? If so on what size VMs are you working with?
> > > > > >
> > > > > > Dave
> > > > >
> > > > > Hi Dave,
> > > > > I'm sorry it took so long, I was on vacation. And thanks for the quick
> > > > > review and merge!
> > > > >
> > > > > We want to use this function to update Qemu without rebooting VMs. It
> > > > > looks like a local migration on the same host. Now, switching into
> > > > > postcopy mode is done immediately, the size of VMs can be very
> > > > > different.
> > > >
> > > > Thanks! Do you have libvirt magic to do that update?
> > >
> > > Yes, there are patches that add a flag "--local" for migration. The
> > > flag adds start incoming VM and other magic about replacement source on
> > > destination.
> >
> > Nice; are those posted to libvirt's list somewhere?
>
> Not yet, but we're going to do it.
Great, I look forward to that.
Dave
>
> > Dave
> >
> > > > Dave
> > > >
> > > > > > * Pavel Butsykin (pbutsykin@virtuozzo.com) wrote:
> > > > > > > This feature frees the migrated memory on the source during postcopy-ram
> > > > > > > migration. In the second step of postcopy-ram migration when the source vm
> > > > > > > is put on pause we can free unnecessary memory. It will allow, in particular,
> > > > > > > to start relaxing the memory stress on the source host in a load-balancing
> > > > > > > scenario.
> > > > > > >
> > > > > > > Changes from v1:
> > > > > > > - changed name of the interfaces (discard to release)
> > > > > > > - fix make check error
> > > > > > > - add more comments to qemu_iovec_release_ram()
> > > > > > > - rebase on "Postcopy: Hugepage support" (David's patch series)
> > > > > > > - removed ram_discard_page for xbzrle
> > > > > > > - fix erroneous release memory in complete precopy (tie release-ram to postcopy)
> > > > > > >
> > > > > > > Pavel Butsykin (3):
> > > > > > > migration: add MigrationState arg for ram_save_/compressed_/page()
> > > > > > > add 'release-ram' migrate capability
> > > > > > > migration: discard non-dirty ram pages after the start of postcopy
> > > > > > >
> > > > > > > include/migration/migration.h | 2 ++
> > > > > > > include/migration/qemu-file.h | 3 ++-
> > > > > > > migration/migration.c | 13 ++++++++++
> > > > > > > migration/qemu-file.c | 59 ++++++++++++++++++++++++++++++++++++++-----
> > > > > > > migration/ram.c | 56 ++++++++++++++++++++++++++++++++++------
> > > > > > > qapi-schema.json | 5 +++-
> > > > > > > 6 files changed, 121 insertions(+), 17 deletions(-)
> > > > > > >
> > > > > > > --
> > > > > > > 2.11.0
> > > > > > >
> > > > > > >
> > > > > > --
> > > > > > Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
> > > > > >
> > > > --
> > > > Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
> > > >
> > --
> > Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
> >
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
prev parent reply other threads:[~2017-03-07 15:17 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-03 15:23 [Qemu-devel] [PATCH v2 0/3] migration capability to discard the migrated ram pages Pavel Butsykin
2017-02-03 15:23 ` [Qemu-devel] [PATCH v2 1/3] migration: add MigrationState arg for ram_save_/compressed_/page() Pavel Butsykin
2017-02-10 11:54 ` Dr. David Alan Gilbert
2017-02-14 23:22 ` Philippe Mathieu-Daudé
2017-02-03 15:23 ` [Qemu-devel] [PATCH v2 2/3] add 'release-ram' migrate capability Pavel Butsykin
2017-02-10 12:22 ` Dr. David Alan Gilbert
2017-02-10 12:25 ` Dr. David Alan Gilbert
2017-02-10 14:36 ` [Qemu-devel] [PATCH] migration: madvise error_report fixup! Pavel Butsykin
2017-02-10 14:47 ` Dr. David Alan Gilbert
2017-02-03 15:23 ` [Qemu-devel] [PATCH v2 3/3] migration: discard non-dirty ram pages after the start of postcopy Pavel Butsykin
2017-02-10 12:29 ` Dr. David Alan Gilbert
2017-02-03 17:07 ` [Qemu-devel] [PATCH v2 0/3] migration capability to discard the migrated ram pages no-reply
2017-02-10 15:12 ` Dr. David Alan Gilbert
2017-02-14 14:02 ` Dr. David Alan Gilbert
2017-03-03 8:39 ` Pavel Butsykin
2017-03-07 13:56 ` Dr. David Alan Gilbert
2017-03-07 14:42 ` Pavel Butsykin
2017-03-07 14:46 ` Dr. David Alan Gilbert
2017-03-07 15:16 ` Pavel Butsykin
2017-03-07 15:17 ` Dr. David Alan Gilbert [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=20170307151705.GH2869@work-vm \
--to=dgilbert@redhat.com \
--cc=pbutsykin@virtuozzo.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.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).