From: Kevin Wolf <kwolf@redhat.com>
To: Anthony Liguori <aliguori@us.ibm.com>
Cc: Lucas Meneghel Rodrigues <lmr@redhat.com>,
Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>,
Juan Quintela <quintela@redhat.com>,
qemu-devel@nongnu.org, Avi Kivity <avi@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 1/7] migrate: add migration blockers
Date: Mon, 14 Nov 2011 10:12:21 +0100 [thread overview]
Message-ID: <4EC0DB75.7070306@redhat.com> (raw)
In-Reply-To: <1321113420-3252-1-git-send-email-aliguori@us.ibm.com>
Am 12.11.2011 16:56, schrieb Anthony Liguori:
> This lets different subsystems register an Error that is thrown whenever
> migration is attempted. This works nicely because it gracefully supports
> things like hotplug.
>
> Right now, if multiple errors are registered, only one of them is reported.
> I expect that for 1.1, we'll extend query-migrate to return all of the reasons
> why migration is disabled at any given point in time.
>
> Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
> Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
> ---
> migration.c | 18 ++++++++++++++++++
> migration.h | 15 +++++++++++++++
> 2 files changed, 33 insertions(+), 0 deletions(-)
There doesn't seem to be a patch 0/n, so it goes here...
The series looks good in general. I commented on two patches, and there
are a few more image formats that must block migration (basically
everything that is writable, I would be surprised if there was one that
didn't cache anything).
Kevin
next prev parent reply other threads:[~2011-11-14 9:09 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-12 15:56 [Qemu-devel] [PATCH 1/7] migrate: add migration blockers Anthony Liguori
2011-11-12 15:56 ` [Qemu-devel] [PATCH 2/7] ivshmem: use migration blockers to prevent live migration in peer mode Anthony Liguori
2011-11-14 13:05 ` Juan Quintela
2011-11-14 13:52 ` Anthony Liguori
2011-11-14 19:52 ` Juan Quintela
2011-11-14 19:55 ` Anthony Liguori
2011-11-12 15:56 ` [Qemu-devel] [PATCH 3/7] qcow2: add a migration blocker Anthony Liguori
2011-11-12 15:56 ` [Qemu-devel] [PATCH 4/7] qed: add " Anthony Liguori
2011-11-12 15:56 ` [Qemu-devel] [PATCH 5/7] block: allow migration to work with image files (v2) Anthony Liguori
2011-11-14 13:11 ` Juan Quintela
2011-11-14 14:10 ` Anthony Liguori
2011-11-14 19:46 ` Juan Quintela
2011-11-14 19:49 ` Anthony Liguori
2011-11-14 20:11 ` Kevin Wolf
2011-11-14 20:12 ` Anthony Liguori
2011-11-14 20:28 ` Juan Quintela
2011-11-14 20:36 ` Kevin Wolf
2011-11-14 20:49 ` Anthony Liguori
2011-11-14 20:15 ` Juan Quintela
2011-11-12 15:56 ` [Qemu-devel] [PATCH 6/7] qcow2: implement bdrv_invalidate_cache Anthony Liguori
2011-11-12 15:57 ` [Qemu-devel] [PATCH 7/7] qcow2: relax migration blocker Anthony Liguori
2011-11-14 9:04 ` Kevin Wolf
2011-11-14 9:08 ` [Qemu-devel] [PATCH 1/7] migrate: add migration blockers Kevin Wolf
2011-11-14 18:25 ` Anthony Liguori
2011-11-14 9:12 ` Kevin Wolf [this message]
2011-11-14 13:00 ` Juan Quintela
-- strict thread matches above, loose matches on Subject: below --
2011-11-12 15:57 Anthony Liguori
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=4EC0DB75.7070306@redhat.com \
--to=kwolf@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=avi@redhat.com \
--cc=lmr@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=stefanha@linux.vnet.ibm.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).