From: Mohammed Gamal <mohammed.gamal@profitbricks.com>
To: qemu-devel@nongnu.org
Cc: Anshul Makkar <anshul.makkar@profitbricks.com>,
Mikhail Sennikovskii <mikhail.sennikovskii@profitbricks.com>,
Elmar Gerdes <elmar.gerdes@profitbricks.com>,
Eduardo Otubo <eduardo.otubo@profitbricks.com>,
Luiz Capitulino <lcapitulino@redhat.com>
Subject: [Qemu-devel] QMP unix socket randomly returning -EAGAIN
Date: Fri, 12 Dec 2014 16:54:39 +0100 [thread overview]
Message-ID: <CAHTgm8LLtikAxFEDtfb1xevUn8CMNxM2Yj1pFj8FDmfrKwS7mg@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 780 bytes --]
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?
Regards,
Mohammed
[-- Attachment #2: Type: text/html, Size: 917 bytes --]
next reply other threads:[~2014-12-12 15:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-12 15:54 Mohammed Gamal [this message]
2014-12-15 14:00 ` [Qemu-devel] QMP unix socket randomly returning -EAGAIN Luiz Capitulino
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=CAHTgm8LLtikAxFEDtfb1xevUn8CMNxM2Yj1pFj8FDmfrKwS7mg@mail.gmail.com \
--to=mohammed.gamal@profitbricks.com \
--cc=anshul.makkar@profitbricks.com \
--cc=eduardo.otubo@profitbricks.com \
--cc=elmar.gerdes@profitbricks.com \
--cc=lcapitulino@redhat.com \
--cc=mikhail.sennikovskii@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 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).