From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:47291)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <wency@cn.fujitsu.com>) id 1Z8P4X-00076A-CR
	for qemu-devel@nongnu.org; Fri, 26 Jun 2015 04:33:18 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <wency@cn.fujitsu.com>) id 1Z8P4U-0007dY-0r
	for qemu-devel@nongnu.org; Fri, 26 Jun 2015 04:33:17 -0400
Received: from [59.151.112.132] (port=31548 helo=heian.cn.fujitsu.com)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <wency@cn.fujitsu.com>) id 1Z8P4S-0007cd-5t
	for qemu-devel@nongnu.org; Fri, 26 Jun 2015 04:33:13 -0400
Message-ID: <558D0F13.30803@cn.fujitsu.com>
Date: Fri, 26 Jun 2015 16:36:35 +0800
From: Wen Congyang <wency@cn.fujitsu.com>
MIME-Version: 1.0
References: <1435303314-10021-1-git-send-email-lizhijian@cn.fujitsu.com>
	<558D072F.7030806@huawei.com>
In-Reply-To: <558D072F.7030806@huawei.com>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 7bit
Subject: Re: [Qemu-devel] [PATCH 0/2] avoid a hotplug operation leading
 migration's source side abort
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
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

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
> 
> 
> 
>