From: "Andreas Färber" <afaerber@suse.de>
To: yinyin <yin.yin@cs2c.com.cn>
Cc: qemu-devel@nongnu.org, Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 0/3] dataplane: virtio-blk live migration with x-data-plane=on
Date: Tue, 23 Jul 2013 11:30:51 +0200 [thread overview]
Message-ID: <51EE4D4B.3070808@suse.de> (raw)
In-Reply-To: <F6ACEFCD-79B5-4105-ABC7-559245226874@cs2c.com.cn>
Hi,
Am 23.07.2013 11:19, schrieb yinyin:
> Hi, Stefan:
> during the migration, the source, not the destination, will start dataplane again....
> I think the process of migration with dataplane as follows:
> 1. migration begin to start
> 2. the migration source stop the dataplane
> 3. do migration ...
> 4. migration completed, the destination start the dataplane.
I can't speak for the dataplane, but in general the source guest is
expected to continue working during live migration (that's the "live"
part) until it has been fully transferred to the destination.
HTH,
Andreas
> when migration start, the source dataplane should already stopped, and not start again, if there is no cancel or abort.
> But the trace show that, in step 3 above, the source dataplane will be start by virtio_blk_handle_output. I'm afraid of some inconsistent will happen there.Is it right?
>
> There is no crash found, I just use this trace to understand the flow of dataplane migration.
>
> Yin Yin
> yin.yin@cs2c.com.cn
>
>
> 在 2013-7-23，下午4:51，Stefan Hajnoczi <stefanha@redhat.com> 写道：
>
>> On Fri, Jul 19, 2013 at 01:33:12PM +0800, yinyin wrote:
>>> I use systemtap to test this patch,the migration will success. But I found the dataplane will start again after migration start. the virtio_blk_handle_output will start dataplane.
>>
>> Hi Yin Yin,
>> Thank you for testing the patch. It is not clear to me whether you
>> encountered a problem or not.
>>
>> It is expected that the destination will start the dataplane thread.
>> Was there a crash or some reason why you posted these traces?
>>
>> Stefan
>>
>
>
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
next prev parent reply other threads:[~2013-07-23 9:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-19 5:33 [Qemu-devel] [PATCH 0/3] dataplane: virtio-blk live migration with x-data-plane=on yinyin
2013-07-23 8:51 ` Stefan Hajnoczi
2013-07-23 9:19 ` yinyin
2013-07-23 9:30 ` Andreas Färber [this message]
2013-07-23 9:43 ` yinyin
2013-07-23 9:59 ` Andreas Färber
2013-07-23 13:20 ` Stefan Hajnoczi
-- strict thread matches above, loose matches on Subject: below --
2013-07-17 9:35 Stefan Hajnoczi
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=51EE4D4B.3070808@suse.de \
--to=afaerber@suse.de \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=yin.yin@cs2c.com.cn \
/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).