From: Andre Przywara <andre.przywara@amd.com>
To: "Thomas Løcke" <thomas.granvej6@gmail.com>
Cc: kvm@vger.kernel.org
Subject: Re: Tracking KVM development
Date: Sun, 21 Mar 2010 21:19:33 +0100 [thread overview]
Message-ID: <4BA67F55.3060607@amd.com> (raw)
In-Reply-To: <1f0fa7ae1003210937h62a1baa1q734692b9a11d30ef@mail.gmail.com>
Thomas Løcke wrote:
> On Sun, Mar 21, 2010 at 1:23 PM, Avi Kivity <avi@redhat.com> wrote:
>> Tracking git repositories and stable setups are mutually exclusive. If you
>> are interested in something stable I recommend staying with the distribution
>> provided setup (and picking a distribution that has an emphasis on kvm). 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 repositories,
>> use qemu-kvm.git and kvm.git for the kernel and kvm.
>
> Thanks Avi.
>
> I will stay with the stable qemu-kvm releases and stable kernel.org
> kernel releases from now on.
>
> 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
Slackware because of missing packages I ended up with accepting the
involved hassle with self-compiling because I could stay with the
simplicity and clean design of Slackware.
I usually compile my own kernels anyway and use the Slackware kernels
only for testing and installation. So I usually do "make oldconfig" on a
stable 2.6.xx.>=3 kernel, and am happy with that. QEMU(-kvm) is not a
problem at all, the dependencies are very small and with Slackware[64]
13.0 it compiles out of the box with almost all features. I can send you
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,
although I usually do only testing and development with KVM and actually
"use" it very rarely. So if you need more upper level management tools
(like libvirt) I cannot help you on this.
Regards,
Andre.
--
Andre Przywara
AMD-Operating System Research Center (OSRC), Dresden, Germany
Tel: +49 351 488-3567-12
next prev parent reply other threads:[~2010-03-21 20:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-21 11:21 Tracking KVM development Thomas Løcke
2010-03-21 12:23 ` Avi Kivity
2010-03-21 16:37 ` Thomas Løcke
2010-03-21 16:42 ` Avi Kivity
2010-03-21 20:09 ` Alexander Graf
2010-03-21 20:16 ` Michael Tokarev
2010-03-21 20:19 ` Andre Przywara [this message]
2010-03-21 20:37 ` Thomas Løcke
2010-03-21 23:23 ` Asdo
2010-03-22 12:20 ` Kenni Lund
2010-03-21 20:50 ` Zdenek Kaspar
-- strict thread matches above, loose matches on Subject: below --
2010-03-22 16:33 Tomasz Chmielewski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4BA67F55.3060607@amd.com \
--to=andre.przywara@amd.com \
--cc=kvm@vger.kernel.org \
--cc=thomas.granvej6@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox