From: "H. Peter Anvin" <hpa@zytor.com>
To: Christian Ehrhardt <lk@c--e.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: New x886-Setup code breaks HVM-XEN boot
Date: Thu, 30 Aug 2007 07:49:26 -0700 [thread overview]
Message-ID: <46D6D8F6.2040201@zytor.com> (raw)
In-Reply-To: <20070830141528.GA307@lisa.in-ulm.de>
Christian Ehrhardt wrote:
>
> Note the the xm console command terminates on its own, i.e. the guest
> machine seems to halt and not hang somewhere.
>
> I could verify that the real mode code up to the assembly code in
> pmjump.S is in fact executed. The problem appears to occur while
> enabling protected mode. I tried to put endless loops into the 32-bit
> setup code but these were apparently not reached. As far as I understand
> this, the protected mode jump in pmjump.S seems to jump into nowhere.
>
> I am willing to do tests with the XEN guest and send any additional
> information that might be helpful. However, I cannot change the XEN host
> at this time.
>
> Any suggestions?
>
All of this point to a bug in the Xen emulation host. You're not saying
if you're on an Intel or AMD host, but on Intel, hardware
virtualization doesn't actually kick in until you're in protected mode
with all segments configured properly. This means all of pmjump.S runs
in an interpreter. A bug in that interpreter would cause what you observe.
-hpa
next prev parent reply other threads:[~2007-08-30 14:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-30 14:15 New x886-Setup code breaks HVM-XEN boot Christian Ehrhardt
2007-08-30 14:49 ` H. Peter Anvin [this message]
2007-09-03 18:32 ` New x86-Setup " Christian Ehrhardt
2007-09-04 6:16 ` H. Peter Anvin
2007-08-30 19:04 ` New x886-Setup " Jeremy Fitzhardinge
2007-08-31 7:54 ` New x86-Setup " Christian Ehrhardt
2007-08-31 14:20 ` H. Peter Anvin
2007-09-05 13:06 ` Ian Campbell
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=46D6D8F6.2040201@zytor.com \
--to=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lk@c--e.de \
/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