From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:52517)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <pbonzini@redhat.com>) id 1ZC4Ba-0002PQ-BQ
	for qemu-devel@nongnu.org; Mon, 06 Jul 2015 07:03:43 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <pbonzini@redhat.com>) id 1ZC4BX-0008HF-5g
	for qemu-devel@nongnu.org; Mon, 06 Jul 2015 07:03:42 -0400
Received: from mx1.redhat.com ([209.132.183.28]:57090)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <pbonzini@redhat.com>) id 1ZC4BX-0008H3-06
	for qemu-devel@nongnu.org; Mon, 06 Jul 2015 07:03:39 -0400
References: <559A342C.6020207@huawei.com> <559A4010.30808@redhat.com>
	<559A516E.1070000@huawei.com>
From: Paolo Bonzini <pbonzini@redhat.com>
Message-ID: <559A6086.1040709@redhat.com>
Date: Mon, 6 Jul 2015 13:03:34 +0200
MIME-Version: 1.0
In-Reply-To: <559A516E.1070000@huawei.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Subject: Re: [Qemu-devel] [BUG/RFC] Two cpus are not brought up normally in
 SLES11 sp3 VM after reboot
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: zhanghailiang <zhang.zhanghailiang@huawei.com>, kvm@vger.kernel.org
Cc: peter.huangpeng@huawei.com, "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>



On 06/07/2015 11:59, zhanghailiang wrote:
> 
> 
> Besides, the follow is the cpus message got from host.
> 80FF72F5-FF6D-E411-A8C8-000000821800:/home/fsp/hrg # virsh
> qemu-monitor-command instance-0000000
> * CPU #0: pc=0x00007f64160c683d thread_id=68570
>   CPU #1: pc=0xffffffff810301f1 (halted) thread_id=68573
>   CPU #2: pc=0xffffffff810301e2 (halted) thread_id=68575
>   CPU #3: pc=0xffffffff810301e2 (halted) thread_id=68576
>   CPU #4: pc=0xffffffff810301e2 (halted) thread_id=68577
>   CPU #5: pc=0xffffffff810301e2 (halted) thread_id=68578
>   CPU #6: pc=0xffffffff810301e2 (halted) thread_id=68583
>   CPU #7: pc=0xffffffff810301f1 (halted) thread_id=68584
> 
> Oh, i also forgot to mention in the above message that, we have bond
> each vCPU to different physical CPU in
> host.

Can you capture a trace on the host (trace-cmd record -e kvm) and send
it privately?  Please note which CPUs get stuck, since I guess it's not
always 1 and 7.

Paolo