Re: [Xen-devel] [PATCH V3 1/5] libxl: bump LIBXL_MAXMEM_CONSTANT to 2048

[Wei Liu <wei.liu2@xxxxxxxxxx>]

On Tue, Oct 29, 2013 at 11:39:47AM +0000, 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.
> 
> Changing this constant doesn't necessary increase the total amount of
> memory a guest uses because it's just a limit.
> 
> Signed-off-by: Wei Liu <wei.liu2@xxxxxxxxxx>
> Cc: Ian Campbell <ian.campbell@xxxxxxxxxx>
> Cc: Ian Jackson <ian.jackson@xxxxxxxxxxxxx>
> ---
>  tools/libxl/libxl_internal.h |    2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/tools/libxl/libxl_internal.h b/tools/libxl/libxl_internal.h
> index 165dc00..908af20 100644
> --- a/tools/libxl/libxl_internal.h
> +++ b/tools/libxl/libxl_internal.h
> @@ -87,7 +87,7 @@
>  #define LIBXL_QEMU_BODGE_TIMEOUT 2
>  #define LIBXL_XENCONSOLE_LIMIT 1048576
>  #define LIBXL_XENCONSOLE_PROTOCOL "vt100"
> -#define LIBXL_MAXMEM_CONSTANT 1024
> +#define LIBXL_MAXMEM_CONSTANT 2048
>  #define LIBXL_PV_EXTRA_MEMORY 1024
>  #define LIBXL_HVM_EXTRA_MEMORY 2048
>  #define LIBXL_MIN_DOM0_MEM (128*1024)
> -- 

Actually those messages are debug only, so this patch is not necessary.

Please drop this one.


Wei.

> 1.7.10.4

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel