From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:59430) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1USoxh-0004nh-WA for qemu-devel@nongnu.org; Thu, 18 Apr 2013 09:33:18 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1USoxg-0003op-Hf for qemu-devel@nongnu.org; Thu, 18 Apr 2013 09:33:17 -0400 Received: from mx1.redhat.com ([209.132.183.28]:24362) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1USoxg-0003ok-AE for qemu-devel@nongnu.org; Thu, 18 Apr 2013 09:33:16 -0400 Message-ID: <516FF5F5.50902@redhat.com> Date: Thu, 18 Apr 2013 15:32:37 +0200 From: Paolo Bonzini MIME-Version: 1.0 References: <715415426.20130416212325@eikelenboom.it> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] xen-unstable qemu-upstream: libxl: error: libxl_qmp.c:440:qmp_next: timeout, libxl_qmp.c:705:libxl__qmp_initialize: Failed to connect to QMP List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Stefano Stabellini Cc: Sander Eikelenboom , Anthony PERARD , "qemu-devel@nongnu.org" , "xen-devel@lists.xen.org" Il 18/04/2013 15:27, Stefano Stabellini ha scritto: >> > >> > Any thing that springs to mind ? > Nope, sorry. > Given the commit that your bisection identified and the error message, > it's clear that it's a QMP connection issue from libxl. I would start > looking in libxl_qmp.c. > Maybe Anthony (CC'ed) has some ideas. What host is this? It is likely a glib or qemu-char bug (hopefully the deadlock that Gerd found on RHEL6) that was latent up to this patch. Paolo