[Top] [All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] Xen 4.0.1 "xc_map_foreign_batch: mmap failed: Cannot allocate memory"

  • To: Charles Arnold <carnold@xxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: Keir Fraser <keir@xxxxxxx>
  • Date: Thu, 16 Dec 2010 20:33:23 +0000
  • Cc:
  • Delivery-date: Thu, 16 Dec 2010 12:34:14 -0800
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:user-agent:date:subject:from:to:message-id:thread-topic :thread-index:in-reply-to:mime-version:content-type :content-transfer-encoding; b=DCBBt8fnq1G35asPXIPXnV2MvnkyXGl0fqzA7jDR/QQI+/d2U4rMV+ofPq0OeWmpmT 3teuqSOMzJe5gppVIae6/gP5xiSEhCEyFES/TGPs058VNYwmbcNLuAeC39GFhCAy5XW4 e4vSplU6MdL2KgM6V4WlYRTxLizj2qeTAbF80=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AcudYHvSRz7nJ+I/L0CzdlqSxEfGtQ==
  • Thread-topic: [Xen-devel] Xen 4.0.1 "xc_map_foreign_batch: mmap failed: Cannot allocate memory"
On 16/12/2010 19:23, "Charles Arnold" <carnold@xxxxxxxxxx> 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



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

 

©2013 Xen Project, A Linux Foundation Collaborative Project. All Rights Reserved.
Linux Foundation is a registered trademark of The Linux Foundation.
Xen Project is a trademark of The Linux Foundation.

Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.