From: Keir Fraser <keir.fraser@eu.citrix.com>
To: "David P. Quigley" <dpquigl@tycho.nsa.gov>,
Samuel Thibault <samuel.thibault@ens-lyon.org>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: Re: [PATCH] pv-grub: fix boot crash when no fb is available
Date: Tue, 13 Apr 2010 16:12:45 +0100 [thread overview]
Message-ID: <C7EA487D.10B7E%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <1271170524.19046.286.camel@moss-terrapins.epoch.ncsc.mil>
On 13/04/2010 15:55, "David P. Quigley" <dpquigl@tycho.nsa.gov> wrote:
> I just returned from vacation and am working on this again and have run
> into a new stumbling block. I managed to solve the booting to the grub
> prompt issue (apparently pvgrub can't handle symlinks). The issue now
> though is that my image that works fine as an HVM seems to hang. I've
> pasted the output below. In there you can see that there is a call trace
> for something xen related early on in the kernel boot process. I'm
> unsure if this is related to some of the other pvgrub problems I've been
> seeing on the list as of late.
Can you boot this kernel *without* using pvgrub or pygrub? The kernel's PV
support may well simply be buggy.
-- Keir
next prev parent reply other threads:[~2010-04-13 15:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-04 17:18 [PATCH] pv-grub: fix boot crash when no fb is available Samuel Thibault
2010-04-05 13:40 ` David P. Quigley
2010-04-05 15:16 ` Samuel Thibault
2010-04-05 15:17 ` David P. Quigley
2010-04-05 21:57 ` Samuel Thibault
2010-04-06 15:42 ` David P. Quigley
2010-04-06 18:16 ` Jeremy Fitzhardinge
2010-04-06 18:22 ` David P. Quigley
2010-04-06 19:17 ` Jeremy Fitzhardinge
2010-04-06 22:28 ` Daniel Stodden
2010-04-06 21:47 ` Samuel Thibault
2010-04-13 14:55 ` David P. Quigley
2010-04-13 15:12 ` Keir Fraser [this message]
2010-04-13 17:16 ` Jeremy Fitzhardinge
2011-04-28 10:56 ` Samuel Thibault
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=C7EA487D.10B7E%keir.fraser@eu.citrix.com \
--to=keir.fraser@eu.citrix.com \
--cc=dpquigl@tycho.nsa.gov \
--cc=jeremy@goop.org \
--cc=samuel.thibault@ens-lyon.org \
--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).