From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:59265)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <paolo.bonzini@gmail.com>) id 1ZC2Ci-0002i0-Vg
	for qemu-devel@nongnu.org; Mon, 06 Jul 2015 04:56:49 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <paolo.bonzini@gmail.com>) id 1ZC21T-0002PK-BO
	for qemu-devel@nongnu.org; Mon, 06 Jul 2015 04:45:42 -0400
Received: from mail-wg0-x22e.google.com ([2a00:1450:400c:c00::22e]:36739)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <paolo.bonzini@gmail.com>) id 1ZC21T-0002O8-23
	for qemu-devel@nongnu.org; Mon, 06 Jul 2015 04:45:07 -0400
Received: by wguu7 with SMTP id u7so133835830wgu.3
	for <qemu-devel@nongnu.org>; Mon, 06 Jul 2015 01:45:06 -0700 (PDT)
Sender: Paolo Bonzini <paolo.bonzini@gmail.com>
References: <559A342C.6020207@huawei.com>
From: Paolo Bonzini <pbonzini@redhat.com>
Message-ID: <559A4010.30808@redhat.com>
Date: Mon, 6 Jul 2015 10:45:04 +0200
MIME-Version: 1.0
In-Reply-To: <559A342C.6020207@huawei.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
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 09:54, zhanghailiang wrote:
> 
> From host, we found that QEMU vcpu1 thread and vcpu7 thread were not
> consuming any cpu (Should be in idle state),
> All of VCPUs' stacks in host is like bellow:
> 
> [<ffffffffa07089b5>] kvm_vcpu_block+0x65/0xa0 [kvm]
> [<ffffffffa071c7c1>] __vcpu_run+0xd1/0x260 [kvm]
> [<ffffffffa071d508>] kvm_arch_vcpu_ioctl_run+0x68/0x1a0 [kvm]
> [<ffffffffa0709cee>] kvm_vcpu_ioctl+0x38e/0x580 [kvm]
> [<ffffffff8116be8b>] do_vfs_ioctl+0x8b/0x3b0
> [<ffffffff8116c251>] sys_ioctl+0xa1/0xb0
> [<ffffffff81468092>] system_call_fastpath+0x16/0x1b
> [<00002ab9fe1f99a7>] 0x2ab9fe1f99a7
> [<ffffffffffffffff>] 0xffffffffffffffff
> 
> We looked into the kernel codes that could leading to the above 'Stuck'
> warning,
> and found that the only possible is the emulation of 'cpuid' instruct in
> kvm/qemu has something wrong.
> But since we can’t reproduce this problem, we are not quite sure.
> Is there any possible that the cupid emulation in kvm/qemu has some bug ?

Can you explain the relationship to the cpuid emulation?  What do the
traces say about vcpus 1 and 7?

Paolo