From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: (XEN) page_alloc.c:1148:d0 Over-allocation for domain 0: 694017 > 694016 Date: Thu, 26 Apr 2012 22:34:39 -0400 Message-ID: <20120427023439.GB26931@phenom.dumpdata.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org I am not sure how this is happening, but I can only reproduce this is I use the "max" parameter in the 'dom0_mem=*:max:*' combination: sh-4.1# xl info | grep dom0_mem xen_commandline : cpuinfo dom0_mem=1G,max:2711M cpufreq=verbose com1=115200,8n1 console=com1,vga loglvl=all guest_loglvl= 02:32:22 # 19 :/sys/devices/system/xen_memory/xen_memory0/ > cat /proc/meminfo |grep Direct DirectMap4k: 2776516 kB DirectMap2M: 0 kB 02:33:11 # 23 :/sys/devices/system/xen_memory/xen_memory0/ > echo 2776516 > target_kb (XEN) page_alloc.c:1148:d0 Over-allocation for domain 0: 694017 > 694016 (XEN) memory.c:133:d0 Could not allocate order=0 extent: id=0 memflags=0 (239 of 256) (XEN) page_alloc.c:1148:d0 Over-allocation for domain 0: 694017 > 694016 (XEN) memory.c:133:d0 Could not allocate order=0 extent: id=0 memflags=0 (0 of 17) (XEN) page_alloc.c:1148:d0 Over-allocation for domain 0: 694017 > 694016 (XEN) memory.c:133:d0 Could not allocate order=0 extent: id=0 memflags=0 (0 of 17) > The value that it decided it was Ok with was: 2776510kB which is 6 pages short of the goal and that makes the messages disappear. Any ideas of what that might be? Could it be the shared_info, hypercall page, start_info, xenconsole and some other ones are the magic 6 pages which inhibit how much we can balloon up to?