From: Anthony Liguori <aliguori@us.ibm.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
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: [Qemu-devel] [PATCH 0/5] migration: support migration with image files
Date: Mon, 14 Nov 2011 15:29:17 -0600 [thread overview]
Message-ID: <4EC1882D.9080101@us.ibm.com> (raw)
In-Reply-To: <1321304987-23041-1-git-send-email-aliguori@us.ibm.com>
This series allows live migration to work with image formats. This series has
two parts. The first part adds a new error infrastructure to migration which
allows for different subsystems (other than qdev) to block migration when
specific features are in use.
The second part adds block interfaces to flush metadata with image formats.
The migration error infrastructure is a no brainer for 1.0. It significantly
improves the user experience and prevents a user from doing things that will
cause a VM to crash during migration.
I'm less comfortable with the block interface for flushing metadata for 1.0.
The code is completely isolated to the image formats and live migration. It
should have no impact on normal use of an image format or live migration with
raw images. That makes the risk for this very, very low.
Moreover, I'm sympathetic to the argument that this is a required feature for a
1.0 release. Image formats are a fairly normal way to use QEMU and not
supporting live migration in this scenario means that live migration won't work
for a large portion of QEMU's users.
next prev parent reply other threads:[~2011-11-14 21:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-14 21:09 [Qemu-devel] [PATCH 1/5] migrate: add migration blockers Anthony Liguori
2011-11-14 21:09 ` [Qemu-devel] [PATCH 2/5] ivshmem: use migration blockers to prevent live migration in peer mode (v2) Anthony Liguori
2011-11-14 21:31 ` Michael Roth
2011-11-14 21:38 ` Anthony Liguori
2011-11-14 21:09 ` [Qemu-devel] [PATCH 3/5] block: allow migration to work with image files (v3) Anthony Liguori
2011-11-14 21:09 ` [Qemu-devel] [PATCH 4/5] qcow2: implement bdrv_invalidate_cache (v2) Anthony Liguori
2011-11-14 21:09 ` [Qemu-devel] [PATCH 5/5] qed: add migration blocker (v2) Anthony Liguori
2011-11-14 21:29 ` Anthony Liguori [this message]
2011-11-22 0:21 ` [Qemu-devel] [PATCH 1/5] migrate: add migration blockers 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=4EC1882D.9080101@us.ibm.com \
--to=aliguori@us.ibm.com \
--cc=avi@redhat.com \
--cc=kwolf@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).