From mboxrd@z Thu Jan  1 00:00:00 1970
From: Daniel Veillard <veillard@redhat.com>
Subject: Re: Re: Error reporting capabilities for libxc
Date: Tue, 24 Oct 2006 05:15:04 -0400
Message-ID: <20061024091504.GD19122@redhat.com>
References: <453D1554.8000202@us.ibm.com> <20061023192753.GG25795@redhat.com>
	<3AAA99889D105740BE010EB6D5A5A3B205073B@paddington.ad.cl.cam.ac.uk>
	<20061023205730.GI25795@redhat.com>
	<3AAA99889D105740BE010EB6D5A5A3B205073C@paddington.ad.cl.cam.ac.uk>
	<453D30D3.6090007@us.ibm.com> <20061023212802.GL25795@redhat.com>
	<453D366E.5020201@us.ibm.com>
	<20061023214740.GA30872@totally.trollied.org>
Reply-To: veillard@redhat.com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Return-path: <xen-devel-bounces@lists.xensource.com>
Content-Disposition: inline
In-Reply-To: <20061023214740.GA30872@totally.trollied.org>
List-Unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.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>
List-Id: xen-devel@lists.xenproject.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/