From: Olaf Hering <olaf@aepfle.de>
To: Ian.Jackson@eu.citrix.com, ian.campbell@citrix.com
Cc: xen-devel@lists.xen.org
Subject: libxl error reporting
Date: Thu, 6 Mar 2014 09:11:07 +0100 [thread overview]
Message-ID: <20140306081107.GA12445@aepfle.de> (raw)
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
next reply other threads:[~2014-03-06 8:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-06 8:11 Olaf Hering [this message]
2014-03-06 12:11 ` libxl error reporting Ian Jackson
2014-03-11 9:58 ` Ian Campbell
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=20140306081107.GA12445@aepfle.de \
--to=olaf@aepfle.de \
--cc=Ian.Jackson@eu.citrix.com \
--cc=ian.campbell@citrix.com \
--cc=xen-devel@lists.xen.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).