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

Re: [Xen-devel] backport c1d322e6048796296555dd36fdd102d7fa2f50bf to all stable trees

Il 26/02/2015 14:02, Stefano Stabellini ha scritto:
Hi all,

I would like to request a backport of

commit c1d322e6048796296555dd36fdd102d7fa2f50bf
Author: Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>
Date:   Wed Dec 3 08:15:19 2014 -0500

     xen-hvm: increase maxmem before calling xc_domain_populate_physmap

Seems that this fixes is applied only in staging/qemu-upstream-unstable.git (of xen's gits) but still not in qemu-upstream-unstable.git or stables ones. Can be the cause of strange problem of "loop" of increase memory failing on hvm domUs start with xen 4.4, 4.5 and unstable with newer kernel even if domUs and dom0 have all fixed memory settings with balloning disabled?
Or is another memory bug in xen?
I have syslog and kern.log increasing some gb each days full of:
xen:balloon: reserve_additional_memory: add_memory() failed: -17
in one 4.5.0 dom0 also with kernel 3.16.7-ckt4-3~bpo70+1 with these applied: [xen] cancel ballooning if adding new memory failed (Closes: #776448)

Thanks for any reply and sorry for my bad english.

to all QEMU stable trees. Which ones are the currently maintained trees?

It applies without issues to 2.2, 2.1, 2.0, 1.7, 1.6, 1.5.
The filename in the commit needs to be changed from xen-hvm.c to
xen-all.c for 1.4, 1.3, 1.2, 1.1.  I didn't go father back.



Xen-devel mailing list

Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.