From: Anton D Kachalov <mouse@mayc.ru>
To: Chris Frey <cdfrey@foursquare.net>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Killing KQEMU
Date: Tue, 02 Jun 2009 13:26:27 +0400 [thread overview]
Message-ID: <4A24F043.60007@mayc.ru> (raw)
In-Reply-To: <20090602035217.GA16574@foursquare.net>
On 02.06.2009 07:52, Chris Frey wrote:
> Hi,
>
> I feel that I should post here, for the simple reason that most QEMU
> users likely don't read this list, and have no idea that developers are
> striving to kill off a valued feature.
>
[...]
Chris,
I may suggest you to switch to VirtualBox / VirtualBox OSE that has more
features (comparable to VmWare) if you're interested to use QEMU just to
run some kind of OS. It's much faster than QEMU + kqemu. And more over,
it's stable. Sometimes I have software fails (segfaults in Java JIT)
with QEMU+kqemu, but VBox drives well.
If you're HW/FW developer, you doesn't need kqemu at all.
Rgds,
Anton
next prev parent reply other threads:[~2009-06-02 9:26 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-02 3:52 [Qemu-devel] Killing KQEMU Chris Frey
2009-06-02 4:18 ` Avi Kivity
2009-06-02 6:28 ` Avi Kivity
2009-06-02 19:25 ` [Qemu-devel] " Chris Frey
2009-06-02 4:45 ` [Qemu-devel] " Rick Vernam
2009-06-02 12:54 ` Paul Brook
2009-06-02 20:09 ` [Qemu-devel] " Chris Frey
2009-06-02 20:24 ` Avi Kivity
2009-06-03 21:50 ` [Qemu-devel] " Chris Frey
2009-06-04 6:30 ` [Qemu-devel] " Avi Kivity
2009-06-02 20:30 ` Paul Brook
2009-06-03 21:34 ` Chris Frey
2009-06-03 21:46 ` Rick Vernam
2009-06-06 11:01 ` Andreas Färber
2009-06-06 11:27 ` Paul Brook
2009-06-06 13:50 ` Andreas Färber
2009-06-06 15:24 ` Gleb Natapov
2009-06-06 16:03 ` Avi Kivity
2009-06-02 20:35 ` Gerd Hoffmann
2009-06-02 20:47 ` Stuart Brady
2009-06-03 21:21 ` [Qemu-devel] " Chris Frey
2009-06-04 0:22 ` Paul Brook
2009-06-02 6:25 ` [Qemu-devel] " Gleb Natapov
2009-06-02 9:26 ` Anton D Kachalov [this message]
2009-06-02 19:47 ` [Qemu-devel] " Chris Frey
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=4A24F043.60007@mayc.ru \
--to=mouse@mayc.ru \
--cc=cdfrey@foursquare.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.