From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: Michael Monnerie <michael.monnerie@is.it-management.at>,
xen-devel@lists.xensource.com
Subject: Re: [michael.monnerie@is.it-management.at: kernel crash 2.6.35.4 as XEN client on a XenServer 5.6]
Date: Thu, 09 Sep 2010 11:02:37 +1000 [thread overview]
Message-ID: <4C88322D.5030104@goop.org> (raw)
In-Reply-To: <20100908165210.GA31459@dumpdata.com>
On 09/09/2010 02:52 AM, Konrad Rzeszutek Wilk wrote:
> Anybody seen this?
No. Is it a stock kernel.org kernel?
J
> ----- Forwarded message from Michael Monnerie <michael.monnerie@is.it-management.at> -----
>
> Date: Tue, 7 Sep 2010 07:42:13 +0200
> From: Michael Monnerie <michael.monnerie@is.it-management.at>
> To: linux-kernel@vger.kernel.org
> Subject: kernel crash 2.6.35.4 as XEN client on a XenServer 5.6
>
> I just tried to run a self compiled kernel as XEN guest on a XenServer
> 5.6, but get these crashes during boot. I had to take screenshots, and
> they are overlapping, but at least no line is missing:
>
> http://zmi.at/x/crash1.jpg
> http://zmi.at/x/crash2.jpg
> http://zmi.at/x/crash3.jpg
> http://zmi.at/x/crash4.jpg
> http://zmi.at/x/crash5.jpg
> http://zmi.at/x/crash6.jpg
> http://zmi.at/x/crash7.jpg
> http://zmi.at/x/crash8.jpg
> http://zmi.at/x/crash9.jpg
> http://zmi.at/x/crashA.jpg
> http://zmi.at/x/crashB.jpg
>
> Did I miss some options during kernel compile?
>
next prev parent reply other threads:[~2010-09-09 1:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-08 16:52 [michael.monnerie@is.it-management.at: kernel crash 2.6.35.4 as XEN client on a XenServer 5.6] Konrad Rzeszutek Wilk
2010-09-09 1:02 ` Jeremy Fitzhardinge [this message]
2010-09-09 10:14 ` Michael Monnerie
-- strict thread matches above, loose matches on Subject: below --
2010-09-23 6:10 Michael Monnerie
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=4C88322D.5030104@goop.org \
--to=jeremy@goop.org \
--cc=konrad.wilk@oracle.com \
--cc=michael.monnerie@is.it-management.at \
--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.