From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:47771) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Z5TnP-0003dK-TN for qemu-devel@nongnu.org; Thu, 18 Jun 2015 02:59:32 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Z5TnP-0006eh-3X for qemu-devel@nongnu.org; Thu, 18 Jun 2015 02:59:31 -0400 Sender: Paolo Bonzini Message-ID: <55826C49.2030605@redhat.com> Date: Thu, 18 Jun 2015 08:59:21 +0200 From: Paolo Bonzini MIME-Version: 1.0 References: <55803637.3060607@kamp.de> <20150617083539.GA4202@noname.str.redhat.com> <55826789.6080008@kamp.de> In-Reply-To: <55826789.6080008@kamp.de> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [Qemu-block] RFC cdrom in own thread? List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Peter Lieven , Kevin Wolf , Stefan Hajnoczi Cc: qemu-devel , qemu block On 18/06/2015 08:39, Peter Lieven wrote: > > It seems like the mainloop is waiting here: > > #0 0x00007ffff606c89c in __lll_lock_wait () > from /lib/x86_64-linux-gnu/libpthread.so.0 > No symbol table info available. > #1 0x00007ffff6068065 in _L_lock_858 () > from /lib/x86_64-linux-gnu/libpthread.so.0 > No symbol table info available. > #2 0x00007ffff6067eba in pthread_mutex_lock () > from /lib/x86_64-linux-gnu/libpthread.so.0 > No symbol table info available. > #3 0x00005555559f2557 in qemu_mutex_lock (mutex=0x555555ed6d40) > at util/qemu-thread-posix.c:76 > err = 0 > __func__ = "qemu_mutex_lock" > #4 0x00005555556306ef in qemu_mutex_lock_iothread () > at /usr/src/qemu-2.2.0/cpus.c:1123 > No locals. This means the VCPU is busy with some synchronous activity---maybe a bdrv_aio_cancel? Paolo