From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:55779) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VW3lu-00072c-7X for qemu-devel@nongnu.org; Tue, 15 Oct 2013 08:30:52 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VW3ln-0002Um-QW for qemu-devel@nongnu.org; Tue, 15 Oct 2013 08:30:45 -0400 Message-ID: <525D355F.4060504@redhat.com> Date: Tue, 15 Oct 2013 14:30:23 +0200 From: Paolo Bonzini MIME-Version: 1.0 References: <7A2C95E1327F7148AB122F200A3EFA403447CB6A@SZXEMA502-MBX.china.huawei.com> <525D2C61.7080203@redhat.com> <7A2C95E1327F7148AB122F200A3EFA403447CBE1@SZXEMA502-MBX.china.huawei.com> In-Reply-To: <7A2C95E1327F7148AB122F200A3EFA403447CBE1@SZXEMA502-MBX.china.huawei.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [RFH] Qemu main thread is blocked in g_poll in windows guest List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Xiexiangyou Cc: "qemu-devel-request@nongnu.org" , Luonengjun , "qemu-devel@nongnu.org" , "kvm@vger.kernel.org" , "Huangpeng (Peter)" Il 15/10/2013 14:18, Xiexiangyou ha scritto: > (gdb) bt > #0 0x00007f9ba661a423 in poll () from /lib64/libc.so.6 > #1 0x000000000059460f in os_host_main_loop_wait (timeout=4294967295) at main-loop.c:226 > #2 0x00000000005946a4 in main_loop_wait (nonblocking=0) at main-loop.c:464 > #3 0x0000000000619309 in main_loop () at vl.c:2182 > #4 0x000000000061fb5e in main (argc=54, argv=0x7fff879830c8, envp=0x7fff87983280) at vl.c:4611 This backtrace looks okay. poll is not holding the "iothread lock" and thus the VCPU thread can run QEMU code. It also looks like the VCPU thread is doing nothing special besides running KVM_RUN. Did you take the backtrace during one of these "hangups"? Paolo