From: Ian Murray <murrayie@yahoo.co.uk>
To: xen-devel@lists.xen.org
Subject: Re: [PATCH v5 3/7] libxl/libxl_domain_info: Log if domain not found.
Date: Fri, 03 Apr 2015 23:12:15 +0100 [thread overview]
Message-ID: <551F103F.2000209@yahoo.co.uk> (raw)
In-Reply-To: <1428091354-6720-4-git-send-email-konrad.wilk@oracle.com>
On 03/04/15 21:02, Konrad Rzeszutek Wilk wrote:
> If we cannot find the domain - log an error (and still
> continue returning an error).
Forgive me if I am misunderstanding the effect of this patch (I tried to
find the original rationale but failed). If the effect is that commands
such as xl domid will cause a log entry when the specified domain
doesn't exist, I would suggest that's going to be a problem for people
that use that or similar commands to tell if a domain is present or
still alive. I use it as part of a back-up script to make sure a domain
shutdown before the script continues. I suspect many other people will
be doing something similar.
Apologies if I have the wrong end of the stick!
Thanks,
Ian.
>
> Signed-off-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
> Acked-by: Ian Campbell <ian.campbell@citrix.com>
> ---
> tools/libxl/libxl.c | 6 ++++--
> 1 file changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/tools/libxl/libxl.c b/tools/libxl/libxl.c
> index c0e9cfe..8753e27 100644
> --- a/tools/libxl/libxl.c
> +++ b/tools/libxl/libxl.c
> @@ -698,8 +698,10 @@ int libxl_domain_info(libxl_ctx *ctx, libxl_dominfo *info_r,
> LIBXL__LOG_ERRNO(ctx, LIBXL__LOG_ERROR, "getting domain info list");
> return ERROR_FAIL;
> }
> - if (ret==0 || xcinfo.domain != domid) return ERROR_DOMAIN_NOTFOUND;
> -
> + if (ret==0 || xcinfo.domain != domid) {
> + LIBXL__LOG_ERRNO(ctx, LIBXL__LOG_ERROR, "Domain %d not found!", domid);
> + return ERROR_DOMAIN_NOTFOUND;
> + }
> if (info_r)
> xcinfo2xlinfo(ctx, &xcinfo, info_r);
> return 0;
next prev parent reply other threads:[~2015-04-03 22:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-03 20:02 [PATCH v5] Fix xl vcpu-set to decrrease an guest vCPU amount without complaints Konrad Rzeszutek Wilk
2015-04-03 20:02 ` [PATCH v5 1/7] libxl: Add ERROR_DOMAIN_NOTFOUND for libxl_domain_info when it cannot find the domain Konrad Rzeszutek Wilk
2015-04-03 20:02 ` [PATCH v5 2/7] libxl: In libxl_set_vcpuonline check for maximum number of VCPUs against the cpumap Konrad Rzeszutek Wilk
2015-04-15 13:01 ` Ian Campbell
2015-04-03 20:02 ` [PATCH v5 3/7] libxl/libxl_domain_info: Log if domain not found Konrad Rzeszutek Wilk
2015-04-03 22:12 ` Ian Murray [this message]
2015-04-06 13:32 ` Konrad Rzeszutek Wilk
2015-04-15 13:03 ` Ian Campbell
2015-04-15 13:30 ` Ian Campbell
2015-04-15 13:56 ` Konrad Rzeszutek Wilk
2015-04-15 13:55 ` Konrad Rzeszutek Wilk
2015-04-03 20:02 ` [PATCH v5 4/7] libxl/vcpuset: Print error if libxl_set_vcpuonline returns ERROR_DOMAIN_NOTFOUND Konrad Rzeszutek Wilk
2015-04-03 20:02 ` [PATCH v5 5/7] libxl/vcpuset: Return error value if failed Konrad Rzeszutek Wilk
2015-04-03 20:02 ` [PATCH v5 6/7] libxl/vcpuset: Remove useless limit on max_vcpus Konrad Rzeszutek Wilk
2015-04-03 20:02 ` [PATCH v5 7/7] libxl/vcpu-set - allow to decrease vcpu count on overcommitted guests (v5) Konrad Rzeszutek Wilk
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=551F103F.2000209@yahoo.co.uk \
--to=murrayie@yahoo.co.uk \
--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 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.