From: "Daniel P. Berrange" <berrange@redhat.com>
To: John Levon <levon@movementarian.org>
Cc: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>, xen-devel@lists.xensource.com
Subject: Re: Error reporting capabilities for libxc
Date: Mon, 23 Oct 2006 22:09:38 +0100 [thread overview]
Message-ID: <20061023210938.GJ25795@redhat.com> (raw)
In-Reply-To: <20061023210459.GA29777@totally.trollied.org>
On Mon, Oct 23, 2006 at 10:04:59PM +0100, John Levon wrote:
> On Mon, Oct 23, 2006 at 07:00:17PM +0100, Daniel P. Berrange wrote:
>
> > Attached is an update to the original patch which annotates the static
> > variables with __thread so that they are setup per-thread. It also adds
> > more informative error reporting for bad kernels.
>
> It needs merging with latest tip I think. xc_private.h is missing a
> prototype for xc_set_error(), so it doesn't compile. Also it
> re-introduces ERR(), which causes problems for us, and can just be
> removed.
Ah yes, I hadn't noticed there were xen-unstable changes in this area. I
did the patch against 3.0.3 final release. I'll rebase to xen-unstable
before posting again.
> I fixed these two problems and did some simple tests on Solaris; all
> seems OK:
>
> bash-3.00# xm create -c johnlev-64.py
> Using config file "johnlev-64.py".
> Error: [2, 'Invalid kernel', "Kernel ELF architecture '62' does not match Xen architecture '3' (i386)"]
>
> (It's so wonderful to get a meaningful error message at last!!)
Thats good news, thanks for testing it.
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-10-23 21:09 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-26 12:58 Error reporting capabilities for libxc 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:54 ` Ian Pratt
2006-10-23 20:57 ` Daniel P. Berrange
2006-10-23 21:10 ` Ian Pratt
2006-10-23 21:14 ` Anthony Liguori
2006-10-23 21:28 ` Daniel P. Berrange
2006-10-23 21:38 ` Anthony Liguori
2006-10-23 21:47 ` John Levon
2006-10-24 9:15 ` Daniel Veillard
2006-10-23 21:48 ` Daniel P. Berrange
2006-10-24 7:47 ` Gerd Hoffmann
2006-10-24 9:07 ` Keir Fraser
2006-10-24 10:26 ` Gerd Hoffmann
2006-10-23 21:21 ` Daniel P. Berrange
2006-10-23 22:15 ` Ian Pratt
2006-10-23 23:05 ` 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 [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-09-22 20:31 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
2006-09-26 18:40 ` Hollis Blanchard
2006-09-26 18:49 ` Daniel P. Berrange
2006-09-26 21:37 ` Muli Ben-Yehuda
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=20061023210938.GJ25795@redhat.com \
--to=berrange@redhat.com \
--cc=levon@movementarian.org \
--cc=m+Ian.Pratt@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.