xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Simon Rowe <simon.rowe@eu.citrix.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: megasas stops I/O when running kernel as dom0 under xen4.1/4.2
Date: Thu, 11 Aug 2011 18:51:19 -0400	[thread overview]
Message-ID: <20110811225119.GA3557@dumpdata.com> (raw)
In-Reply-To: <201108111727.26021.simon.rowe@eu.citrix.com>

On Thu, Aug 11, 2011 at 05:27:25PM +0100, Simon Rowe wrote:
> On Thursday 11 August 2011 14:59:39 Andreas Olsowski wrote:
> 
> > as one of the people using Dell Servers i am aware that the LSI megaraid
> > drivers are quite old in the current 2.6.32 pvops tree,
> > but it seems that, once again, i have run into problems that are more
> > rare than the usual "cant find disk" issues. (Of which i had none, ever)
> > 
> > 
> > The situation:
> > --------------
> > I have 2 dom0 kernels, 2.6.32.44 and 3.0.1 that work fine when booted
> > bare-metal. I can run stress -m 40 -d 4 -i 1 for hours on end without
> > any error occuring.
> > The 2.6.32.44 kernels use version 00.00.05.30 megasas modules.
> 
> I've had reports of something similar with a Dell R710 and MegaRAID SAS 
> controller. We're using version 00.00.05.33 of megaraid_sas on a classic Xen 
> 2.6.32 kernel.

With the same version of hypervisor?

Andreas,

Can you try running without irqbalance daemon?
> 
> 	Simon
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel

  reply	other threads:[~2011-08-11 22:51 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-11 13:59 megasas stops I/O when running kernel as dom0 under xen4.1/4.2 Andreas Olsowski
2011-08-11 16:27 ` Simon Rowe
2011-08-11 22:51   ` Konrad Rzeszutek Wilk [this message]
2011-08-12  6:31     ` xen.frontend flag for higher display resolution (vnc) for HVM domU domains Mark Schneider
2011-08-12  7:26       ` Marc - A. Dahlhaus
2011-08-12  7:42     ` megasas stops I/O when running kernel as dom0 under xen4.1/4.2 Simon Rowe
2011-08-12  9:11     ` Andreas Olsowski
2011-08-12  9:23       ` Simon Rowe
2011-08-15 10:49       ` Simon Rowe
2011-08-15 12:52         ` Andreas Olsowski
2011-08-19 12:28           ` Andrew Cooper
2011-08-19 14:17             ` Andreas Olsowski
2011-08-19 14:57               ` Andrew Cooper
2011-08-19 16:37                 ` Andreas Olsowski
2011-08-19 16:49                   ` Andrew Cooper
2011-08-19 18:10                     ` Andreas Olsowski
2011-08-22  9:05                       ` Andrew Cooper
2011-08-24 12:06                         ` Andrew Cooper
2011-08-24 16:57                           ` Andrew Cooper
2011-08-24 17:09                             ` Konrad Rzeszutek Wilk
2011-08-24 17:20                               ` Andrew Cooper
2011-08-26 18:16                                 ` Andrew Cooper
2011-08-26 18:32                                   ` Andrew Cooper
2011-08-30 12:02                                     ` Andreas Olsowski
2011-08-30 12:11                                       ` Andrew Cooper
2011-08-30 12:46                                         ` Keir Fraser
2011-08-12  9:02 ` Simon Rowe
2011-08-12 16:26   ` Pasi Kärkkäinen
2011-08-15  7:44     ` Simon Rowe
2011-08-12 16:25 ` Pasi Kärkkäinen

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=20110811225119.GA3557@dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=simon.rowe@eu.citrix.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).