From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LVYQz-0004Li-SW for qemu-devel@nongnu.org; Fri, 06 Feb 2009 16:40:25 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LVYQx-0004Jn-FB for qemu-devel@nongnu.org; Fri, 06 Feb 2009 16:40:25 -0500 Received: from [199.232.76.173] (port=44354 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LVYQx-0004JV-6j for qemu-devel@nongnu.org; Fri, 06 Feb 2009 16:40:23 -0500 Received: from mr01.hansenet.de ([213.191.74.10]:55104) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LVYQw-00027b-M2 for qemu-devel@nongnu.org; Fri, 06 Feb 2009 16:40:22 -0500 Received: from exactcode.de (85.183.32.143) by mr01.hansenet.de (7.3.132) id 4967D2550030E9C5 for qemu-devel@nongnu.org; Fri, 6 Feb 2009 22:40:20 +0100 Received: from [82.113.106.17] (helo=[10.73.153.107]) by exactcode.de with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.54) id 1LVYQt-0006tL-9D for qemu-devel@nongnu.org; Fri, 06 Feb 2009 21:40:20 +0000 Message-ID: <498CAFED.4010502@exactcode.com> Date: Fri, 06 Feb 2009 22:47:25 +0100 From: =?ISO-8859-1?Q?Ren=E9_Rebe?= 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> <200902050936.49909.rickv@hobi.com> <200902051627.21972.paul@codesourcery.com> <498B380E.5090603@codemonkey.ws> <1233917676.6637.39.camel@ecrins.fosdick.home.net> <498C5DCC.3060106@exactcode.de> <498C6F83.9010404@codemonkey.ws> In-Reply-To: <498C6F83.9010404@codemonkey.ws> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: Quoted-Printable Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Anthony Liguori wrote: > Ren=E9 Rebe wrote: >> >> Hi, >>> >> Indeed. Though I used KVM for the past months to do Linux development >> and system testing / integration I had a use case for kqemu (non-VT CP= U) >> just this week and was surprised to find quite "old" kqemu release=20 >> just build >> and work for booth 2.6.26 and 2.6.28. And so far there was no problem=20 >> with >> it. >> >> While I have no problem having it long time ported to the KVM interfac= e, >> just declaring some quite useful and functional piece of open source w= ork >> obsolete and unsupported quite drastic. This work should be not be los= t >> so easily. >=20 > I think you misunderstand. Noone is claiming that kqemu is no longer=20 > being supported. Quite rather, we're simply stating it's never been=20 > supported. >=20 > It started as a binary kernel module, impossible to support within the=20 > QEMU community. While Fabrice has open sourced kqemu, it's never been=20 > included in QEMU. It's not maintained by the current QEMU maintainers=20 > and not supported by the current QEMU maintainers. I know about the history pretty well. Btw. is Farbrice still actively working on Qemu related code these days? > It's essentially a separate project. Well - depends. The user-space part always was in Qemu, but the kernel module apparently is a little left aside. However, this should not stop us from improving the situation instead of letting it bitrott. --=20 Ren=E9 Rebe - ExactCODE GmbH - Europe, Germany, Berlin http://exactcode.de | http://t2-project.org | http://rene.rebe.name