Re: [Xen-devel] [PATCH V3 1/1] libxl: set stub domain size based on VRAM size

[George Dunlap <George.Dunlap@xxxxxxxxxxxxx>]

On Sat, Jul 11, 2015 at 10:30 PM, Eric Shelton <eshelton@xxxxxxxxx> wrote:
> Allocate additional memory to the stub domain for qemu-traditional if
> more than 4 MB is assigned to the video adapter to avoid out of memory
> condition for QEMU.
>
> Signed-off-by: Eric Shelton <eshelton@xxxxxxxxx>

This seems like a good fix for now, thanks.

But (just speaking to people in general) it does make it even harder
to predict exactly how much host memory a VM is going to end up
needing to start, which is something a lot of people complain about.

I'm beginning to think that one feature we should try to look at is a
way for the admin to specify, "Max host memory used", from which
shadow/p2m/device memory/stubdomain can all be "allocated".

 -George

> ---
>  tools/libxl/libxl_dm.c | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/tools/libxl/libxl_dm.c b/tools/libxl/libxl_dm.c
> index 317a8eb..9a5a937 100644
> --- a/tools/libxl/libxl_dm.c
> +++ b/tools/libxl/libxl_dm.c
> @@ -1087,6 +1087,7 @@ void libxl__spawn_stub_dm(libxl__egc *egc, 
> libxl__stub_dm_spawn_state *sdss)
>
>      dm_config->b_info.max_vcpus = 1;
> -    dm_config->b_info.max_memkb = 32 * 1024;
> +    dm_config->b_info.max_memkb = 28 * 1024 +
> +        guest_config->b_info.video_memkb;
>      dm_config->b_info.target_memkb = dm_config->b_info.max_memkb;
>
>      dm_config->b_info.u.pv.features = "";
> --
> 2.1.0
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxx
> http://lists.xen.org/xen-devel

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