[Top][All Lists]

[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: Luiz Capitulino
Subject: Re: [Qemu-devel] [RFC 00/14]: add printf-like human msg to error_set()
Date: Fri, 27 Jul 2012 11:27:29 -0300

On Fri, 27 Jul 2012 15:17:15 +0200
Andreas Färber <address@hidden> wrote:

> 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.

We don't send empty device IDs afaik, but that problem will have to be
discussed again... Why does libvirt need the QOM path from the error
message? Can't it be queried some other way?

reply via email to

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