From: Wei Liu <wei.liu2@citrix.com>
To: Ian Campbell <ian.campbell@citrix.com>
Cc: wei.liu2@citrix.com, ian.jackson@eu.citrix.com, suse.dev@fea.st,
xen-devel@lists.xen.org
Subject: Re: [PATCH] tools/libxl: improve logging on domain create failure.
Date: Thu, 28 Jan 2016 10:52:33 +0000 [thread overview]
Message-ID: <20160128105233.GL25660@citrix.com> (raw)
In-Reply-To: <1453819126-10218-1-git-send-email-ian.campbell@citrix.com>
On Tue, Jan 26, 2016 at 02:38:46PM +0000, Ian Campbell wrote:
> A user reported[0] that xl create failed with just:
> libxl: error: libxl_create.c:892:initiate_domain_create: Unable to set domain build info defaults
> and some resulting fallout, but without indicating why it was unable
> to set the defaults, even in verbose mode[1].
>
> Go through libxl__domain_{create,build}_info_setdefault and ensure
> that each error path logs something.
>
> In most cases this involved simply adding a call to LOG.
>
> In two cases this involved switching from strdup to
> libxl__strdup(NOGC) and removing the existing error handling.
>
> When switching from qemu-xen to qemu-xen-traditional (because the
> former is not available) log at level INFO rather than VERBOSE, so
> the message would normally be printed. Also tweak the language here.
>
> I'm not sure all these messages are reachable (some might be shadowed
> by previous error paths) but it seems better to err on the side of
> caution.
>
> [0] http://lists.xen.org/archives/html/xen-users/2016-01/msg00125.html
> [1] http://lists.xen.org/archives/html/xen-users/2016-01/msg00129.html
>
> Signed-off-by: Ian Campbell <ian.campbell@citrix.com>
> Cc: suse.dev@fea.st
Acked-by: Wei Liu <wei.liu2@citrix.com>
next prev parent reply other threads:[~2016-01-28 10:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-26 14:38 [PATCH] tools/libxl: improve logging on domain create failure Ian Campbell
2016-01-28 10:52 ` Wei Liu [this message]
2016-02-03 11:50 ` 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=20160128105233.GL25660@citrix.com \
--to=wei.liu2@citrix.com \
--cc=ian.campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=suse.dev@fea.st \
--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).