This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


RE: [Xen-devel] Error reporting capabilities for libxc

To: "Keir Fraser" <Keir.Fraser@xxxxxxxxxxxx>, "Stephen C. Tweedie" <sct@xxxxxxxxxx>, "Daniel P. Berrange" <berrange@xxxxxxxxxx>
Subject: RE: [Xen-devel] Error reporting capabilities for libxc
From: "Ian Pratt" <m+Ian.Pratt@xxxxxxxxxxxx>
Date: Tue, 26 Sep 2006 13:58:11 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 26 Sep 2006 06:00:50 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcbhZ0o8iKEnPk1aEduAkQAX8io7RQAA9TMg
Thread-topic: [Xen-devel] Error reporting capabilities for libxc
> On 26/9/06 12:45, "Stephen C. Tweedie" <sct@xxxxxxxxxx> 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'.

Yep, definitely needs to happen. However, I think we should at least
discuss alternative potentially less clunky implementation methods.
Perhaps we should use a thread local errno and error string variables?


Xen-devel mailing list