[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#784688: marked as done (Thousands of "xen:balloon: Cannot add additional memory (-17) messages" despite dom0 ballooning disabled)

Your message dated Sat, 08 May 2021 11:53:41 -0700 (PDT)
with message-id <6096de35.1c69fb81.f60a1.9a3f@mx.google.com>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #784688,
regarding Thousands of "xen:balloon: Cannot add additional memory (-17) messages" despite dom0 ballooning disabled
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
784688: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784688
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: linux-image-3.16.0-4-amd64
Version: 3.16.7-ckt9-3~deb8u1
Severity: normal

Dear maintainer,

my Xen dom0 is printing thousands of these messages to its logs:

# journalctl -b |grep "xen:balloon: Cannot add additional memory (-17)" | wc -l
126892
# uptime
 20:50:08 up 3 days,  8:28,  7 users,  load average: 0.21, 0.07, 0.06

The messages start occuring the first time I shutdown a domU. Due to using
this dom0 for Xen unikernel testing, such shutdowns are a common occurence.

Some shutdowns cause a few of these messages, some cause hundreds.

The dom0 has memory ballooning disabled:

# grep dom0_mem /etc/default/grub 
GRUB_CMDLINE_XEN="dom0_mem=4096M,max:4096M loglvl=info guest_loglvl=info"
# grep autoballoon /etc/xen/xl.conf 
autoballoon="0"

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

I am also including an excerpt from "xl dmesg", in case this helps:

(XEN) *** LOADING DOMAIN 0 ***
(XEN)  Xen  kernel: 64-bit, lsb, compat32
(XEN)  Dom0 kernel: 64-bit, PAE, lsb, paddr 0x1000000 -> 0x1f18000
(XEN) PHYSICAL MEMORY ARRANGEMENT:
(XEN)  Dom0 alloc.:   0000000814000000->0000000818000000 (1031107 pages to be allocated)
(XEN)  Init. ramdisk: 000000082fbc3000->000000082ffff212
(XEN) VIRTUAL MEMORY ARRANGEMENT:
(XEN)  Loaded kernel: ffffffff81000000->ffffffff81f18000
(XEN)  Init. ramdisk: ffffffff81f18000->ffffffff82354212
(XEN)  Phys-Mach map: ffffffff82355000->ffffffff82b55000
(XEN)  Start info:    ffffffff82b55000->ffffffff82b554b4
(XEN)  Page tables:   ffffffff82b56000->ffffffff82b6f000
(XEN)  Boot stack:    ffffffff82b6f000->ffffffff82b70000
(XEN)  TOTAL:         ffffffff80000000->ffffffff82c00000
(XEN)  ENTRY ADDRESS: ffffffff819021f0
(XEN) Dom0 has maximum 8 VCPUs

Bug #776448 claims to have fixed this problem, however it seems that the
fix is incomplete?

Thanks,

Martin

--- End Message ---
--- Begin Message --- 
Hi

This bug was filed for a very old kernel or the bug is old itself
without resolution.

If you can reproduce it with

- the current version in unstable/testing
- the latest kernel from backports

please reopen the bug, see https://www.debian.org/Bugs/server-control
for details.

Regards,
Salvatore

--- End Message ---
Reply to: