WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

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

To: Charles Arnold <carnold@xxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] Xen 4.0.1 "xc_map_foreign_batch: mmap failed: Cannot allocate memory"
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
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:user-agent:date :subject:from:to:message-id:thread-topic:thread-index:in-reply-to :mime-version:content-type:content-transfer-encoding; bh=eCdSJJTl6pKK8ctMgLJRN8w0P2rZupQU8oBofME5mYk=; b=ROW+3QkDwxBQ2wRA9+S4m8t9EqnfuQrqGe9dTmBIXI/WKhIbdjjmrNpP1fygp/LR4z p8ug9jB+WkuWRXdsIUtb6BLinB5qs54PPLu/Q1t8rOt8SCRyj80ewt1Yb5C2krZP/wN4 L8qyVxR2SicHqMl1p1UcLAe/Ima1d20GyroKQ=
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=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4D0A04C0020000910006885B@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcudYHvSRz7nJ+I/L0CzdlqSxEfGtQ==
Thread-topic: [Xen-devel] Xen 4.0.1 "xc_map_foreign_batch: mmap failed: Cannot allocate memory"
User-agent: Microsoft-Entourage/12.27.0.100910
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