From mboxrd@z Thu Jan  1 00:00:00 1970
From: Keir Fraser <keir@xen.org>
Subject: Re: Xen 4.0.1 "xc_map_foreign_batch: mmap failed: Cannot
	allocate memory"
Date: Thu, 16 Dec 2010 20:33:23 +0000
Message-ID: <C9302813.2966F%keir@xen.org>
References: <4D0A04C0020000910006885B@novprvoes0310.provo.novell.com>
Mime-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <4D0A04C0020000910006885B@novprvoes0310.provo.novell.com>
List-Unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: Charles Arnold <carnold@novell.com>, xen-devel@lists.xensource.com
List-Id: xen-devel@lists.xenproject.org

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