All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Zhang Haoyu" <zhanghy@sangfor.com.cn>
To: Fam Zheng <famz@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
	Marcelo Tosatti <mtosatti@redhat.com>,
	qemu-devel <qemu-devel@nongnu.org>,
	vsementsov <vsementsov@parallels.com>,
	Stefan Hajnoczi <stefanha@redhat.com>,
	Paolo Bonzini <pbonzini@redhat.com>, jsnow <jsnow@redhat.com>
Subject: Re: [Qemu-devel] [RFC] introduce bitmap to bdrv_commit totrackdirtysector
Date: Tue, 10 Mar 2015 11:12:11 +0800	[thread overview]
Message-ID: <201503101112105657084@sangfor.com.cn> (raw)
In-Reply-To: 201503101012008258045@sangfor.com.cn


On 2015-03-10 10:58:44, Fam Zheng wrote:
> > Is it worthy to implement it?
> 
> Maybe, I think once we start to assign node-name to each BDS in the tree, this
> will be natural to implement.
> 
Once implemented, to be honest, I really don't see much advantages of 
incremental backup over aforementioned mechanism(external snapshot + active block commit),
especially, regarding the case of source vm non-normal shutdown, full copy is needed,
and corresponding check mechanism is needed too.
I think so much exceptional scenarios are needed to be considered for incremental backup mechanism.
Maybe I missed something.

Thanks,
Zhang Haoyu
> > And does qemu support commit any external snapshot to its backing file?
> 
> Yes.

      parent reply	other threads:[~2015-03-10  3:12 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-03  6:52 [Qemu-devel] [RFC] introduce bitmap to bdrv_commit to track dirty sector Zhang Haoyu
2015-03-03  9:59 ` Paolo Bonzini
2015-03-09  7:03   ` Zhang Haoyu
2015-03-09  7:38     ` Paolo Bonzini
2015-03-09  8:14     ` Zhang Haoyu
2015-03-10  0:28       ` Fam Zheng
2015-03-10  1:30       ` [Qemu-devel] [RFC] introduce bitmap to bdrv_commit to trackdirty sector Zhang Haoyu
2015-03-10  1:54         ` Fam Zheng
2015-03-10  2:12         ` [Qemu-devel] [RFC] introduce bitmap to bdrv_commit to trackdirtysector Zhang Haoyu
2015-03-10  2:58           ` Fam Zheng
2015-03-10  3:12           ` Zhang Haoyu [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=201503101112105657084@sangfor.com.cn \
    --to=zhanghy@sangfor.com.cn \
    --cc=famz@redhat.com \
    --cc=jsnow@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=mtosatti@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    --cc=vsementsov@parallels.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.