From: Andreas Kinzler <ml-xen-devel@hfp.de>
To: Roderick Colenbrander <thunderbird2k@gmail.com>,
xen-devel@lists.xensource.com
Subject: Re: Questions about GPLPV stability tests
Date: Tue, 29 Nov 2011 18:12:49 +0100 [thread overview]
Message-ID: <4ED51291.1010308@hfp.de> (raw)
In-Reply-To: <CAEc3jaBds7xmiKH8RMfmEHQumkEeZ3PopVfbZPs_B-Kz8-DsWw@mail.gmail.com>
On 29.11.2011 16:48, Roderick Colenbrander wrote:
> Your tests are heavily stressing DomU. During any of your tests, have
> you seen DomU crashing in such a nasty way that Dom0 went down? What
> about in production? Our servers use similar software to you
> (initially Xen 4.0.1, but now Xen 4.1.1 and a Linux 2.6.32-pvops
> kernel), but a few percent of our servers go down in a very nasty way
> every day. Dom0 becomes unresponsive, it feels it 'hung' and we have
> to force reboot the boxes. Do issues like this sound familiar?
Not in this year of my stability tests. In this year I am always
experiencing crashes of domU only. dom0 was always stable.
But last year, I hunted a very serious problem which causes nasty
hangs/crashes in dom0 (which crashes domU as a consequence). See this
mailing list post:
http://lists.xen.org/archives/html/xen-devel/2010-09/msg00556.html
In my tests it clearly shows that if you have a CPU without ARAT and you
don't have the patch from my post, your Xen 4.0.1 or 4.1.1 will crash
under load and/or after a while. What is your CPU?
Regards Andreas
next parent reply other threads:[~2011-11-29 17:12 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAEc3jaBds7xmiKH8RMfmEHQumkEeZ3PopVfbZPs_B-Kz8-DsWw@mail.gmail.com>
2011-11-29 17:12 ` Andreas Kinzler [this message]
2011-11-29 18:04 ` Questions about GPLPV stability tests Roderick Colenbrander
2011-11-29 18:15 ` Andreas Kinzler
2011-11-29 18:21 ` Roderick Colenbrander
2011-11-30 13:11 ` Andreas Kinzler
2011-11-29 23:02 ` Konrad Rzeszutek Wilk
2011-11-30 0:01 ` Roderick Colenbrander
2011-12-06 19:12 ` Roderick Colenbrander
2011-12-07 20:38 ` Konrad Rzeszutek Wilk
2011-12-07 20:44 ` Roderick Colenbrander
2011-12-08 23:46 ` Konrad Rzeszutek Wilk
2011-12-09 1:33 ` Roderick Colenbrander
2011-12-09 22:02 ` Roderick Colenbrander
2011-12-11 12:52 ` Pasi Kärkkäinen
2011-12-11 18:58 ` Roderick Colenbrander
2011-12-12 22:30 ` Roderick Colenbrander
2011-12-13 1:50 ` James Harper
2011-12-13 1:58 ` Roderick Colenbrander
2011-12-13 2:02 ` Konrad Rzeszutek Wilk
2011-12-13 21:20 ` Konrad Rzeszutek Wilk
2011-12-16 2:25 ` Roderick Colenbrander
2011-12-26 18:45 ` Roderick Colenbrander
2012-01-03 16:55 ` Konrad Rzeszutek Wilk
2012-01-04 23:37 ` Roderick Colenbrander
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4ED51291.1010308@hfp.de \
--to=ml-xen-devel@hfp.de \
--cc=thunderbird2k@gmail.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).