From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Cc: Steffen Liebergeld <usenet@gmx.eu>
Subject: Re: [Qemu-devel] Status on ARM host cpu
Date: Fri, 14 Nov 2008 14:15:51 +0000 [thread overview]
Message-ID: <200811141415.51702.paul@codesourcery.com> (raw)
In-Reply-To: <gfjd36$85n$1@ger.gmane.org>
On Friday 14 November 2008, Steffen Liebergeld wrote:
> Hi,
>
> I am currently researching of whether or not it is feasible to port kqemu
> to the ARM platform. The website says qemu on ARM hosts is in
> "testing"-state. Does that still apply to the latest svn-Version?
Should just about work, though you should expect bugs.
However I advise using KVM and not kqemu. KVM has already been merged to
upstream kernels, and the chances of getting another hypervisor interface
merged are approximately zero.
Paul
next prev parent reply other threads:[~2008-11-14 14:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-14 8:32 [Qemu-devel] Status on ARM host cpu Steffen Liebergeld
2008-11-14 14:15 ` Paul Brook [this message]
2008-11-15 15:12 ` [Qemu-devel] " Steffen Liebergeld
2008-11-15 22:21 ` Jan Kiszka
2008-11-17 16:32 ` Hollis Blanchard
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=200811141415.51702.paul@codesourcery.com \
--to=paul@codesourcery.com \
--cc=qemu-devel@nongnu.org \
--cc=usenet@gmx.eu \
/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).