From: Jan Beulich <jbeulich@suse.com>
To: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Cc: Ian Jackson <iwj@xenproject.org>, Wei Liu <wl@xen.org>,
Anthony Perard <anthony.perard@citrix.com>,
Andrew Cooper <andrew.cooper3@citrix.com>
Subject: [PATCH] libxl/x86: check return value of SHADOW_OP_SET_ALLOCATION domctl
Date: Mon, 28 Jun 2021 13:47:03 +0200 [thread overview]
Message-ID: <5d2bb2cf-8c0c-7300-c895-75bef0e50817@suse.com> (raw)
The hypervisor may not have enough memory to satisfy the request.
Requested-by: Andrew Cooper <andrew.cooper3@citrix.com>
Signed-off-by: Jan Beulich <jbeulich@suse.com>
---
Especially if the request was mostly fulfilled, guests may have done
fine despite the failure, so there is a risk of perceived regressions
here. But not checking the error at all was certainly wrong.
--- a/tools/libs/light/libxl_x86.c
+++ b/tools/libs/light/libxl_x86.c
@@ -531,8 +531,18 @@ int libxl__arch_domain_create(libxl__gc
if (d_config->b_info.type != LIBXL_DOMAIN_TYPE_PV) {
unsigned long shadow = DIV_ROUNDUP(d_config->b_info.shadow_memkb,
1024);
- xc_shadow_control(ctx->xch, domid, XEN_DOMCTL_SHADOW_OP_SET_ALLOCATION,
- NULL, 0, &shadow, 0, NULL);
+ int rc = xc_shadow_control(ctx->xch, domid,
+ XEN_DOMCTL_SHADOW_OP_SET_ALLOCATION,
+ NULL, 0, &shadow, 0, NULL);
+
+ if (rc) {
+ LOGED(ERROR, domid,
+ "Failed to set %s allocation: %d (errno:%d)\n",
+ libxl_defbool_val(d_config->c_info.hap) ? "HAP" : "shadow",
+ rc, errno);
+ ret = ERROR_FAIL;
+ goto out;
+ }
}
if (d_config->c_info.type == LIBXL_DOMAIN_TYPE_PV &&
next reply other threads:[~2021-06-28 11:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-28 11:47 Jan Beulich [this message]
2021-06-28 15:59 ` [PATCH] libxl/x86: check return value of SHADOW_OP_SET_ALLOCATION domctl Andrew Cooper
2021-07-01 9:36 ` Anthony PERARD
2021-07-02 12:29 ` Jan Beulich
2021-07-02 14:46 ` Anthony PERARD
2021-07-02 15:12 ` Jan Beulich
2021-07-02 15:14 ` Jan Beulich
2021-07-02 15:51 ` Anthony PERARD
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=5d2bb2cf-8c0c-7300-c895-75bef0e50817@suse.com \
--to=jbeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=anthony.perard@citrix.com \
--cc=iwj@xenproject.org \
--cc=wl@xen.org \
--cc=xen-devel@lists.xenproject.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).