[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [Xen-devel] backport c1d322e6048796296555dd36fdd102d7fa
Re: [Qemu-devel] [Xen-devel] backport c1d322e6048796296555dd36fdd102d7fa2f50bf to all stable trees
Fri, 27 Feb 2015 11:24:22 +0000
Alpine 2.02 (DEB 1266 2009-07-14)
On Fri, 27 Feb 2015, Fabio Fantoni wrote:
> 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 <address@hidden>
> > 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.
An unrelated local-migrate test is failing. It is believed to be due to
Paul's ioreq-server API changes and the fix should be in xen-unstable
already (the fix is a patch to the hypervisor). We expect the test to
> 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?
What exactly are you referring to?
Are you talking about http://marc.info/?l=xen-devel&m=142499350515886 ?
> 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.
It shouldn't have anything to do with "xen-hvm: increase maxmem before
calling xc_domain_populate_physmap". To make sure you could simply
(901230fd8ce053cc21312a2eca2f3ba9f1d103f2 in qemu-upstream-unstable.git)
and try again to see if the memory issues you are experiencing go away.
> > 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.
> > Thanks,
> > Stefano
> > _______________________________________________
> > Xen-devel mailing list
> > address@hidden
> > http://lists.xen.org/xen-devel