From: Anthony Liguori <anthony@codemonkey.ws>
To: Kevin Wolf <kwolf@redhat.com>
Cc: stefanha@gmail.com, qemu-devel@nongnu.org, lcapitulino@redhat.com
Subject: [Qemu-devel] Re: [PATCH 1/4] qerror: Add QERR_UNKNOWN_BLOCK_FORMAT_FEATURE
Date: Wed, 09 Feb 2011 05:28:55 -0600 [thread overview]
Message-ID: <4D527A77.8070306@codemonkey.ws> (raw)
In-Reply-To: <4D5279D3.4070702@redhat.com>
On 02/09/2011 05:26 AM, Kevin Wolf wrote:
> Am 09.02.2011 12:08, schrieb Anthony Liguori:
>
>> On 02/09/2011 04:31 AM, Kevin Wolf wrote:
>>
>>> Signed-off-by: Kevin Wolf<kwolf@redhat.com>
>>> ---
>>> qerror.c | 5 +++++
>>> qerror.h | 3 +++
>>> 2 files changed, 8 insertions(+), 0 deletions(-)
>>>
>>> diff --git a/qerror.c b/qerror.c
>>> index 9d0cdeb..62dcc1a 100644
>>> --- a/qerror.c
>>> +++ b/qerror.c
>>> @@ -201,6 +201,11 @@ static const QErrorStringTable qerror_table[] = {
>>> .desc = "An undefined error has ocurred",
>>> },
>>> {
>>> + .error_fmt = QERR_UNKNOWN_BLOCK_FORMAT_FEATURE,
>>> + .desc = "'%(device)' uses an image format feature which is not "
>>> + "supported by this qemu version: %(feature)",
>>> + },
>>> + {
>>> .error_fmt = QERR_VNC_SERVER_FAILED,
>>> .desc = "Could not start VNC server on %(target)",
>>> },
>>> diff --git a/qerror.h b/qerror.h
>>> index b0f69da..31d6df3 100644
>>> --- a/qerror.h
>>> +++ b/qerror.h
>>> @@ -165,6 +165,9 @@ QError *qobject_to_qerror(const QObject *obj);
>>> #define QERR_UNDEFINED_ERROR \
>>> "{ 'class': 'UndefinedError', 'data': {} }"
>>>
>>> +#define QERR_UNKNOWN_BLOCK_FORMAT_FEATURE \
>>> + "{ 'class': 'UnknownBlockFormatFeature', 'data': { 'device': %s, 'feature': %s } }"
>>>
>>>
>> Would be good to include the name of the block format in the error
>> message to put the feature in context.
>>
> I actually had the format name there initally, but then I replaced it
> with the device name because I thought that would be more helpful. If
> you prefer, I can add it back so that we have both.
>
Yes, I think both would be best.
If I'm going to display this error to a user, I want to say something
like "Could not start machine because this image uses the 'free list'
feature of 'qed' which is not supported by this version of QEMU, please
upgrade."
With the device name, I can do a query-block to figure out the format
but it's nice to avoid the extra round trip.
Regards,
Anthony Liguori
> Kevin
>
next prev parent reply other threads:[~2011-02-09 11:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-09 10:31 [Qemu-devel] [PATCH 0.14/master 0/4] Error messages for unsupoorted image format features Kevin Wolf
2011-02-09 10:31 ` [Qemu-devel] [PATCH 1/4] qerror: Add QERR_UNKNOWN_BLOCK_FORMAT_FEATURE Kevin Wolf
2011-02-09 11:08 ` [Qemu-devel] " Anthony Liguori
2011-02-09 11:26 ` Kevin Wolf
2011-02-09 11:28 ` Anthony Liguori [this message]
2011-02-09 10:31 ` [Qemu-devel] [PATCH 2/4] qcow2: Report error for version > 2 Kevin Wolf
2011-02-09 10:32 ` [Qemu-devel] [PATCH 3/4] qed: Report error for unsupported features Kevin Wolf
2011-02-09 11:20 ` [Qemu-devel] " Anthony Liguori
2011-02-09 11:21 ` Anthony Liguori
2011-02-09 11:29 ` Kevin Wolf
2011-02-09 11:29 ` Anthony Liguori
2011-02-09 12:09 ` Kevin Wolf
2011-02-09 10:32 ` [Qemu-devel] [PATCH 4/4] qemu-img: Improve error messages for failed bdrv_open Kevin Wolf
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=4D527A77.8070306@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=kwolf@redhat.com \
--cc=lcapitulino@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.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).