From: Keir Fraser <keir@xen.org>
To: Charles Arnold <carnold@novell.com>, xen-devel@lists.xensource.com
Subject: Re: Xen 4.0.1 "xc_map_foreign_batch: mmap failed: Cannot allocate memory"
Date: Thu, 16 Dec 2010 20:33:23 +0000 [thread overview]
Message-ID: <C9302813.2966F%keir@xen.org> (raw)
In-Reply-To: <4D0A04C0020000910006885B@novprvoes0310.provo.novell.com>
On 16/12/2010 19:23, "Charles Arnold" <carnold@novell.com> wrote:
> The bug is that qemu-dm seems to make the assumption that it can mmap from
> dom0 all the memory with which the guest has been defined instead of the
> memory
> that is actually available on the host.
32-bit dom0? Hm, I thought the qemu mapcache was supposed to limit the total
amount of guest memory mapped at one time, for a 32-bit qemu. For 64-bit
qemu I wouldn't expect to find a limit as low as 3.25G.
-- Keir
next prev parent reply other threads:[~2010-12-16 20:33 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-16 19:23 Xen 4.0.1 "xc_map_foreign_batch: mmap failed: Cannot allocate memory" Charles Arnold
2010-12-16 20:33 ` Keir Fraser [this message]
2010-12-16 20:44 ` Charles Arnold
2010-12-16 20:54 ` Keir Fraser
2010-12-17 9:22 ` Jan Beulich
2010-12-17 10:06 ` Keir Fraser
2011-01-05 14:37 ` Stefano Stabellini
2011-01-05 15:30 ` Jan Beulich
2011-01-05 16:22 ` Stefano Stabellini
2011-01-05 16:33 ` Jan Beulich
2011-01-05 17:48 ` Stefano Stabellini
2011-01-05 18:09 ` Jan Beulich
2011-01-05 17:17 ` Charles Arnold
2011-01-06 16:50 ` Stefano Stabellini
2011-01-06 17:14 ` Charles Arnold
-- strict thread matches above, loose matches on Subject: below --
2011-01-05 18:10 Jan Beulich
2011-01-06 20:49 Charles Arnold
2011-01-07 9:35 Jan Beulich
2011-01-07 11:18 ` Stefano Stabellini
2011-01-07 12:37 ` Jan Beulich
2011-01-10 11:11 ` Stefano Stabellini
2011-01-07 17:03 ` Charles Arnold
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=C9302813.2966F%keir@xen.org \
--to=keir@xen.org \
--cc=carnold@novell.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).