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 13:03:34 +0200	[thread overview]
Message-ID: <559A6086.1040709@redhat.com> (raw)
In-Reply-To: <559A516E.1070000@huawei.com>



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

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 13:03:34 +0200	[thread overview]
Message-ID: <559A6086.1040709@redhat.com> (raw)
In-Reply-To: <559A516E.1070000@huawei.com>



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

  reply	other threads:[~2015-07-06 11:03 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
2015-07-06  8:45   ` [Qemu-devel] " Paolo Bonzini
2015-07-06  9:59   ` zhanghailiang
2015-07-06  9:59     ` [Qemu-devel] " zhanghailiang
2015-07-06 11:03     ` Paolo Bonzini [this message]
2015-07-06 11:03       ` 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=559A6086.1040709@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.