From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andre Przywara Subject: Re: Tracking KVM development Date: Sun, 21 Mar 2010 21:19:33 +0100 Message-ID: <4BA67F55.3060607@amd.com> References: <1f0fa7ae1003210421x734e8c1bid1ad04c0f3c51885@mail.gmail.com> <4BA60FB5.5070609@redhat.com> <1f0fa7ae1003210937h62a1baa1q734692b9a11d30ef@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: kvm@vger.kernel.org To: =?ISO-8859-1?Q?Thomas_L=F8cke?= Return-path: Received: from va3ehsobe005.messaging.microsoft.com ([216.32.180.15]:52704 "EHLO VA3EHSOBE006.bigfish.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1752887Ab0CUUTW convert rfc822-to-8bit (ORCPT ); Sun, 21 Mar 2010 16:19:22 -0400 In-Reply-To: <1f0fa7ae1003210937h62a1baa1q734692b9a11d30ef@mail.gmail.com> Sender: kvm-owner@vger.kernel.org List-ID: Thomas L=F8cke wrote: > On Sun, Mar 21, 2010 at 1:23 PM, Avi Kivity wrote: >> Tracking git repositories and stable setups are mutually exclusive. = If you >> are interested in something stable I recommend staying with the dist= ribution >> provided setup (and picking a distribution that has an emphasis on k= vm). If >> you want to track upstream, use qemu-kvm-0.12.x stable releases and >> kernel.org 2.6.x.y stable releases. If you want to track git reposi= tories, >> use qemu-kvm.git and kvm.git for the kernel and kvm. >=20 > Thanks Avi. >=20 > I will stay with the stable qemu-kvm releases and stable kernel.org > kernel releases from now on. >=20 > I've never heard of any KVM specific distributions. Are you aware of > any? My primary reason for going with Slackware, is because I already > know it. But if there are better choices for a KVM virtualization > host, then I'm willing to switch. Please think twice about that. Every time I wanted to go away from=20 Slackware because of missing packages I ended up with accepting the=20 involved hassle with self-compiling because I could stay with the=20 simplicity and clean design of Slackware. I usually compile my own kernels anyway and use the Slackware kernels=20 only for testing and installation. So I usually do "make oldconfig" on = a=20 stable 2.6.xx.>=3D3 kernel, and am happy with that. QEMU(-kvm) is not a= =20 problem at all, the dependencies are very small and with Slackware[64]=20 13.0 it compiles out of the box with almost all features. I can send yo= u=20 a reasonably configured package (or build-script) if you like. Currently both qemu-kvm-0.12.3 and Linux 2.6.33 work together very well= ,=20 although I usually do only testing and development with KVM and actuall= y=20 "use" it very rarely. So if you need more upper level management tools=20 (like libvirt) I cannot help you on this. Regards, Andre. --=20 Andre Przywara AMD-Operating System Research Center (OSRC), Dresden, Germany Tel: +49 351 488-3567-12