* [Qemu-devel] backport c1d322e6048796296555dd36fdd102d7fa2f50bf to all stable trees
@ 2015-02-26 13:02 ` Stefano Stabellini
0 siblings, 0 replies; 8+ messages in thread
From: Stefano Stabellini @ 2015-02-26 13:02 UTC (permalink / raw)
To: qemu-stable; +Cc: xen-devel, qemu-devel, dslutz, Stefano Stabellini
Hi all,
I would like to request a backport of
commit c1d322e6048796296555dd36fdd102d7fa2f50bf
Author: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Date: Wed Dec 3 08:15:19 2014 -0500
xen-hvm: increase maxmem before calling xc_domain_populate_physmap
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
^ permalink raw reply [flat|nested] 8+ messages in thread
* backport c1d322e6048796296555dd36fdd102d7fa2f50bf to all stable trees
@ 2015-02-26 13:02 ` Stefano Stabellini
0 siblings, 0 replies; 8+ messages in thread
From: Stefano Stabellini @ 2015-02-26 13:02 UTC (permalink / raw)
To: qemu-stable; +Cc: xen-devel, qemu-devel, dslutz, Stefano Stabellini
Hi all,
I would like to request a backport of
commit c1d322e6048796296555dd36fdd102d7fa2f50bf
Author: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Date: Wed Dec 3 08:15:19 2014 -0500
xen-hvm: increase maxmem before calling xc_domain_populate_physmap
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
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [Qemu-devel] [Xen-devel] backport c1d322e6048796296555dd36fdd102d7fa2f50bf to all stable trees
2015-02-26 13:02 ` Stefano Stabellini
@ 2015-02-27 9:43 ` Fabio Fantoni
-1 siblings, 0 replies; 8+ messages in thread
From: Fabio Fantoni @ 2015-02-27 9:43 UTC (permalink / raw)
To: Stefano Stabellini, qemu-stable; +Cc: xen-devel, qemu-devel, dslutz
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@eu.citrix.com>
> 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.
>
> Thanks,
>
> Stefano
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [Xen-devel] backport c1d322e6048796296555dd36fdd102d7fa2f50bf to all stable trees
@ 2015-02-27 9:43 ` Fabio Fantoni
0 siblings, 0 replies; 8+ messages in thread
From: Fabio Fantoni @ 2015-02-27 9:43 UTC (permalink / raw)
To: Stefano Stabellini, qemu-stable; +Cc: xen-devel, qemu-devel, dslutz
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@eu.citrix.com>
> 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.
>
> Thanks,
>
> Stefano
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [Qemu-devel] [Xen-devel] backport c1d322e6048796296555dd36fdd102d7fa2f50bf to all stable trees
2015-02-27 9:43 ` Fabio Fantoni
@ 2015-02-27 11:24 ` Stefano Stabellini
-1 siblings, 0 replies; 8+ messages in thread
From: Stefano Stabellini @ 2015-02-27 11:24 UTC (permalink / raw)
To: Fabio Fantoni
Cc: qemu-devel, xen-devel, qemu-stable, dslutz, Stefano Stabellini
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 <stefano.stabellini@eu.citrix.com>
> > 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
pass soon.
> 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
revert c1d322e6048796296555dd36fdd102d7fa2f50bf
(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
> > Xen-devel@lists.xen.org
> > http://lists.xen.org/xen-devel
>
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [Xen-devel] backport c1d322e6048796296555dd36fdd102d7fa2f50bf to all stable trees
@ 2015-02-27 11:24 ` Stefano Stabellini
0 siblings, 0 replies; 8+ messages in thread
From: Stefano Stabellini @ 2015-02-27 11:24 UTC (permalink / raw)
To: Fabio Fantoni
Cc: qemu-devel, xen-devel, qemu-stable, dslutz, Stefano Stabellini
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 <stefano.stabellini@eu.citrix.com>
> > 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
pass soon.
> 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
revert c1d322e6048796296555dd36fdd102d7fa2f50bf
(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
> > Xen-devel@lists.xen.org
> > http://lists.xen.org/xen-devel
>
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [Qemu-devel] backport c1d322e6048796296555dd36fdd102d7fa2f50bf to all stable trees
2015-02-26 13:02 ` Stefano Stabellini
@ 2015-03-02 15:41 ` Stefano Stabellini
-1 siblings, 0 replies; 8+ messages in thread
From: Stefano Stabellini @ 2015-03-02 15:41 UTC (permalink / raw)
To: Stefano Stabellini; +Cc: xen-devel, qemu-stable, dslutz, qemu-devel
ping?
On Thu, 26 Feb 2015, Stefano Stabellini wrote:
> Hi all,
>
> I would like to request a backport of
>
> commit c1d322e6048796296555dd36fdd102d7fa2f50bf
> Author: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
> Date: Wed Dec 3 08:15:19 2014 -0500
>
> xen-hvm: increase maxmem before calling xc_domain_populate_physmap
>
>
> 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
>
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: backport c1d322e6048796296555dd36fdd102d7fa2f50bf to all stable trees
@ 2015-03-02 15:41 ` Stefano Stabellini
0 siblings, 0 replies; 8+ messages in thread
From: Stefano Stabellini @ 2015-03-02 15:41 UTC (permalink / raw)
To: Stefano Stabellini; +Cc: xen-devel, qemu-stable, dslutz, qemu-devel
ping?
On Thu, 26 Feb 2015, Stefano Stabellini wrote:
> Hi all,
>
> I would like to request a backport of
>
> commit c1d322e6048796296555dd36fdd102d7fa2f50bf
> Author: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
> Date: Wed Dec 3 08:15:19 2014 -0500
>
> xen-hvm: increase maxmem before calling xc_domain_populate_physmap
>
>
> 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
>
^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2015-03-02 15:43 UTC | newest]
Thread overview: 8+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2015-02-26 13:02 [Qemu-devel] backport c1d322e6048796296555dd36fdd102d7fa2f50bf to all stable trees Stefano Stabellini
2015-02-26 13:02 ` Stefano Stabellini
2015-02-27 9:43 ` [Qemu-devel] [Xen-devel] " Fabio Fantoni
2015-02-27 9:43 ` Fabio Fantoni
2015-02-27 11:24 ` [Qemu-devel] " Stefano Stabellini
2015-02-27 11:24 ` Stefano Stabellini
2015-03-02 15:41 ` [Qemu-devel] " Stefano Stabellini
2015-03-02 15:41 ` Stefano Stabellini
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.