From mboxrd@z Thu Jan 1 00:00:00 1970 From: Farkas Levente Subject: Re: can we hope a stable version in the near future? Date: Wed, 19 Nov 2008 10:59:28 +0100 Message-ID: <4923E380.6050307@lfarkas.org> References: <4917525D.709@lfarkas.org> <49180D1D.9000409@redhat.com> <491811B4.6040700@lfarkas.org> <492046F3.900@redhat.com> <49233C85.6070807@lfarkas.org> <4923DEF8.6040309@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: Avi Kivity , KVM , Uri Lublin To: dlaor@redhat.com Return-path: Received: from fg-out-1718.google.com ([72.14.220.152]:25341 "EHLO fg-out-1718.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752477AbYKSJ7d (ORCPT ); Wed, 19 Nov 2008 04:59:33 -0500 Received: by fg-out-1718.google.com with SMTP id 19so2784486fgg.17 for ; Wed, 19 Nov 2008 01:59:31 -0800 (PST) In-Reply-To: <4923DEF8.6040309@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: Dor Laor wrote: >>>> on the other hand the real question are you plan to somehow stabilize >>>> any of the following release in the near future? in the last 1.5 years >>>> we wait for this. or you currently not recommend and not plan to use >>>> kvm >>>> in production? it's also an option but would be useful to know. in this >>>> case we (and probably many others) switch to xen, virtualbox, vmware or >>>> anything else as a virtualization platform. >>>> >>> kvm is used in production on several products. Just not the kvm-nn >>> releases I make. The production versions of kvm are backed by testing, >>> which makes all the difference. Slapping a 'stable' label over a >>> release doesn't make it so. >>> >> >> there are many open source project which has stable and devel >> versions:-) actually almost all projects have a stable release along >> with the devel version. but kvm has not any in the last few years, >> that's why i think it's high time to stabilize 'a' version ie. frozen >> feature list and fix all known bugs. >> > You're right about the need for stable release, that's the idea of the > 'maint' branches. > maint/2.6.26 for both kernel and userspace is stable (using userspace > irqchip). > Now we'll stabilize another user/kernel pair based on 2.6.28 that's a good news:-) but does this means there will be a new kvm-x.y.z release and i can build the userspace from it _and_ build a kmod for eg. the latest rhel-5's kernel-2.6.18-92.1.18.el5? ie. i'll be able to install it on rhel-5 a kvm and kvm-kmod and it'll work? or it'll just run on the not even released 2.6.28 kernel? and what is the relationship between maint release and kvm-nn and the next stable release? is there a tarball for the current maint release? and the same question here can i build a kmod and userspace from that for rhel-5? -- Levente "Si vis pacem para bellum!"