From: Gregory Alexander <yakovlev@grandecom.net>
To: qemu-devel@nongnu.org
Subject: Old version support. Was: Re: [Qemu-devel] FreeOSZoo will stop March 1, 2005
Date: Tue, 15 Feb 2005 17:32:50 -0600 [thread overview]
Message-ID: <421286A2.7020609@grandecom.net> (raw)
In-Reply-To: <67341562.20050213010610@ena.si>
I worry about the availability of patches for the old version, since the
new one is so much faster. (See bochs->Qemu mass move, when system
emulation became available.)
Will Fabrice continue to support the userspace version of QEMU?
KQEMU would be an EXCELLENT way to test the CPU emulation of userspace
QEMU. Is anyone considering doing this? Is it an option with the new
license?
These are the kinds of problems that I foresee.
Anyways, I understand the rationale, just have a few fears.
Thanks,
GREG
Jernej Simončič wrote:
> On Saturday, February 12, 2005, 22:18:48, Daniel Egger wrote:
>
>
>>If you only intend to run Linux VMs and don't have a problem
>>patching the kernel sources this is a very viable approach to
>>get something which is not possible anymore *without* kqemu
>>which is more flexible but does only run on 32bit kernels ATM.
>
>
> You don't understand - I was asking what are you loosing with "new" Qemu
> without the kernel module compared to Qemu before the kernel module was
> introduced. I know that with the kernel module Qemu runs much faster, but if
> you don't want to use it due to it's licence, you haven't lost anything
> compared to before the module was available. Or have you?
>
next prev parent reply other threads:[~2005-02-15 23:55 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-12 9:18 [Qemu-devel] FreeOSZoo will stop March 1, 2005 Jean-Michel POURE
2005-02-12 10:15 ` Magnus Damm
2005-02-12 10:18 ` Brad Campbell
2005-02-12 12:19 ` Antti-Juhani Kaijanaho
2005-02-12 12:20 ` Daniel Egger
2005-02-12 13:42 ` Brad Campbell
2005-02-12 16:15 ` Daniel Egger
2005-02-12 17:00 ` Fabrice Bellard
2005-02-12 18:11 ` Jernej Simončič
2005-02-12 21:18 ` Daniel Egger
2005-02-12 23:01 ` Darrin Ritter
2005-02-13 0:06 ` Jernej Simončič
2005-02-13 11:28 ` Daniel Egger
2005-02-13 17:01 ` Jim C. Brown
2005-02-13 17:40 ` [Qemu-devel] Plex86 and Qemu jeebs
2005-02-13 18:27 ` Jim C. Brown
2005-02-13 19:35 ` jeebs
2005-02-13 22:06 ` Jim C. Brown
2005-02-13 23:20 ` jeebs
2005-02-14 0:05 ` [Qemu-devel] coLinux and Qemu? --was-- " Darryl Dixon
2005-02-14 0:37 ` Jim C. Brown
2005-02-14 0:58 ` Mark Williamson
2005-02-14 0:34 ` [Qemu-devel] " Jim C. Brown
2005-02-14 10:39 ` Andreas Bollhalder
2005-02-13 22:18 ` Adrian Smarzewski
2005-02-13 23:04 ` Martin Koniczek
2005-02-14 14:18 ` Phil Krylov
2005-02-15 23:32 ` Gregory Alexander [this message]
2005-02-16 18:51 ` Old version support. Was: Re: [Qemu-devel] FreeOSZoo will stop March 1, 2005 Fabrice Bellard
2005-02-13 0:18 ` Jim C. Brown
2005-02-13 4:42 ` James Mastros
2005-02-13 5:26 ` Jim C. Brown
2005-02-13 6:21 ` James Mastros
2005-02-13 10:02 ` Darryl Dixon
2005-02-13 16:53 ` Jim C. Brown
2005-02-13 13:32 ` [Qemu-devel] " Robert Wittams
2005-02-12 22:41 ` [Qemu-devel] " Grzegorz Kulewski
2005-02-17 21:53 ` Herbert Poetzl
2005-02-17 22:18 ` Grzegorz Kulewski
2005-02-17 23:25 ` Fabrice Bellard
2005-02-18 4:29 ` John R. Hogerhuis
2005-02-18 8:23 ` Asko Kauppi
2005-02-18 11:05 ` Elefterios Stamatogiannakis
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=421286A2.7020609@grandecom.net \
--to=yakovlev@grandecom.net \
--cc=gwa@alumni.cmu.edu \
--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.