On 2016-01-27 05:57, Ian Campbell wrote:
To summarise what I can tell from this bug log the following combinations
are/are not prone to this issue:
xen-??? xen-4.1 xen-4.4.1 4.4.1-9+deb8u3 xen-4.6.0
3.14.15-2 Y[1]
3.16.7-ckt7-1 N[1]
3.16.7-ckt9-3~deb8u1 Y[2]
3.16.7-ckt20-1+deb8u2 Y[3]
4.2.6-1 ?[1]
4.3.3-5 NN[1]
4.3.3-7 N[1]
[1] KSV
[2] ML (original report, Xen version unknown)
[3] AS (with dom0_mem=1024M,max:1024M, but not dom0_mem=1024M)
Although it may not add a lot to the situation at this point, you can add my configuration as being affected:
- kernel 3.16.7-ckt11-1+deb8u5 - Xen 4.4.1-9+deb8u2 - autoballoon="off" in xl.conf- GRUB_CMDLINE_XEN_DEFAULT="dom0_mem=2048M,max:2056M" (and also just "dom0_mem=2048M").
--
-Chad