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>
Subject: Re: [Xen-devel] Error reporting capabilities for libxc
From: "Daniel P. Berrange" <berrange@xxxxxxxxxx>
Date: Tue, 26 Sep 2006 14:18:22 +0100
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Tue, 26 Sep 2006 06:18:53 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <C13EDB85.1A47%Keir.Fraser@xxxxxxxxxxxx>
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>
References: <1159271107.7649.10.camel@xxxxxxxxxxxxxxxxxxxxx> <C13EDB85.1A47%Keir.Fraser@xxxxxxxxxxxx>
Reply-to: "Daniel P. Berrange" <berrange@xxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.4.1i
On Tue, Sep 26, 2006 at 01:28:37PM +0100, Keir Fraser wrote:
> 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'.

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

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

Xen-devel mailing list