From: Wen Congyang <wency@cn.fujitsu.com>
To: Gonglei <arei.gonglei@huawei.com>,
Li Zhijian <lizhijian@cn.fujitsu.com>,
qemu-devel@nongnu.org, pbonzini@redhat.com, quintela@redhat.com,
amit.shah@redhat.com
Subject: Re: [Qemu-devel] [PATCH 0/2] avoid a hotplug operation leading migration's source side abort
Date: Fri, 26 Jun 2015 16:36:35 +0800 [thread overview]
Message-ID: <558D0F13.30803@cn.fujitsu.com> (raw)
In-Reply-To: <558D072F.7030806@huawei.com>
On 06/26/2015 04:02 PM, Gonglei wrote:
> On 2015/6/26 15:21, Li Zhijian wrote:
>> qemu migration's source side will exit unexpectedly when we hotplug a deivce
>> during a migration is processing.
>
> Can we simply disable hot-plugging functions during migration process?
1. there is no API to disable it, and it is not a simple work.
2. For HA/FT, we will use migration to implement checkpoint. We should
enable hot-plug when HA/FT is running. There are too many works to do
to make it work. The first step is to fix the problem.
Thanks
Wen Congyang
>
> Regards,
> -Gonglei
>
>> we can reproduced it easily by following step
>> 1. do something with dirty memory requently(like memtester) in guest
>> 2. startup a background migraion with '-d' option
>> 3. hotplug a device(device_add e1000,id=mye1000)
>> 4. stop step.1, let guest idle so that migration can complete fastly
>
>
>
>
prev parent reply other threads:[~2015-06-26 8:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-26 7:21 [Qemu-devel] [PATCH 0/2] avoid a hotplug operation leading migration's source side abort Li Zhijian
2015-06-26 7:21 ` [Qemu-devel] [PATCH 1/2] migration: protect migration_bitmap Li Zhijian
2015-06-26 7:21 ` [Qemu-devel] [PATCH 2/2] migration: extend migration_bitmap Li Zhijian
2015-06-26 9:05 ` Juan Quintela
2015-06-26 9:15 ` Wen Congyang
2015-06-26 9:57 ` Igor Mammedov
2015-06-26 9:42 ` Li Zhijian
2015-06-26 8:02 ` [Qemu-devel] [PATCH 0/2] avoid a hotplug operation leading migration's source side abort Gonglei
2015-06-26 8:36 ` Wen Congyang [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=558D0F13.30803@cn.fujitsu.com \
--to=wency@cn.fujitsu.com \
--cc=amit.shah@redhat.com \
--cc=arei.gonglei@huawei.com \
--cc=lizhijian@cn.fujitsu.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@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.