Jamie Lokier wrote:
Anthony Liguori wrote:
Markus Armbruster wrote:
3. It falls short of the requirement that clients can easily present a
  human-readable error description to their human users, regardless of
  whether they know the error or not.
That's just incorrect. We provide an example conversion table that's akin to strerror() or a __repr__ for an exception in Python.

Markus refers to errors that the client does not know - i.e. when the
client is older than qemu, or is not in the same development branch if
it's a branched qemu.  Which means the client won't have a fully up to
date conversion table.

Do you mean qemu provides it's current conversion table to the client
over the wire protocol?

(qemu) format_error "{'class': 'DeviceNotFound', 'data' : {'addr': '00:11:22'} }"
Device 0:11:22 is not present

Is what I'm thinking. I don't think it's needed but it solves the "problem".

Regards,

Anthony Liguori


Reply via email to