From: Kevin Wolf <kwolf@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>,
Luiz Capitulino <lcapitulino@redhat.com>
Cc: Qemu-devel@nongnu.org
Subject: [Qemu-devel] Ignoring errno makes QMP errors suck
Date: Mon, 26 Mar 2012 10:39:50 +0200 [thread overview]
Message-ID: <4F702B56.8030400@redhat.com> (raw)
Hi,
I keep getting reports of problems, with nice error descriptions that
usually look very similar to what I produced here:
{"execute":"blockdev-snapshot-sync","arguments":{"device":"ide0-hd0","snapshot-file":"/tmp/backing.qcow2"}}
{"error": {"class": "OpenFileFailed", "desc": "Could not open
'/tmp/backing.qcow2'", "data": {"filename": "/tmp/backing.qcow2"}}}
Who can tell me what has happened here? Oh, yes, the command failed, I
would have guessed that from the "error" key. But the actual error
description is as useless as it gets. It doesn't tell me anything about
_why_ the snapshot couldn't be created. ("Permission denied" would have
been the helpful additional information in this case)
How should management tools ever be able to provide a helpful error
message to their users if all they get is this useless "something went
wrong" error?
Kevin
next reply other threads:[~2012-03-26 8:36 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-26 8:39 Kevin Wolf [this message]
2012-03-26 12:46 ` [Qemu-devel] Ignoring errno makes QMP errors suck Luiz Capitulino
2012-03-26 13:13 ` Kevin Wolf
2012-03-26 13:28 ` Luiz Capitulino
2012-03-26 13:39 ` Anthony Liguori
2012-03-26 14:04 ` Kevin Wolf
2012-03-26 14:33 ` Luiz Capitulino
2012-03-26 14:47 ` Kevin Wolf
2012-03-26 14:54 ` Luiz Capitulino
2012-03-26 15:20 ` Kevin Wolf
2012-03-26 13:37 ` Anthony Liguori
2012-03-26 15:08 ` Kevin Wolf
2012-03-26 15:14 ` Anthony Liguori
2012-03-26 15:34 ` Kevin Wolf
2012-03-26 15:38 ` Anthony Liguori
2012-03-26 15:59 ` Kevin Wolf
2012-03-26 16:01 ` Anthony Liguori
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=4F702B56.8030400@redhat.com \
--to=kwolf@redhat.com \
--cc=Qemu-devel@nongnu.org \
--cc=anthony@codemonkey.ws \
--cc=lcapitulino@redhat.com \
/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).