qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [RFC 00/14]: add printf-like human msg to error_set()


From: Anthony Liguori
Subject: Re: [Qemu-devel] [RFC 00/14]: add printf-like human msg to error_set()
Date: Fri, 27 Jul 2012 08:45:51 -0500
User-agent: Notmuch/0.13.2+93~ged93d79 (http://notmuchmail.org) Emacs/23.3.1 (x86_64-pc-linux-gnu)

Andreas Färber <address@hidden> writes:

> Am 26.07.2012 18:37, schrieb Luiz Capitulino:
>> On Thu, 26 Jul 2012 18:03:20 +0200
>> Paolo Bonzini <address@hidden> wrote:
>> 
>>> Il 26/07/2012 17:54, Markus Armbruster ha scritto:
>>>> Unlike Anthony, I think this is a move in the right direction.
>>>
>>> Me too, but I would like to understand how it fits with the
>>> qapi-schema-errors.json.  Do we actually need a schema if the messages
>>> are flat?
>> 
>> Yes, we need it because we still an error object to obey (ie. the data 
>> member).
>> 
>> But we're talking about dropping that, so it might be possible to kill
>> the schema.
>
> I'm not so familiar with how all this error infrastructure is plugged
> together...
>
> In a different thread that I mentioned recently (and still haven't found
> in my inbox), we were talking about changing the JSON encoding of errors
> where unused by libvirt. Specifically we were talking about having a
> field for the canonical QOM path of the affected object in place of the
> often-empty device ID.
>
> Are you now discussing to drop any such elaborated QMP schemes in place
> of just one non-parsable human error message string?

See the other note I sent out for a description of the plan.  It's
english string + error code.

Regards,

Anthony Liguori

>
> Andreas
>
> -- 
> SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
> GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg




reply via email to

[Prev in Thread] Current Thread [Next in Thread]