From: "andrzej zaborowski" <balrogg@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] KQEMU doesnt support x86-64?
Date: Fri, 2 May 2008 12:21:04 +0200 [thread overview]
Message-ID: <fb249edb0805020321x3ac4f786ma7370bd5ec8fe236@mail.gmail.com> (raw)
In-Reply-To: <fdaac4d50805020308h2b9aaea0p484582410d4c809f@mail.gmail.com>
On 02/05/2008, Jun Koi <junkoi2004@gmail.com> wrote:
> Hi,
>
> I am using qemu-0.9.1 on x86 Linux. I notice that while "qemu" is
> compiled with kqemu support, "qemu-system-x86_64" doesn't (tested on
> the same qemu image)
>
> Is there any reason that qemu-system-x86_64 doesnt support kqemu? Is
> that intention, or just a bug??
KQEMU attempts to skip the code translation, so the target and the
host architecture must be the same. When you're building on amd64,
"qemu-system-x86_64" supports kqemu and "qemu" doesn't.
--
Please do not print this email unless absolutely necessary. Spread
environmental awareness.
prev parent reply other threads:[~2008-05-02 10:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-02 10:08 [Qemu-devel] KQEMU doesnt support x86-64? Jun Koi
2008-05-02 10:21 ` andrzej zaborowski [this message]
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=fb249edb0805020321x3ac4f786ma7370bd5ec8fe236@mail.gmail.com \
--to=balrogg@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).