WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

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

To: Guillaume Thouvenin <guillaume.thouvenin@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] Re: Xen 3.2 and Big Real Mode support?
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Thu, 31 Jan 2008 13:45:04 +0000
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 31 Jan 2008 05:46:23 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <20080131144033.75224fb6@frecb000711>
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AchkD3uKudU+69ACEdylgwAX8io7RQ==
Thread-topic: [Xen-devel] Re: Xen 3.2 and Big Real Mode support?
User-agent: Microsoft-Entourage/11.3.6.070618
On 31/1/08 13:40, "Guillaume Thouvenin" <guillaume.thouvenin@xxxxxxxxxxxx>
wrote:

> On Thu, 31 Jan 2008 10:36:31 +0000
> Keir Fraser <Keir.Fraser@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?

I have a utility to scrape another domain's memory to a file, and then I run
ndisasm on that. The utility is attached.

 -- Keir

Attachment: xenmem.c
Description: Binary data

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
<Prev in Thread] Current Thread [Next in Thread>