From mboxrd@z Thu Jan 1 00:00:00 1970 From: Wei Liu Subject: Re: [PATCH 1/4] libxl: bump LIBXL_MAXMEM_CONSTANT to 2048 Date: Tue, 29 Oct 2013 12:15:13 +0000 Message-ID: <20131029121513.GE5221@zion.uk.xensource.com> References: <1381855205-3329-1-git-send-email-wei.liu2@citrix.com> <1381855205-3329-2-git-send-email-wei.liu2@citrix.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: George Dunlap Cc: Ian Jackson , Wei Liu , Ian Campbell , "xen-devel@lists.xen.org" List-Id: xen-devel@lists.xenproject.org On Tue, Oct 29, 2013 at 12:03:25PM +0000, George Dunlap wrote: > On Tue, Oct 15, 2013 at 5:40 PM, Wei Liu wrote: > > When using OVMF we need to have 1MiB of memory in place for firmware. > > Without this change we have: > > > > (XEN) HVM128: Loading OVMF ... > > (XEN) page_alloc.c:1460:d128 Over-allocation for domain 128: 33025 > 33024 > > (XEN) memory.c:132:d128 Could not allocate order=0 extent: id=128 memflags=0 (0 of 1) > > > > This is not a fatal error as hvmloader will instead use low memory to > > load OVMF, but it's better to eliminate such error. > > Wait -- hvmloader is actually allocating memory from Xen to load > firmware stuff like this? > > That seems a bit weird... shouldn't it just use the memory it already > has, instead of asking for more? > See hvmloader/util.c:mem_hole_populate_ram(). It's used in building ACPI info area and allocating ram to load OVMF firmware volume. Are you suggesting we change the behavior of hvmloader? Wei. > -George