From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
qemu-devel@nongnu.org
Cc: xen-devel@lists.xensource.com,
"Wei Liu (Intern)" <wei.liu2@citrix.com>,
Ian Campbell <Ian.Campbell@citrix.com>
Subject: Re: [Qemu-devel] [Xen-devel] [PATCH] increase maxmem before calling xc_domain_populate_physmap
Date: Tue, 25 Nov 2014 18:24:42 +0000 [thread overview]
Message-ID: <5474C96A.6090506@citrix.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1411251742280.14135@kaball.uk.xensource.com>
On 25/11/14 17:45, Stefano Stabellini wrote:
> Increase maxmem before calling xc_domain_populate_physmap_exact to avoid
> the risk of running out of guest memory. This way we can also avoid
> complex memory calculations in libxl at domain construction time.
>
> This patch fixes an abort() when assigning more than 4 NICs to a VM.
>
> Signed-off-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
>
> diff --git a/xen-hvm.c b/xen-hvm.c
> index 5c69a8d..38e08c3 100644
> --- a/xen-hvm.c
> +++ b/xen-hvm.c
> @@ -218,6 +218,7 @@ void xen_ram_alloc(ram_addr_t ram_addr, ram_addr_t size, MemoryRegion *mr)
> unsigned long nr_pfn;
> xen_pfn_t *pfn_list;
> int i;
> + xc_dominfo_t info;
>
> if (runstate_check(RUN_STATE_INMIGRATE)) {
> /* RAM already populated in Xen */
> @@ -240,6 +241,13 @@ void xen_ram_alloc(ram_addr_t ram_addr, ram_addr_t size, MemoryRegion *mr)
> pfn_list[i] = (ram_addr >> TARGET_PAGE_BITS) + i;
> }
>
> + if (xc_domain_getinfo(xen_xc, xen_domid, 1, &info) < 0) {
xc_domain_getinfo()'s interface is mad, and provides no guarantee that
it returns the information for the domain you requested. It also won't
return -1 on error. The correct error handing is:
(xc_domain_getinfo(xen_xc, xen_domid, 1, &info) != 1) || (info.domid !=
xen_domid)
~Andrew
> + hw_error("xc_domain_getinfo failed");
> + }
> + if (xc_domain_setmaxmem(xen_xc, xen_domid, info.max_memkb +
> + (nr_pfn * XC_PAGE_SIZE / 1024)) < 0) {
> + hw_error("xc_domain_setmaxmem failed");
> + }
> if (xc_domain_populate_physmap_exact(xen_xc, xen_domid, nr_pfn, 0, 0, pfn_list)) {
> hw_error("xen: failed to populate ram at " RAM_ADDR_FMT, ram_addr);
> }
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2014-11-25 18:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-25 17:45 [Qemu-devel] [PATCH] increase maxmem before calling xc_domain_populate_physmap Stefano Stabellini
2014-11-25 18:24 ` Andrew Cooper [this message]
2014-11-26 18:17 ` [Qemu-devel] [Xen-devel] " Stefano Stabellini
2014-11-27 2:42 ` Don Slutz
2014-11-27 10:48 ` Stefano Stabellini
2014-12-01 13:33 ` Don Slutz
2014-12-01 15:37 ` Stefano Stabellini
2014-12-01 23:16 ` Don Slutz
2014-12-02 12:26 ` Stefano Stabellini
2014-12-02 20:23 ` Don Slutz
2014-12-03 10:54 ` Wei Liu
2014-12-03 12:20 ` Stefano Stabellini
2014-12-03 13:39 ` Don Slutz
2014-12-03 14:50 ` Stefano Stabellini
2014-12-04 16:26 ` Don Slutz
2014-12-04 16:38 ` Wei Liu
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=5474C96A.6090506@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=qemu-devel@nongnu.org \
--cc=stefano.stabellini@eu.citrix.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xensource.com \
/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).