As far I understand second part of bugreport describes problems that leads to some inconvenient and doubtful messages during creating/rebooting domU's when memory balloning is disabled, but aren't very grave in general (although patches are available in Debian repository - as specific for glibc they are not pushed upstream, I suppose).
In general, where balloning is disabled, kernel complains few (about twenty, to be honest) times during creating/restarting domU:
xen:balloon: Cannot add additional memory (-17)
Enabling balloning, for example by dom0_mem=1536M,max:2048M "fixes" problem, although it is may be troublesome in environments with very small memory amount assigned to dom0 (as stated in mentioned thread in Debian's bugzilla).
Problems described in first parts of Debian's bug report was gone after update, although a problem with "pseudo-leak", explained in https:/ /bugs.debian. org/cgi- bin/bugreport. cgi?bug= 767295# 75 (and few following messages) still exists.
As far I understand second part of bugreport describes problems that leads to some inconvenient and doubtful messages during creating/rebooting domU's when memory balloning is disabled, but aren't very grave in general (although patches are available in Debian repository - as specific for glibc they are not pushed upstream, I suppose).
In general, where balloning is disabled, kernel complains few (about twenty, to be honest) times during creating/restarting domU:
xen:balloon: Cannot add additional memory (-17)
Enabling balloning, for example by dom0_mem= 1536M,max: 2048M "fixes" problem, although it is may be troublesome in environments with very small memory amount assigned to dom0 (as stated in mentioned thread in Debian's bugzilla).