From: "Magnus Damm" <magnus.damm@gmail.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] qemu-system-x86_64, Xen and CONFIG_IA32_EMULATION
Date: Thu, 20 Apr 2006 09:40:00 +0900 [thread overview]
Message-ID: <aec7e5c30604191740s51e46228ga571ebab34ffab1@mail.gmail.com> (raw)
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
reply other threads:[~2006-04-20 0:40 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=aec7e5c30604191740s51e46228ga571ebab34ffab1@mail.gmail.com \
--to=magnus.damm@gmail.com \
--cc=qemu-devel@nongnu.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).