search for: current_kb

...00000 - 4fffffff cannot be added Aug 1 11:22:52 host43 kernel: xen_balloon: reserve_additional_memory: add_memory() failed: ?17 Doing a search I found a thread from xen-devel that talks a bit about it. I?m not sure if this is related to the same issue or if that issue was ever fixed. When I cat current_kb and target_kb the values don?t match, they are just barely off. I have not tried setting them to match yet. http://marc.info/?t=135601508900004&r=1&w=3 [root at host ~]# cat /sys/devices/system/xen_memory/xen_memory0/info/current_kb 1048532 [root at host ~]# cat /sys/devices/system/xen_m...

...10.20-11.el6.centos.alt.x86_64 To replicate this just disable Dom0 memory ballooning in /etc/xen/xend-config.sxp and these errors will over time completely fill up dmesg. This is because the amount of memory within these two sys files is different: /sys/devices/system/xen_memory/xen_memory0/info/current_kb /sys/devices/system/xen_memory/xen_memory0/target_kb We can manually edit to work around the problem and stop the error but its not ideal, I would help with making a patch but don't really know where to start! Thanks Chris -------------- next part -------------- An HTML attachment was scrubb...

...try: for line in f: @@ -61,6 +63,29 @@ return None finally: f.close() + +def _linux_balloon_stat_sysfs(label): + sysfiles = { ''target'' : ''target_kb'', + ''current'' : ''info/current_kb'', + ''low-balloon'' : ''info/low_kb'', + ''high-balloon'' : ''info/high_kb'', + ''limit'' : ''info/hard_limit_kb'' } + + name = os.path...

Hi, I have encountered an apparently benign error on two systems where the dom0 kernel log is flooded with messages like: [52482.163855] System RAM resource [mem 0x1b8000000-0x1bfffffff] cannot be added [52482.163860] xen_balloon: reserve_additional_memory: add_memory() failed: -17 The first line is from drivers/xen/xen-balloon.c, the second from mm/memory_hotplug.c The trigger for the