All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Sander Eikelenboom <linux@eikelenboom.it>
Cc: Gerd Hoffmann <kraxel@redhat.com>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
	Anthony PERARD <anthony@citrix.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	Stefano Stabellini <stefano.stabellini@eu.citrix.com>
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: Fri, 19 Apr 2013 10:04:22 +0200	[thread overview]
Message-ID: <5170FA86.6010700@redhat.com> (raw)
In-Reply-To: <6110678685.20130419095209@eikelenboom.it>

Il 19/04/2013 09:52, Sander Eikelenboom ha scritto:
>> > What version is glib on the host?
> Ah i knew i forgot to look something up ..
> 
> ii  libglib2.0-0                                                                   2.24.2-1                           The GLib library of C routines
> ii  libglib2.0-data                                                                2.24.2-1                           Common files for GLib library
> ii  libglib2.0-dev                                                                 2.24.2-1                           Development files for the GLib library

This very likely has the same deadlock bug that Gerd found on RHEL6.

Paolo

  reply	other threads:[~2013-04-19  8:04 UTC|newest]

Thread overview: 27+ 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
2013-04-18 13:32   ` [Qemu-devel] " Paolo Bonzini
2013-04-18 23:21     ` Sander Eikelenboom
2013-04-18 23:21     ` [Qemu-devel] " Sander Eikelenboom
2013-04-19  7:27       ` Paolo Bonzini
2013-04-19  7:52         ` Sander Eikelenboom
2013-04-19  8:04           ` Paolo Bonzini [this message]
2013-04-19 12:56             ` Sander Eikelenboom
2013-04-19 13:00               ` Paolo Bonzini
2013-04-19 13:00               ` [Qemu-devel] " Paolo Bonzini
2013-04-19 16:53                 ` Sander Eikelenboom
2013-04-19 16:53                 ` [Qemu-devel] " Sander Eikelenboom
2013-04-19 17:00                   ` Paolo Bonzini
2013-04-19 17:00                   ` [Qemu-devel] " Paolo Bonzini
2013-04-19 17:03                     ` Sander Eikelenboom
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-20 14:36                         ` [Qemu-devel] " Sander Eikelenboom
2013-04-19 12:56             ` Sander Eikelenboom
2013-04-19  8:04           ` Paolo Bonzini
2013-04-19  7:52         ` Sander Eikelenboom
2013-04-19  7:56         ` Sander Eikelenboom
2013-04-19  7:56         ` [Qemu-devel] " Sander Eikelenboom
2013-04-19  7:27       ` Paolo Bonzini
2013-04-18 13:27 ` Stefano Stabellini

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=5170FA86.6010700@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=anthony@citrix.com \
    --cc=kraxel@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.