From mboxrd@z Thu Jan  1 00:00:00 1970
From: Olaf Hering <olaf@aepfle.de>
Subject: libxl error reporting
Date: Thu, 6 Mar 2014 09:11:07 +0100
Message-ID: <20140306081107.GA12445@aepfle.de>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xen.org>
Content-Disposition: inline
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: Ian.Jackson@eu.citrix.com, ian.campbell@citrix.com
Cc: xen-devel@lists.xen.org
List-Id: xen-devel@lists.xenproject.org


How are users of libxl supposed to report errors that occour during an
libxl function call?

For example "virsh migrate" calls libxl_domain_suspend, which has many
ways to fail. What details about the specific error should be returned
to the caller? Right now its just some sort of libxl_error. All virsh
could do is to show "please see logfile for details".

I think this specifc function should return some sort of state, which is
preserved within the function call. It could be something like "remote
side had issues", "guest was too busy", "guest lacks PV drivers", "some
unexpected (internal) error".

Unfortunately libxl.h contains nothing about error handling.


Olaf