From: Chrysostomos Nanakos <cnanakos@grnet.gr>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: "Chrysostomos Nanakos" <cnanakos@grnet.gr>,
"Benoît Canet" <benoit.canet@irqsave.net>,
pingfank@linux.vnet.ibm.com, famz@redhat.com, kroosec@gmail.com,
jan.kiszka@siemens.com, mjt@tls.msk.ru, qemu-devel@nongnu.org,
stefanha@redhat.com, sw@weilnetz.de, kwolf@redhat.com,
afaerber@suse.de, aliguori@amazon.com
Subject: Re: [Qemu-devel] [PATCH v2] async: aio_context_new(): Handle event_notifier_init failure
Date: Tue, 16 Sep 2014 18:50:38 +0300 [thread overview]
Message-ID: <20140916155038.GB4631@blackdevil> (raw)
In-Reply-To: <54185B0C.6090008@redhat.com>
On Tue, Sep 16, 2014 at 05:45:16PM +0200, Paolo Bonzini wrote:
> Il 16/09/2014 17:43, Chrysostomos Nanakos ha scritto:
> >> > error_propagate(errp, local_error);
> >> > return;
> > Just to note that after propagating the error and returning, QEMU fails
> > silently without printing the error message.
>
> What is your testcase?
I am starting QEMU with the options below and explicitly set iothread->ctx to
NULL. Is that ok as a testcase or should I reduce my open files limit to
produce the error?
qemu --enable-kvm -smp 2 -m 1024 -object iothread,id=iothread0 -drive file=archipelago:fedora_stable
-vnc 0.0.0.0:0 -qmp tcp:127.0.0.1:8888,server,nowait
No error message, at least the propagated one, fails silently.
Regards,
Chrysostomos.
next prev parent reply other threads:[~2014-09-16 15:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-16 9:06 [Qemu-devel] [PATCH v2] async: aio_context_new(): Handle event_notifier_init failure Chrysostomos Nanakos
2014-09-16 9:06 ` Chrysostomos Nanakos
2014-09-16 13:53 ` Benoît Canet
2014-09-16 13:57 ` Paolo Bonzini
2014-09-16 15:43 ` Chrysostomos Nanakos
2014-09-16 15:45 ` Paolo Bonzini
2014-09-16 15:50 ` Chrysostomos Nanakos [this message]
2014-09-16 17:58 ` Chrysostomos Nanakos
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=20140916155038.GB4631@blackdevil \
--to=cnanakos@grnet.gr \
--cc=afaerber@suse.de \
--cc=aliguori@amazon.com \
--cc=benoit.canet@irqsave.net \
--cc=famz@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=kroosec@gmail.com \
--cc=kwolf@redhat.com \
--cc=mjt@tls.msk.ru \
--cc=pbonzini@redhat.com \
--cc=pingfank@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=sw@weilnetz.de \
/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).