Re: [Xen-users] ballon memory error message

[James Dingwall <james@xxxxxxxxxxxxxx>]

On Tue, Dec 23, 2014 at 12:17:42AM +0000, Mark Pryor wrote:
> add 16MB per VM to dom0 Max Memory, like this for 6 auto-started VM on xen.gz 
> cmdline:dom0_mem=512M,max:608M
> No more balloon warnings.

I think that works until the next time you restart the vm.  I can suppress the 
warning with the script below 
until after I reboot the guest domain at which point it starts again so I 
thought this was actually a leak in 
the kernel code.  However it seems that 3.18 has solved this and some other 
ballooning problems I was 
having with tmem.

#!/bin/sh

# This contains the current size of the dom0 memory allocation
CURRENT_KB="/sys/bus/xen_memory/devices/xen_memory0/info/current_kb"
# This contains the target value for the dom0 memory allocation
TARGET_KB="/sys/bus/xen_memory/devices/xen_memory0/target_kb"

# Read the current values
CKB=$(< "${CURRENT_KB}")
TKB=$(< "${TARGET_KB}")

if [ "${TKB}" -gt "${CKB}" ] ; then
        echo "Resizing dom0 memory balloon target to ${CKB}"
        echo "${CKB}" > "${TARGET_KB}"
fi

James

>  
> 
>      On Monday, December 22, 2014 1:16 PM, Greg Woods <woods@xxxxxxxx> wrote:
>    
> 
>  I sometimes see this in /var/log/messages:
> 
> Dec 21 03:17:01 vmx1 kernel: System RAM resource [mem 
> 0x108000000-0x10fffffff] cannot be addedDec 21 03:17:01 vmx1 kernel: 
> xen_balloon: reserve_additional_memory: add_memory() failed: -17
> Does this mean Dom0 is out of memory? Or a DomU is out of memory? 
> How serious a problem is this? Would increasing dom0_mem on the kernel boot 
> line help?
> 
> Thanks,--Greg

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