qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Hetz Ben Hamo <hetzbh@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Open source qemu x86 accelerator module.
Date: Sun, 3 Apr 2005 01:45:48 +0200	[thread overview]
Message-ID: <41e41e7a050402154521b4d775@mail.gmail.com> (raw)
In-Reply-To: <200504030022.17173.paul@codesourcery.com>

Hi Paul,

First - congratulations for your new kernel module. I have few
questions, if you don't mind:

1. Have you tested the speed compared to QEMU CVS + kqemu?
2. Which Windows 2000 have you installed? there are few versions of
the bootable CD's, few of them comes with service packs already
applied..
3. Do you plan to make it work with the 2.4.x kernels?
4. Have you tried installing it with XP as guest?

Thanks,
Hetz

On Apr 3, 2005 1:22 AM, Paul Brook <paul@codesourcery.com> wrote:
> I'd like to announce qvm86; an open source x86 accelerator module for qemu.
> 
> qvm86 is basically a drop-in replacement for kqemu. However is is an
> independent replacement written from scratch by myself, and released under
> the GnNU General Public Licence (GPL).
> 
> The CVS repository and mailing list for qvm86 are hosted on savannah:
> http://www.nongnu.org/qvm86/
> 
> qvm86 is still in the early stages of development, so I provide no guarantees
> about its reliability. It almost certainly has bugs which could crash your
> machine or cause data corruption. Any assistance identifying and fixing these
> bugs is welcomed ;-)
> 
> See the README file in qvm86 CVS for brief instructions how to install. It's
> basically the same procedure as kqemu.
> 
> qvm86 currently only works on x86-linux hosts, and has only been tested on
> relatively recent 2.6 kernels with udev installed.
> 
> It should be possible to port qvm86 to other x86 hosts (eg. FreeBSD or even
> Windows). I don't have immediate plans for doing such ports, but would
> welcome patches if other people want to do the porting. It may also be
> possible to x86-64 hosts, but I don't know enough details to say how hard
> this would be.
> 
> I have successfully booted windows 2000, freebsd and couple of different linux
> guests. Windows 98 guests don't work, but I think I know what's wrong.
> 
> Performance depends heavily on the guest wokload. It varies from near-native
> to about the same as normal qemu. For example compiling qemu with gcc is ~5x
> slower than native (normal qemu is ~17x slower). I believe there is sill
> quite a bit of scope for improving performance.
> 
> Paul Brook
> 
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/qemu-devel
>

  reply	other threads:[~2005-04-03  0:04 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-02 23:22 [Qemu-devel] Open source qemu x86 accelerator module Paul Brook
2005-04-02 23:45 ` Hetz Ben Hamo [this message]
2005-04-03  0:30   ` Paul Brook
2005-04-03  0:47   ` Jim C. Brown
2005-04-03  1:16     ` Paul Brook
2005-04-03  4:31       ` Jim C. Brown
2005-04-03  0:32 ` Jim C. Brown
2005-04-03  7:24 ` Jean-Michel POURE
2005-04-03  8:38 ` ML
2005-04-03 18:58 ` Herbert Poetzl
2005-04-04  5:47 ` Jens Arm
  -- strict thread matches above, loose matches on Subject: below --
2005-04-14 21:30 James Stone

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=41e41e7a050402154521b4d775@mail.gmail.com \
    --to=hetzbh@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).