[Xen-devel] Can't always start 32 bit domains after 64 bit domains

[Sarah Newman <srn@xxxxxxxxx>]

Last night on a 288GiB server with less than 64GiB of 32 bit
domUs, we used the standard xendomains script which starts VMs
in alphabetical order.

Some 32 bit domUs at the very end were unable to start. The
error message we received is the following:

xc: error: panic: xc_dom_x86.c:944: arch_setup_meminit: failed to allocate 
0x80000 pages: Internal error
xc: error: panic: xc_dom_boot.c:154: xc_dom_boot_mem_init: can't allocate low 
memory for domain: Out of memory
libxl: error: libxl_dom.c:719:libxl__build_pv: xc_dom_boot_mem_init failed: 
Device or resource busy
libxl: error: libxl_create.c:1144:domcreate_rebuild_done: cannot (re-)build 
domain: -3

After shutting down some 64 bit domUs, we could start the remainder
of the 32 bit domUs. Finally we started the rest of the 64 bit
domUs such that everything was booted.

My current understanding is that on a server with more than 168GiB
of memory, I should still be able to around 128GiB of 32-bit PV
domUs, regardless of what order the domUs are started in.

The version of xen we're using is Xen4CentOS 4.6.3-3.

The current workaround plan is to start all the 32-bit domUs
in smallest to largest order, and then all the 64 bit domUs in
smallest to largest order, but we are not 100% confident this will
work long term given it should have worked in the first place.

Is there any other information I can provide to help with duplicating the issue?

Please keep me CC'ed as I am not subscribed to xen-devel right now.

--Sarah

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