All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Cris Daniluk <cris.daniluk@gmail.com>
Cc: Drew Jones <drjones@redhat.com>,
	dwu@redhat.com, xen-devel@lists.xensource.com
Subject: Re: Dom0 panic on xen 3.4.3
Date: Mon, 01 Nov 2010 11:28:50 +0100	[thread overview]
Message-ID: <4CCE9662.5040600@redhat.com> (raw)
In-Reply-To: <AANLkTinLLt5=mjm5kG56E3r7eikgC49ini5oz_0qw2S+@mail.gmail.com>

On 08/22/2010 12:27 AM, Cris Daniluk wrote:
> Having the same issue with the EL5 RPM as well. Latest 2.6.18 on
> xen.org seems to be a little broken. The LSI controller isn't getting
> detected after the megaraid_sas module loads. The initrds look
> identical between the two, so I'm assuming there is some obscure bug
> that was fixed and backported into the EL5 kernel but not Jeremy's. I
> suppose I can try a newer pvops kernel if you think that might be
> relevant.
>
> Seems to be fairly consistently crashing regardless of Xen version,
> though. Also interestingly it seems it may be more about the VMs
> starting at once htan the specific number of VMs..

Hi Cris,

I am a virtualization engineer at Red Hat.  We encountered this bug 
recently but we are not able to reproduce it consistently.  Can you do 
so?  If so, I could try giving you a test EL5 kernel (so that you can 
boot) with upstream's netback driver to test it.

Thanks,

Paolo

  reply	other threads:[~2010-11-01 10:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-20 18:15 Dom0 panic on xen 3.4.3 Cris Daniluk
2010-08-20 23:59 ` Pasi Kärkkäinen
2010-08-21  0:20   ` Cris Daniluk
2010-08-21 10:12     ` Pasi Kärkkäinen
2010-08-21 22:27       ` Cris Daniluk
2010-11-01 10:28         ` Paolo Bonzini [this message]
2010-12-28  0:50           ` prickett233
2010-12-28 10:38             ` 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=4CCE9662.5040600@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=cris.daniluk@gmail.com \
    --cc=drjones@redhat.com \
    --cc=dwu@redhat.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 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.