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:59:33 +0200 [thread overview]
Message-ID: <51EE5405.3020109@suse.de> (raw)
In-Reply-To: <67E6C951-BB76-493D-AD1D-09F34512C3AF@cs2c.com.cn>
Am 23.07.2013 11:43, schrieb yinyin:
> 在 2013-7-23，下午5:30，Andreas Färber <afaerber@suse.de> 写道：
>> Am 23.07.2013 11:19, schrieb yinyin:
>>> 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.
>
> when dataplane stop, the source guest can continue work, but not use dataplane thread.
So how would it do I/O then?
Andreas
--
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:59 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
2013-07-23 9:43 ` yinyin
2013-07-23 9:59 ` Andreas Färber [this message]
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=51EE5405.3020109@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).