From: Ian Campbell <ian.campbell@citrix.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
Christoffer Dall <cdall@cs.columbia.edu>
Cc: xen-devel@lists.xen.org
Subject: Re: Dom0 crash with apache bench (ab)
Date: Tue, 28 Jul 2015 15:55:19 +0100 [thread overview]
Message-ID: <1438095319.11600.165.camel@citrix.com> (raw)
In-Reply-To: <20150728145022.GE26623@x230.dumpdata.com>
On Tue, 2015-07-28 at 10:50 -0400, Konrad Rzeszutek Wilk wrote:
> On Tue, Jul 28, 2015 at 03:09:31PM +0200, Christoffer Dall wrote:
> > Hi,
> >
> > I've been doing some performance comparisons lately, and wanted to
> > compare
> > the performance overhead of using Xen with apache bench, but
> > unfortunately
> > the Dom0 kernel crashes when hitting it with ab from a remote machine.
> > Most other workloads seem to be stable, however, I do see similar
> > crashes
> > if hitting Dom0 mysql with a mysql benchmark with a high level of
> > parallelism.
> >
> > I use a 10G Mellanox MX354A Dual port FDR CX3 adapter for networking on
> > a
> > Dell PowerEdge R320 system with a Xeon E5-2450 and 16 GB of RAM.
> >
> > Interestingly, we had a similarly looking issue on arm64 recently, but
> > that
> > was fixed with an APM-soecific fix to the hypervisor, so I am guessing
> > this
> > is unrelated, see:
> > http://lists.xenproject.org/archives/html/xen-devel/2015
> > -03/msg02731.html
> > and the fix:
> > http://xenbits.xen.org/gitweb/?p=xen.git;a=commit;h=50dcb3de603927db2fd
> > 87ba09e29c817415aaa44
> >
> > I have tried with several Linux versions, v3.13, v3.18, v4.0-rc4, and
> > v4.1,
> > same issue. I have tried with Xen 4.5-0 release, and the Ubuntu
> > packaged
> > Xen 4.4 release, same issue.
> >
> > Examples of crash:
> > http://pastebin.ubuntu.com/11953498/
> > http://pastebin.ubuntu.com/11953443/
>
> 4.0-rc4?
>
> Have you tried 4.1?
According to the previous paragraph, yes he has.
>
> >
> > Running DomU with a bridge and running ab against apache running in a
> > DomU
> > also causes the system to crash.
> >
> > Note: The server also has an embedded 1G Broadcom NIC (although not
> > suitable for testing due to it being 1G and on a control network), and
> > using that for the test does not cause a system crash, so this points
> > to
> > some difficulties with the Mellanox device and Xen.
> >
> > Any ideas or advice is greatly appreciated, thanks.
> >
> > -Christoffer
>
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@lists.xen.org
> > http://lists.xen.org/xen-devel
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2015-07-28 14:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-28 13:09 Dom0 crash with apache bench (ab) Christoffer Dall
2015-07-28 14:50 ` Konrad Rzeszutek Wilk
2015-07-28 14:55 ` Ian Campbell [this message]
2015-07-28 15:00 ` Christoffer Dall
2015-07-31 10:24 ` Stefano Stabellini
2015-07-31 10:28 ` David Vrabel
2015-07-31 13:17 ` Christoffer Dall
2015-09-14 12:40 ` Christoffer Dall
2015-09-14 15:11 ` Konrad Rzeszutek Wilk
2015-09-14 15:20 ` Ian Campbell
2015-09-14 16:16 ` Christoffer Dall
2015-09-28 20:53 ` Christoffer Dall
2015-09-30 15:12 ` Konrad Rzeszutek Wilk
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=1438095319.11600.165.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=cdall@cs.columbia.edu \
--cc=konrad.wilk@oracle.com \
--cc=xen-devel@lists.xen.org \
/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 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.