From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Charles Gruener <cjg9411@rit.edu>
Cc: xen-devel@lists.xensource.com, fedora-xen@redhat.com
Subject: Re: [Fedora-xen] 2.6.31-1.2.65.xendom0.fc12.x86_64 crash on boot
Date: Tue, 15 Sep 2009 14:14:56 -0700 [thread overview]
Message-ID: <4AB003D0.70706@goop.org> (raw)
In-Reply-To: <94EE0889-57F7-46DC-994A-7ED0F4AE79ED@rit.edu>
On 09/15/09 14:01, Charles Gruener wrote:
> Well, for some reason, the BIOS had NX disabled by default. After
> enabling, I can now get further.
OK, good to know. I'll post a patch shortly which I hope will make it
work either way.
> I've attached the output I'm now seeing. Could this now be related to
> the myoung kernel?
It's crashing because dom0 is trying to manipulate the DMAR hardware,
which Xen won't allow. I think there's a fix in Xen to hide the DMAR
from dom0, but in the meantime you can disable it in BIOS.
J
next prev parent reply other threads:[~2009-09-15 21:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <976E8557-F11D-416E-84C2-CD12B180CA1B@rit.edu>
[not found] ` <20090915071730.GP31123@reaktio.net>
[not found] ` <20090915075613.GQ31123@reaktio.net>
[not found] ` <82B3AFF8-B4F1-4347-82F3-04F100002684@rit.edu>
2009-09-15 11:39 ` [Fedora-xen] 2.6.31-1.2.65.xendom0.fc12.x86_64 crash on boot Pasi Kärkkäinen
2009-09-15 11:53 ` Pasi Kärkkäinen
2009-09-15 14:41 ` Nathan Stratton
2009-09-15 19:58 ` Jeremy Fitzhardinge
2009-09-15 21:01 ` Charles Gruener
2009-09-15 21:14 ` Jeremy Fitzhardinge [this message]
2009-09-15 22:23 ` [Fedora-xen] " Jeremy Fitzhardinge
2009-09-16 8:47 ` M A Young
2009-09-16 11:47 ` Pasi Kärkkäinen
2009-09-16 16:09 ` Charles Gruener
2009-09-21 19:07 ` Re: [Fedora-xen] " Jeremy Fitzhardinge
2009-09-21 19:24 ` Charles J Gruener
[not found] ` <alpine.GSO.2.00.0909151240230.27096@algedi.dur.ac.uk>
[not found] ` <20090915121026.GV31123@reaktio.net>
[not found] ` <alpine.LFD.2.00.0909151323110.16009@vega4.dur.ac.uk>
2009-09-15 12:46 ` 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=4AB003D0.70706@goop.org \
--to=jeremy@goop.org \
--cc=cjg9411@rit.edu \
--cc=fedora-xen@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.