From: Daniel Veillard <veillard@redhat.com>
To: John Levon <levon@movementarian.org>
Cc: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>,
Anthony Liguori <aliguori@us.ibm.com>,
xen-devel@lists.xensource.com,
"Daniel P. Berrange" <berrange@redhat.com>
Subject: Re: Re: Error reporting capabilities for libxc
Date: Tue, 24 Oct 2006 05:15:04 -0400 [thread overview]
Message-ID: <20061024091504.GD19122@redhat.com> (raw)
In-Reply-To: <20061023214740.GA30872@totally.trollied.org>
On Mon, Oct 23, 2006 at 10:47:40PM +0100, John Levon wrote:
> On Mon, Oct 23, 2006 at 04:38:54PM -0500, Anthony Liguori wrote:
> > If a user passes an invalid kernel line in the config, I think an
> > appropriate error would be "Kernel <filename> is not a valid Xen kernel."
>
> Throwing away information on the error never seems like a good idea,
> especially when you consider, say, the Xen API. Logs are particular
> awkward when you're remotely managing a machine via a VM console. Even
> finding the right host machine could be frustrating enough.
I agree totally. You can have structured information where you need
it if reported at the API level. Saving in unstructured logs on the
managed machine is in general not very helpful.
Daniel
--
Red Hat Virtualization group http://redhat.com/virtualization/
Daniel Veillard | virtualization library http://libvirt.org/
veillard@redhat.com | libxml GNOME XML XSLT toolkit http://xmlsoft.org/
http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/
next prev parent reply other threads:[~2006-10-24 9:15 UTC|newest]
Thread overview: 25+ 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 [this message]
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
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=20061024091504.GD19122@redhat.com \
--to=veillard@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=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.