Re: [Qemu-discuss] Debugging a qemu hang using gdb

[Peter Maydell]

On Fri, 24 May 2019 at 18:48, Mark Wood-Patrick <address@hidden> wrote:
>
> When qemu stops responding I'm still able to use the qemu monitor and "info
> status" shows the vm as running but if I do "info cpus" the monitor also
> hangs
>
> I'm using qemu 2.8.0
>
> Looks like we are hung up in pthread_cond_wait
>
> #0  0x00002aaaac98f68c in pthread_cond_wait@@GLIBC_2.3.2 () from
> /lib64/libpthread.so.0
> #1  0x0000555555d006da in qemu_cond_wait (cond=0x55555638b060
> <qemu_work_cond>, mutex=0x555556384660 <qemu_global_mutex>) at
> util/qemu-thread-posix.c:137
> #2  0x00005555559754f7 in do_run_on_cpu (cpu=0x55555693b1a0,
> func=0x5555557f2c07 <do_kvm_cpu_synchronize_state>, data=...,
> mutex=0x555556384660 <qemu_global_mutex>)
>     at cpus-common.c:152

Can you provide the backtrace for all threads (gdb's "thread apply all bt"
ought to do it), please? We might be able to see whether one of the other
threads has got stuck somehow...

thanks
-- PMM