Bug#784688: Thousands of "xen:balloon: Cannot add additional memory (-17) messages" despite dom0 ballooning disabled
On Sun, 2015-05-17 at 15:14 +0100, Ian Campbell wrote:
> On Thu, 2015-05-07 at 21:02 +0200, Martin Lucina wrote:
> > Note that despite the memory setting above, the dom0 has not been allocated
> > exactly the amount asked for:
> >
> > # xl list 0
> > Name ID Mem VCPUs State Time(s)
> > Domain-0 0 4051 8 r----- 5606.1
>
> Could you also post the output of "xenstore-ls -fp | grep target"
> please.
>
> You should have a directory /sys/devices/system/xen_memory/xen_memory0.
> Please could you post the contents of each of the files in there. In
> particular target*, *retry_count and info/*.
>
> It might also be interesting to see the result of "xl debug-keys q"
> followed by "xl dmesg".
>
> Does "xl mem-set 0 4051" make the messages stop? If not what about using
> 4050?
>
> If you try and balloon up to 4096 (with xl mem-set) does the amount of
> memory in xl list change?
One last thing... If you are able to try it then it would be interesting
to know if the 4.0.x kernel from sid exhibits this behaviour too.
Cheers,
Ian.
Reply to: