qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: <jeebs@yango.us>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] We want to example qemu and the accel-module in ourdistribution.
Date: Thu, 12 May 2005 23:50:08 -0500	[thread overview]
Message-ID: <000e01c55777$48a9f5f0$334d21d1@organiza3bfb0e> (raw)
In-Reply-To: 20050513041633.GA6576@hugang.soulinfo.com

>Why not choose QEMU + QVM86, The QVM86 do same thing with accelerator
>module, but it is Open Source Project.

Because at the moment, qvm86 doesn't work well.  Still has bugs and 
limitations.  And it actually seems to be *slower* than qemu without it.  Or 
at least not much faster.

That's based on the only Windows cvs build that had qvm86 with it.  (Still 
available from the club-internet.fr Win daily build mirror.)

I assume the linux build behaves the same, since it is based on the same 
core routines and techniques.  That seems to be the impression I get from 
the qemu users forum, anyway.


I'm sure it could be significantly improved, but at the moment there are 
only a couple people working occasionally on it.  So it's not something you 
can depend on being vastly improved on in the next few weeks.  (To be 
honest, I suspect that the qvm86 techniques didn't work as well as the 
author originally expected / hoped.  Just my feeling.)

  reply	other threads:[~2005-05-13  5:00 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-13  3:14 [Qemu-devel] We want to example qemu and the accel-module in our distribution Xuqing Kuang
2005-05-13  4:16 ` hugang
2005-05-13  4:50   ` jeebs [this message]
2005-05-13  4:53   ` Mike Swanson
2005-05-13  6:56   ` Xuqing Kuang
2005-05-13  8:33     ` Hetz Ben Hamo
2005-05-13 12:43       ` Christian MICHON
2005-05-13 13:24         ` Jason Gress
2005-05-13 14:41         ` Leonardo E. Reiter
2005-05-14  2:26       ` Xuqing Kuang
2005-05-13 12:14 ` Paul Brook

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='000e01c55777$48a9f5f0$334d21d1@organiza3bfb0e' \
    --to=jeebs@yango.us \
    --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).