From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1LVlsr-0007gL-AS
	for qemu-devel@nongnu.org; Sat, 07 Feb 2009 07:02:05 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1LVlso-0007fJ-Mk
	for qemu-devel@nongnu.org; Sat, 07 Feb 2009 07:02:04 -0500
Received: from [199.232.76.173] (port=55610 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1LVlso-0007fC-G7
	for qemu-devel@nongnu.org; Sat, 07 Feb 2009 07:02:02 -0500
Received: from moutng.kundenserver.de ([212.227.126.177]:64284)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <weil@mail.berlios.de>) id 1LVlsn-0007Vf-Ow
	for qemu-devel@nongnu.org; Sat, 07 Feb 2009 07:02:02 -0500
Received: from localhost ([127.0.0.1] ident=stefan)
	by flocke.weilnetz.de with esmtp (Exim 4.69)
	(envelope-from <weil@mail.berlios.de>) id 1LVlsl-0005Dl-Kj
	for qemu-devel@nongnu.org; Sat, 07 Feb 2009 13:01:59 +0100
Message-ID: <498D7837.1090803@mail.berlios.de>
Date: Sat, 07 Feb 2009 13:01:59 +0100
From: Stefan Weil <weil@mail.berlios.de>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] Re: Cutting a new QEMU release
References: <1233825194.6637.4.camel@ecrins.fosdick.home.net>
	<498AF6FC.90803@codemonkey.ws>
In-Reply-To: <498AF6FC.90803@codemonkey.ws>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Reply-To: qemu-devel@nongnu.org
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: qemu-devel@nongnu.org

Anthony Liguori schrieb:
>
> kqemu is unsupported and unmaintained.
>
> Regards,
>
> Anthony Liguori
>

The kvm kernel module could be a good replacement for kqemu
for those running linux on new cpus.

It does not play this role in current linux distributions because
you will need newer versions of kvm which are sometimes
difficult to compile.

It will never play this role for those running "old" cpus.

And it will never play this role on Windows (or is there a kvm
for Windows?). I am surprised that nobody mentions this part
in the discussion.

So even if kqemu is unmaintained, the Qemu developers
should at least maintain the interface.

I'd prefer to have a svn tree with kqemu beside qemu.
Then patches could be sent, and maybe some day there could
be a maintainer, too.

Integration of code from virtualbox could be a way to replace
kqemu, but I don't see this coming in the near future.

Regards
Stefan Weil