This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] Re: Xen 3.2 and Big Real Mode support?

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-devel] Re: Xen 3.2 and Big Real Mode support?
From: Guillaume Thouvenin <guillaume.thouvenin@xxxxxxxxxxxx>
Date: Wed, 6 Feb 2008 09:20:30 +0100
Delivery-date: Wed, 06 Feb 2008 02:53:51 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <C3CE3A04.1BE55%Keir.Fraser@xxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Organization: Bull S.A.
References: <20080131144033.75224fb6@frecb000711> <C3CE3A04.1BE55%Keir.Fraser@xxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Tue, 05 Feb 2008 16:06:28 +0000
Keir Fraser <Keir.Fraser@xxxxxxxxxxxx> wrote:

> On 31/1/08 13:40, "Guillaume Thouvenin" <guillaume.thouvenin@xxxxxxxxxxxx>
> wrote:
> >> I reproduced the problem. CPUID is not executed before the crash. Also a
> >> disassembly of that area of memory does not look like sane 16-bit code. So 
> >> I
> >> think something has gone wrong before we get to the (probably bogus) MOVHPS
> >> instruction.
> > 
> > A question here. You reproduce the problem by starting a domain and
> > booting it on the openSUSE-10.3-GM-x86_64-mini.iso CD-ROM? How do you
> > disassemble the area of memory that produces the problem? Are you using
> > "objdump" on the bootloader found on the iso file or are you using some
> > other trick?
> By the way, this is now fixed with tip of the xen-unstable tree (changeset
> 16980), obtainable from http://xenbits.xensource.com/staging/xen-unstable.hg

Waow. I don't understand everything (and especially how you find that
the problem was here) but it works now.

 I have another question, why did you remove VMXASSIST? I saw that you
replaced all invocation to VMXASSIST by only one call to
vmx_goto_realmode() in arch/x86/hvm/svm/x86_64/exits.S. Are there some
links to any discussion about this choice?

Thanks for your help,

Xen-devel mailing list