From mboxrd@z Thu Jan  1 00:00:00 1970
From: Jeremy Fitzhardinge <jeremy@goop.org>
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
Message-ID: <4742F905.20903@goop.org>
References: <C3689E39.18A85%Keir.Fraser@cl.cam.ac.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <C3689E39.18A85%Keir.Fraser@cl.cam.ac.uk>
List-Unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: xen devel <xen-devel@lists.xensource.com>
List-Id: xen-devel@lists.xenproject.org

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