From: "Zhang Haoyu" <zhanghy@sangfor.com.cn>
To: Paolo Bonzini <pbonzini@redhat.com>, qemu-devel <qemu-devel@nongnu.org>
Cc: Gleb Natapov <gleb@kernel.org>, Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] question about live migration with storage
Date: Tue, 10 Mar 2015 10:01:34 +0800 [thread overview]
Message-ID: <201503101001341072349@sangfor.com.cn> (raw)
In-Reply-To: 201501151756164579870@sangfor.com.cn
On 2015-01-15 18:08:39, Paolo Bonzini wrote:
>
> On 15/01/2015 10:56, Zhang Haoyu wrote:
> > I see, when waiting the completion of drive_mirror IO, the coroutine will be
> > switched back to main-thread to poll and process other events, like qmp request,
> > then after the IO completed, coroutine will be switched back in main-loop process, right?
> >
> > Another question:
> > while starting to migrate storage, will the unused sector be allocated and transferred?
> > regarding the thin-provisioning qcow2 disk, will extra large IO requests be
> > performed, and more data be transferred for the unallocated clusters?
>
> No.
>
My test results show that
when using thin-provisioning qcow2 image(created by qemu-img create -f qcow2 preallocation=metadata),
even the unallocated sectors will be transferred to destination, so much data is transferred,
so the qcow2 image in destination is full allocated.
Thanks,
Zhang Haoyu
> Paolo
next prev parent reply other threads:[~2015-03-10 2:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-13 1:48 [Qemu-devel] question about live migration with storage Zhang Haoyu
2015-01-13 2:03 ` Zhang Haoyu
2015-01-13 9:45 ` Paolo Bonzini
2015-01-14 2:41 ` Zhang Haoyu
2015-01-14 7:34 ` Paolo Bonzini
2015-01-14 7:58 ` Zhang Haoyu
2015-01-14 9:06 ` Paolo Bonzini
2015-01-15 3:54 ` Zhang Haoyu
2015-01-15 9:11 ` Paolo Bonzini
2015-01-15 9:56 ` Zhang Haoyu
2015-01-15 10:08 ` Paolo Bonzini
2015-03-10 2:01 ` Zhang Haoyu [this message]
2015-03-25 13:07 ` Paolo Bonzini
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=201503101001341072349@sangfor.com.cn \
--to=zhanghy@sangfor.com.cn \
--cc=gleb@kernel.org \
--cc=pbonzini@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 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.