From: Paolo Bonzini <pbonzini@redhat.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: Sander Eikelenboom <linux@eikelenboom.it>,
Anthony PERARD <anthony@citrix.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
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
Date: Thu, 18 Apr 2013 15:32:37 +0200 [thread overview]
Message-ID: <516FF5F5.50902@redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1304181425400.7254@kaball.uk.xensource.com>
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
next prev parent reply other threads:[~2013-04-18 13:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-16 19:23 [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 Sander Eikelenboom
2013-04-18 13:27 ` Stefano Stabellini
2013-04-18 13:32 ` Paolo Bonzini [this message]
2013-04-18 23:21 ` Sander Eikelenboom
2013-04-19 7:27 ` Paolo Bonzini
2013-04-19 7:52 ` Sander Eikelenboom
2013-04-19 8:04 ` Paolo Bonzini
2013-04-19 12:56 ` Sander Eikelenboom
2013-04-19 13:00 ` Paolo Bonzini
2013-04-19 16:53 ` Sander Eikelenboom
2013-04-19 17:00 ` Paolo Bonzini
2013-04-19 17:03 ` Sander Eikelenboom
[not found] ` <1897230904.20130419191113@eikelenboom.it>
[not found] ` <51717BCF.8030208@redhat.com>
2013-04-20 14:36 ` Sander Eikelenboom
2013-04-19 7:56 ` Sander Eikelenboom
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=516FF5F5.50902@redhat.com \
--to=pbonzini@redhat.com \
--cc=anthony@citrix.com \
--cc=linux@eikelenboom.it \
--cc=qemu-devel@nongnu.org \
--cc=stefano.stabellini@eu.citrix.com \
--cc=xen-devel@lists.xen.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).