From: "Andreas Färber" <afaerber@suse.de>
To: armbru@redhat.com, qemu-devel@nongnu.org
Cc: Anthony Liguori <aliguori@amazon.com>, lcapitulino@redhat.com
Subject: Re: [Qemu-devel] [PATCH] qdev-monitor: Improve error message for -device nonexistant
Date: Fri, 20 Dec 2013 12:13:32 +0100 [thread overview]
Message-ID: <52B4265C.5060803@suse.de> (raw)
In-Reply-To: <1387463413-20070-1-git-send-email-armbru@redhat.com>
Am 19.12.2013 15:30, schrieb armbru@redhat.com:
> From: Markus Armbruster <armbru@redhat.com>
>
> Once upon a time, the error message was:
>
> qemu: -device nonexistant: "Device "nonexistant" not found. Try -device '?' for a list.
>
> But progress marches on, and conversion to QError (commit 0204276)
> changed it into:
>
> Invalid parameter 'driver'
> Try with argument '?' for a list.
>
> Progress didn't stop there, of course. After a couple of iterations,
> we arrived at the current message (commit 6acbe4c):
>
> qemu: -device nonexistant: Parameter 'driver' expects device type
>
> Mission accomplished: this is complete mush.
>
> We've since abandoned our quest for "rich" error objects, fortunately
> before it turned all error messages into mush. Time to undo the
> damage to this one. Make it:
>
> qemu: -device nonexistant: nonexistant is not a valid device model name
>
> Signed-off-by: Markus Armbruster <armbru@redhat.com>
> ---
> qdev-monitor.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
Thanks, rebased onto your other fix and applied to qom-next:
https://github.com/afaerber/qemu-cpu/commits/qom-next
Andreas
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
prev parent reply other threads:[~2013-12-20 11:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-19 14:30 [Qemu-devel] [PATCH] qdev-monitor: Improve error message for -device nonexistant armbru
2013-12-19 15:48 ` Eric Blake
2013-12-20 11:13 ` Andreas Färber [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=52B4265C.5060803@suse.de \
--to=afaerber@suse.de \
--cc=aliguori@amazon.com \
--cc=armbru@redhat.com \
--cc=lcapitulino@redhat.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.