From: Luiz Capitulino <lcapitulino@redhat.com>
To: Mohammed Gamal <mohammed.gamal@profitbricks.com>
Cc: Anshul Makkar <anshul.makkar@profitbricks.com>,
Mikhail Sennikovskii <mikhail.sennikovskii@profitbricks.com>,
qemu-devel@nongnu.org,
Eduardo Otubo <eduardo.otubo@profitbricks.com>,
Elmar Gerdes <elmar.gerdes@profitbricks.com>
Subject: Re: [Qemu-devel] QMP unix socket randomly returning -EAGAIN
Date: Mon, 15 Dec 2014 09:00:06 -0500 [thread overview]
Message-ID: <20141215090006.636b5d3e@redhat.com> (raw)
In-Reply-To: <CAHTgm8LLtikAxFEDtfb1xevUn8CMNxM2Yj1pFj8FDmfrKwS7mg@mail.gmail.com>
On Fri, 12 Dec 2014 16:54:39 +0100
Mohammed Gamal <mohammed.gamal@profitbricks.com> wrote:
> Hi,
>
> We are experiencing random errors with communication with VMs with QMP via
> unix sockets. At some moment of time the QMP socket keeps on returning
> -EAGAIN and never recovering from this state unless the qemu process is
> stopped then started. This socket hickup happens specfically when
> connecting to the socket or receiving a response from it.
>
> I suspected that this might be caused by the guest hanging on some IO or
> being unresponsive for any reason, but the VMs in question were not
> unresponsive at these times and could be accessed via VNC or SSH normally.
> I've seen this on machines runnnig qemu 1.0,1 1.2.0 and 2.0.0
>
> I am suspecting it might be a bug in the monitor code, but I couldn't reach
> anything tangible. Any ideas what might be causing this?
No. Can you provide a reproducer?
prev parent reply other threads:[~2014-12-15 14:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-12 15:54 [Qemu-devel] QMP unix socket randomly returning -EAGAIN Mohammed Gamal
2014-12-15 14:00 ` Luiz Capitulino [this message]
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=20141215090006.636b5d3e@redhat.com \
--to=lcapitulino@redhat.com \
--cc=anshul.makkar@profitbricks.com \
--cc=eduardo.otubo@profitbricks.com \
--cc=elmar.gerdes@profitbricks.com \
--cc=mikhail.sennikovskii@profitbricks.com \
--cc=mohammed.gamal@profitbricks.com \
--cc=qemu-devel@nongnu.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.