From: "Daniel P. Berrange" <berrange@redhat.com>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: Error reporting capabilities for libxc
Date: Tue, 26 Sep 2006 14:18:22 +0100 [thread overview]
Message-ID: <20060926131822.GA8885@redhat.com> (raw)
In-Reply-To: <C13EDB85.1A47%Keir.Fraser@cl.cam.ac.uk>
On Tue, Sep 26, 2006 at 01:28:37PM +0100, Keir Fraser wrote:
>
>
>
> On 26/9/06 12:45, "Stephen C. Tweedie" <sct@redhat.com> wrote:
>
> >> So, I've prototyped a simple error reporting mechanism for libxc. The idea
> >> is we first define an enum for the broad classes of errors which can occur.
> > ...
> >
> >> Any way, the upshot of all this work:
> >> # xm create error
> >> Using config file "error".
> >> Error: [2, 'Kernel ELF architecture 3 does not match Xen architecture 62']
> >
> > IMHO this is sorely needed. Any comments from XenSource people?
>
> I'd agree something like this is necessary in the 3.0.4 timeframe. I'll let
> one of the guys more acquainted with xend comment in detail. There's also
> the question of how this will integrate with the proposed 'XenAPI'.
I don't anticipate any problems integrating with XenAPI - we've previously
discussed the need to enumerate a set of error codes for XenAPI operations
and the need to also pass back descriptive string of the problem so I should
think its a good fit
Regards,
Dan.
--
|=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=|
|=- Perl modules: http://search.cpan.org/~danberr/ -=|
|=- Projects: http://freshmeat.net/~danielpb/ -=|
|=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=|
next prev parent reply other threads:[~2006-09-26 13:18 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-22 20:31 Error reporting capabilities for libxc Daniel P. Berrange
2006-09-26 11:45 ` Stephen C. Tweedie
2006-09-26 12:28 ` Keir Fraser
2006-09-26 13:18 ` Daniel P. Berrange [this message]
2006-09-26 18:40 ` Hollis Blanchard
2006-09-26 18:49 ` Daniel P. Berrange
2006-09-26 21:37 ` Muli Ben-Yehuda
-- strict thread matches above, loose matches on Subject: below --
2006-09-26 12:58 Ian Pratt
2006-09-26 13:20 ` Daniel P. Berrange
2006-10-23 18:00 ` Daniel P. Berrange
2006-10-23 19:17 ` Anthony Liguori
2006-10-23 19:27 ` Daniel P. Berrange
2006-10-23 20:04 ` Anthony Liguori
2006-10-23 20:08 ` Daniel P. Berrange
2006-10-23 20:40 ` John Levon
2006-10-23 21:04 ` John Levon
2006-10-23 21:09 ` Daniel P. Berrange
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=20060926131822.GA8885@redhat.com \
--to=berrange@redhat.com \
--cc=Keir.Fraser@cl.cam.ac.uk \
--cc=xen-devel@lists.xensource.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 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.