From: Avi Kivity <avi@redhat.com>
To: Marcelo Tosatti <mtosatti@redhat.com>
Cc: kwolf@redhat.com, Jes.Sorensen@redhat.com, dlaor@redhat.com,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [patch 6/7] QEMU live block copy
Date: Tue, 31 May 2011 19:14:57 +0300 [thread overview]
Message-ID: <4DE51401.6040602@redhat.com> (raw)
In-Reply-To: <20110531160636.GA9656@amt.cnet>
On 05/31/2011 07:06 PM, Marcelo Tosatti wrote:
> On Sun, May 29, 2011 at 11:54:25AM +0300, Avi Kivity wrote:
> > On 05/24/2011 12:31 AM, Marcelo Tosatti wrote:
> > >Support live image copy + switch. That is, copy an image backing
> > >a guest hard disk to a destination image (destination image must
> > >be created separately), and switch to this copy.
> > >
> > >Command syntax:
> > >
> > >block_copy device filename [-i] -- live block copy device to image
> > > -i for incremental copy (base image shared between src and destination)
> > >
> > >Please refer to qmp-commands diff for more details.
> >
> > IMO it would have been nicer to use the mirror driver for all
> > copying; there would be no STAGE_DIRTY; simply a background process
> > that copies over all blocks, taking care not to conflict with
> > ongoing writes.
>
> Don't see the advantage of doing that.
No dirty logging
No conflict with migration
Simpler conceptually (IMO)
> Disadvantages:
>
> - Guest write performance is affected during copying (guest writes
> compete with stream of writes from copy).
Competes anyway with your background task?
> - Complexity to handle copy write conflict (there is no need to handle
> that with current solution).
If new write from source A overlaps an in-flight write from source B,
hold it in a list off the B request, and re-issue it on B completion.
> - Unability to have the mirror functionality in a separate driver.
Why?
> > It would also remove the conflict with migration.
>
> There is no fundamental problem with migration, its simply unsupported
> now.
Why?
> > But that's an implementation detail and can be changed later.
>
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2011-05-31 18:31 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-23 21:31 [Qemu-devel] [patch 0/7] live block copy (v3) Marcelo Tosatti
2011-05-23 21:31 ` [Qemu-devel] [patch 1/7] add migration_active function Marcelo Tosatti
2011-05-27 17:43 ` Kevin Wolf
2011-05-30 0:53 ` Jes Sorensen
2011-05-23 21:31 ` [Qemu-devel] [patch 2/7] Add blkmirror block driver Marcelo Tosatti
2011-05-24 19:03 ` Blue Swirl
2011-05-27 17:45 ` Kevin Wolf
2011-05-29 8:45 ` Avi Kivity
2011-05-23 21:31 ` [Qemu-devel] [patch 3/7] Add error messages for live block copy Marcelo Tosatti
2011-05-23 21:31 ` [Qemu-devel] [patch 4/7] Add blkdebug points " Marcelo Tosatti
2011-05-23 21:31 ` [Qemu-devel] [patch 5/7] Add vmstop code " Marcelo Tosatti
2011-05-23 21:31 ` [Qemu-devel] [patch 6/7] QEMU " Marcelo Tosatti
2011-05-24 19:15 ` Blue Swirl
2011-06-03 15:59 ` Marcelo Tosatti
2011-05-29 8:54 ` Avi Kivity
2011-05-31 16:06 ` Marcelo Tosatti
2011-05-31 16:14 ` Avi Kivity [this message]
2011-05-31 16:38 ` Marcelo Tosatti
2011-05-31 16:53 ` Avi Kivity
2011-06-03 16:20 ` Marcelo Tosatti
2011-05-23 21:31 ` [Qemu-devel] [patch 7/7] do not allow migration if block copy in progress Marcelo Tosatti
2011-05-29 8:54 ` Avi Kivity
-- strict thread matches above, loose matches on Subject: below --
2011-06-06 16:55 [Qemu-devel] [patch 0/7] live block copy (v4) Marcelo Tosatti
2011-06-06 16:55 ` [Qemu-devel] [patch 6/7] QEMU live block copy Marcelo Tosatti
2011-06-07 12:15 ` Stefan Hajnoczi
2011-06-08 15:10 ` Jagane Sundar
2011-06-08 16:18 ` Stefan Hajnoczi
2011-06-09 15:42 ` Jagane Sundar
2011-06-15 16:59 ` Marcelo Tosatti
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=4DE51401.6040602@redhat.com \
--to=avi@redhat.com \
--cc=Jes.Sorensen@redhat.com \
--cc=dlaor@redhat.com \
--cc=kwolf@redhat.com \
--cc=mtosatti@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).