From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1FWNDJ-0002Nb-AQ
	for qemu-devel@nongnu.org; Wed, 19 Apr 2006 20:40:05 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1FWNDG-0002Mh-3X
	for qemu-devel@nongnu.org; Wed, 19 Apr 2006 20:40:04 -0400
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1FWNDF-0002MX-R6
	for qemu-devel@nongnu.org; Wed, 19 Apr 2006 20:40:01 -0400
Received: from [64.233.166.181] (helo=pproxy.gmail.com)
	by monty-python.gnu.org with esmtp (Exim 4.52) id 1FWNET-0002aK-89
	for qemu-devel@nongnu.org; Wed, 19 Apr 2006 20:41:17 -0400
Received: by pproxy.gmail.com with SMTP id w49so23708pyg
	for <qemu-devel@nongnu.org>; Wed, 19 Apr 2006 17:40:00 -0700 (PDT)
Message-ID: <aec7e5c30604191740s51e46228ga571ebab34ffab1@mail.gmail.com>
Date: Thu, 20 Apr 2006 09:40:00 +0900
From: "Magnus Damm" <magnus.damm@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Subject: [Qemu-devel] qemu-system-x86_64, Xen and CONFIG_IA32_EMULATION
Reply-To: qemu-devel@nongnu.org
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: qemu-devel@nongnu.org

Hi there,

I'm currently using qemu-system-x86_64 (from cvs) to do Xen
development for the x86_64 architecture. I find that x86_64 emulation
in qemu works pretty well as long as I use a non-smp x86_64 linux
kernel and ia32 user space together with CONFIG_IA32_EMULATION.

Unfortunately, if I run the Xen hypervisor (x86_64) together with a
dom0 kernel (x86_64) configured with CONFIG_IA32_EMULATION, then my
ia32 user space code segfaults in qemu but runs ok on real hardware.
Vanilla kernel (x86_64) configured with CONFIG_IA32_EMULATION works
well in qemu with my ia32 user space code though.

I'm quite busy right now, but if some hacker experienced with x86_64
qemu wants to improve the x86_64 emulation, now is a golden
opportunity. I have binaries and source code that might be useful.
More information could be found here:

http://lists.xensource.com/archives/html/xen-devel/2006-04/msg00778.html

Thanks,

/ magnus