All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: xen devel <xen-devel@lists.xensource.com>
Subject: Re: Xen 3.1.2 + 2.6.23.8 == traps.c:403:d0 Unhandled invalid opcode fault/trap [#6] in domain 0 on VCPU 0 [ec=0000]
Date: Tue, 20 Nov 2007 07:11:01 -0800	[thread overview]
Message-ID: <4742F905.20903@goop.org> (raw)
In-Reply-To: <C3689E39.18A85%Keir.Fraser@cl.cam.ac.uk>

Keir Fraser wrote:
> Two compounded problems. Firstly, the 2.6.23 Xen support only works as domU,
> not as dom0. Secondly, because the dom0 domain builder inside Xen sets a
> 'magic' string in start_info as 'xen-3.1-...' rather than 'xen-3.0-...' as
> the user-space domain builder does, the 2.6.23 kernel BUG_ON()s very very
> early when run as dom0.
>
> I've cc'ed Jeremy as I believe the BUG_ON() should simply be got rid of (or
> at least should perhaps only check for the 'xen-' prefix).

Fair enough.  I was wondering what it actually means: is it just a
hypervisor version string, or is it a hypervisor ABI signature?  Could I
reasonably check for "xen-3", or will Xen 4.x put something else there?

    J

  reply	other threads:[~2007-11-20 15:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-19 18:00 Xen 3.1.2 + 2.6.23.8 == traps.c:403:d0 Unhandled invalid opcode fault/trap [#6] in domain 0 on VCPU 0 [ec=0000] Christopher S. Aker
2007-11-20 10:41 ` Keir Fraser
2007-11-20 14:10   ` Christopher S. Aker
2007-11-20 14:22 ` Keir Fraser
2007-11-20 15:11   ` Jeremy Fitzhardinge [this message]
2007-11-20 15:30     ` Keir Fraser

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=4742F905.20903@goop.org \
    --to=jeremy@goop.org \
    --cc=Keir.Fraser@cl.cam.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.