From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dor Laor Subject: Re: can we hope a stable version in the near future? Date: Wed, 19 Nov 2008 17:23:20 +0200 Message-ID: <49242F68.9030400@redhat.com> 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> <4923E380.6050307@lfarkas.org> Reply-To: dlaor@redhat.com Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: Avi Kivity , KVM , Uri Lublin To: Farkas Levente Return-path: Received: from mx2.redhat.com ([66.187.237.31]:35672 "EHLO mx2.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752772AbYKSPXJ (ORCPT ); Wed, 19 Nov 2008 10:23:09 -0500 In-Reply-To: <4923E380.6050307@lfarkas.org> Sender: kvm-owner@vger.kernel.org List-ID: Farkas Levente wrote: > 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? > > As always you'll have the option of using kvm as a kernel module. So even if the stable branch is based on 2.6.28, you can always take the kvm bits through 'make -C kernel sync LINUX=PATH' in the userspace.