[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [BUG/RFC] Two cpus are not brought up normally in SLES1
|
From: |
Paolo Bonzini |
|
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 |
|
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.0.1 |
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