Original report at
http://lists.xensource.com/archives/html/xen-users/2009-08/msg00136.html
Reproduced under Xen 3.4.0, 3.4.1, and xen-unstable, with various dom0
and domU kernels.
Possibly related to
http://lkml.indiana.edu/hypermail/linux/kernel/0802.2/0626.html , but
it occurs after a significant amount of memory usage, not at boot.
--
Time-sharing is the junk-mail part of the computer business.
--H.R.J. Grosch (attributed)
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
On 24/08/2009 18:30, "Paul Arthur" <flowerysong00@yahoo.com> wrote:> Original report at > http://lists.xensource.com/archives/html/xen-users/2009-08/msg00136.html > > Reproduced under Xen 3.4.0, 3.4.1, and xen-unstable, with various dom0 > and domU kernels. > > Possibly related to > http://lkml.indiana.edu/hypermail/linux/kernel/0802.2/0626.html , but > it occurs after a significant amount of memory usage, not at boot.So it''s a bug in a range of pv_ops-based kernels, you believe? -- Keir _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On 2009-08-24, Keir Fraser <keir.fraser@eu.citrix.com> wrote:> On 24/08/2009 18:30, "Paul Arthur" <flowerysong00@yahoo.com> wrote: > >> Original report at >> http://lists.xensource.com/archives/html/xen-users/2009-08/msg00136.html >> >> Reproduced under Xen 3.4.0, 3.4.1, and xen-unstable, with various dom0 >> and domU kernels. >> >> Possibly related to >> http://lkml.indiana.edu/hypermail/linux/kernel/0802.2/0626.html , but >> it occurs after a significant amount of memory usage, not at boot. > > So it''s a bug in a range of pv_ops-based kernels, you believe?It''s been encountered under the following domU kernels: Vanilla 2.6.29.6, 2.6.30, 2.6.30.4 2.6.18-xen from Mercurial. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On 2009-08-24, Paul Arthur <flowerysong00@yahoo.com> wrote:> On 2009-08-24, Keir Fraser <keir.fraser@eu.citrix.com> wrote: >> On 24/08/2009 18:30, "Paul Arthur" <flowerysong00@yahoo.com> wrote: >> >>> Original report at >>> http://lists.xensource.com/archives/html/xen-users/2009-08/msg00136.html >>> >>> Reproduced under Xen 3.4.0, 3.4.1, and xen-unstable, with various dom0 >>> and domU kernels. >>> >>> Possibly related to >>> http://lkml.indiana.edu/hypermail/linux/kernel/0802.2/0626.html , but >>> it occurs after a significant amount of memory usage, not at boot. >> >> So it''s a bug in a range of pv_ops-based kernels, you believe? > > It''s been encountered under the following domU kernels: > Vanilla 2.6.29.6, 2.6.30, 2.6.30.4 > 2.6.18-xen from Mercurial.dom0 kernels were: xen-tip/master 2.6.18-xen from Mercurial 2.6.29.6 w/patches from http://code.google.com/p/gentoo-xen-kernel/ -- Sailors in ships, sail on! Even while we died, others rode out the storm. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On 08/24/09 10:30, Paul Arthur wrote:> Original report at > http://lists.xensource.com/archives/html/xen-users/2009-08/msg00136.html > > Reproduced under Xen 3.4.0, 3.4.1, and xen-unstable, with various dom0 > and domU kernels. > > Possibly related to > http://lkml.indiana.edu/hypermail/linux/kernel/0802.2/0626.html , but > it occurs after a significant amount of memory usage, not at boot. > >Do you have CONFIG_HIGHPTE enabled? If so, disable it. J _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On 2009-08-24, Jeremy Fitzhardinge <jeremy@goop.org> wrote:> On 08/24/09 10:30, Paul Arthur wrote: >> Original report at >> http://lists.xensource.com/archives/html/xen-users/2009-08/msg00136.html >> >> Reproduced under Xen 3.4.0, 3.4.1, and xen-unstable, with various dom0 >> and domU kernels. >> >> Possibly related to >> http://lkml.indiana.edu/hypermail/linux/kernel/0802.2/0626.html , but >> it occurs after a significant amount of memory usage, not at boot. > > Do you have CONFIG_HIGHPTE enabled? If so, disable it.Thanks, this appears to have solved our stability issues. -- What I hit F to say, though, is that there''s more than one way to gain respect. When you''ve got a major nest of Monks by the upstream IP feed, their hearts and minds will follow. --AdB in ASR _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel