From: Jeremy Fitzhardinge <jeremy@goop.org>
To: M A Young <m.a.young@durham.ac.uk>
Cc: xen-devel@lists.xensource.com
Subject: Re: i386 boot problem on xen/next
Date: Fri, 19 Feb 2010 16:11:39 -0800 [thread overview]
Message-ID: <4B7F28BB.3000903@goop.org> (raw)
In-Reply-To: <alpine.LFD.2.00.1002192138340.29668@vega1.dur.ac.uk>
On 02/19/2010 01:39 PM, M A Young wrote:
> I have now got xen/next to boot on x86_64, though I can't start the
> client (which may be the issue with xen 4 rc4 and pygrub which I think
> someone mentioned). However with i386 it crashes on boot. The crash is
> in xen_set_pte, some logs and debugging are attached.
You're booting a PV domU using a stock Fedora kernel?
You're doing better than me in that case; I get a sullen hang in
pvgrub. I can boot hvm domains OK, so I think the backends/xenstore are
all OK.
Are you using pygrub or pvgrub? If the latter, can you post whatever
output it generates?
J
next prev parent reply other threads:[~2010-02-20 0:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <alpine.LFD.2.00.1002192033200.29668@vega1.dur.ac.uk>
[not found] ` <alpine.LFD.2.00.1002192120330.29668@vega1.dur.ac.uk>
2010-02-19 21:39 ` i386 boot problem on xen/next M A Young
2010-02-20 0:11 ` Jeremy Fitzhardinge [this message]
2010-02-20 0:27 ` M A Young
2010-02-20 20:29 ` M A Young
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=4B7F28BB.3000903@goop.org \
--to=jeremy@goop.org \
--cc=m.a.young@durham.ac.uk \
--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.