CentOS virt - Aug 2013 - messages logs flooded with xen_balloon: reserve_additional_memory: add_memory() failed

My /var/log/messages log is being flooded with kernel messages showing the
following messages

Aug  1 11:22:52 host43 kernel: System RAM resource 48000000 - 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_memory/xen_memory0/target_kb
1048576

Any ideas?

--
Shaun Reitan
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.centos.org/pipermail/centos-virt/attachments/20130801/a02531af/attachment-0006.html>

On 01/08/13 19:28, Shaun Reitan wrote:
> My /var/log/messages log is being flooded with kernel messages showing
> the following messages
>  
> Aug  1 11:22:52 host43 kernel: System RAM resource 48000000 - 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
> <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_memory/xen_memory0/target_kb
> 1048576
This should be fixed in the latest version of the kernel packages.
Which version are you using?

David