All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: zhanghailiang <zhang.zhanghailiang@huawei.com>, kvm@vger.kernel.org
Cc: peter.huangpeng@huawei.com,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [BUG/RFC] Two cpus are not brought up normally in SLES11 sp3 VM after reboot
Date: Mon, 6 Jul 2015 10:45:04 +0200	[thread overview]
Message-ID: <559A4010.30808@redhat.com> (raw)
In-Reply-To: <559A342C.6020207@huawei.com>



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

WARNING: multiple messages have this Message-ID (diff)
From: Paolo Bonzini <pbonzini@redhat.com>
To: zhanghailiang <zhang.zhanghailiang@huawei.com>, kvm@vger.kernel.org
Cc: peter.huangpeng@huawei.com,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [BUG/RFC] Two cpus are not brought up normally in SLES11 sp3 VM after reboot
Date: Mon, 6 Jul 2015 10:45:04 +0200	[thread overview]
Message-ID: <559A4010.30808@redhat.com> (raw)
In-Reply-To: <559A342C.6020207@huawei.com>



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

  reply	other threads:[~2015-07-06  8:45 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-06  7:54 [BUG/RFC] Two cpus are not brought up normally in SLES11 sp3 VM after reboot zhanghailiang
2015-07-06  7:54 ` [Qemu-devel] " zhanghailiang
2015-07-06  8:45 ` Paolo Bonzini [this message]
2015-07-06  8:45   ` Paolo Bonzini
2015-07-06  9:59   ` zhanghailiang
2015-07-06  9:59     ` [Qemu-devel] " zhanghailiang
2015-07-06 11:03     ` Paolo Bonzini
2015-07-06 11:03       ` [Qemu-devel] " Paolo Bonzini
2015-07-07 11:23     ` Igor Mammedov
2015-07-07 11:23       ` [Qemu-devel] " Igor Mammedov
2015-07-07 11:43       ` zhanghailiang
2015-07-07 11:43         ` [Qemu-devel] " zhanghailiang
2015-07-07 12:21         ` Igor Mammedov
2015-07-07 12:39           ` zhanghailiang
2015-07-07 12:39             ` zhanghailiang

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=559A4010.30808@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=peter.huangpeng@huawei.com \
    --cc=qemu-devel@nongnu.org \
    --cc=zhang.zhanghailiang@huawei.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.