From: Stefan Hajnoczi <stefanha@gmail.com>
To: Jeff Cody <jcody@redhat.com>
Cc: kwolf@redhat.com, qemu-devel@nongnu.org, stefanha@redhat.com
Subject: Re: [Qemu-devel] [PATCH] block: vhdx - add migration blocker
Date: Wed, 2 Oct 2013 15:25:53 +0200 [thread overview]
Message-ID: <20131002132553.GA13357@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <29665682371164fd1e375842f5824b1de5648dde.1380643069.git.jcody@redhat.com>
On Tue, Oct 01, 2013 at 11:59:20AM -0400, Jeff Cody wrote:
> This blocks migration for VHDX image files, until the
> functionality can be supported.
>
> Signed-off-by: Jeff Cody <jcody@redhat.com>
> ---
> block/vhdx.c | 10 ++++++++++
> 1 file changed, 10 insertions(+)
Strictly speaking live migration is safe since the format is read-only.
The source machine will never write to the image, we don't need to worry
about cache consistency.
But given that your log reply and write patches are quite far along,
let's just merge this now. We'll need it soon.
Thanks, applied to my block tree:
https://github.com/stefanha/qemu/commits/block
Stefan
prev parent reply other threads:[~2013-10-02 13:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-01 15:59 [Qemu-devel] [PATCH] block: vhdx - add migration blocker Jeff Cody
2013-10-02 13:25 ` Stefan Hajnoczi [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=20131002132553.GA13357@stefanha-thinkpad.redhat.com \
--to=stefanha@gmail.com \
--cc=jcody@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@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).