From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LV74a-0001mC-Le for qemu-devel@nongnu.org; Thu, 05 Feb 2009 11:27:28 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LV74Y-0001m0-7Q for qemu-devel@nongnu.org; Thu, 05 Feb 2009 11:27:27 -0500 Received: from [199.232.76.173] (port=59571 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LV74Y-0001lx-2W for qemu-devel@nongnu.org; Thu, 05 Feb 2009 11:27:26 -0500 Received: from mx20.gnu.org ([199.232.41.8]:6161) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1LV74X-0005Bn-PK for qemu-devel@nongnu.org; Thu, 05 Feb 2009 11:27:25 -0500 Received: from mail.codesourcery.com ([65.74.133.4]) by mx20.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LV74W-0002bW-8T for qemu-devel@nongnu.org; Thu, 05 Feb 2009 11:27:24 -0500 From: Paul Brook Subject: Re: [Qemu-devel] Re: Cutting a new QEMU release Date: Thu, 5 Feb 2009 16:27:21 +0000 References: <1233825194.6637.4.camel@ecrins.fosdick.home.net> <498AF6FC.90803@codemonkey.ws> <200902050936.49909.rickv@hobi.com> In-Reply-To: <200902050936.49909.rickv@hobi.com> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200902051627.21972.paul@codesourcery.com> 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 On Thursday 05 February 2009, Rick Vernam wrote: > On Thursday 05 February 2009 8:26:04 am Anthony Liguori wrote: > > kqemu is unsupported and unmaintained. > > Interesting. When did it fall into that status? IMHO It's pretty much always been that way. > The Maintainers file shows Fabrice as the maintainer of kqemu. I suppose > that needs to be updated? > > I see Fabrice released 1.4.0pre1 on May 30th, 2008, although I never did > see anything declaring it unsupported (I'm not suggesting it was never > declared, just that I never saw any such declaration). > > Are there any plans to support it in the future? This really is quite a > shock to me, actually. I know qemu has a wide range of uses - but for me > and surely others, virtualization is a primary use. To the best of my > knowledge, kvm requires hardware support - where does this leave the class > of users who need virtualization & don't have hardware virtualization > support? Are we no longer the a target audience of qemu? If not, fine, > but apparently a statement needs to be made... You have the source, you're free to fork and maintain it yourself. In practice Fabice is pretty much the only person who's ever done significant work on kqemu (except maybe some fairly minor host OS porting bits). There's never been a public source repository, so you get to use whatever random tarballs Fabrice leaves lying around. If those don't work, noone really cares. Paul