public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark McLoughlin <markmc@redhat.com>
To: kelu@kelu.dk
Cc: kvm@vger.kernel.org
Subject: Re: Questions about relation between kernel version and KVM userspace version
Date: Fri, 23 Jan 2009 09:34:02 +0000	[thread overview]
Message-ID: <1232703242.5115.68.camel@blaa> (raw)
In-Reply-To: <39583.1232668043@kelu.dk>

On Fri, 2009-01-23 at 00:47 +0100, Kenni Lund wrote:

>  I've been wondering about something for a while: How does the version
> of the kernel module and the version of the KVM userspace relate? Eg.
> if you run with a newer 2.6.27-2.6.28 kernel with the modules
> included, will you then benefit from using the modules from the latest
> KVM release together with the latest KVM userspace, or isn't it worth
> the effort?

There are a number of ways of thinking about this:

  * if you want to help out with KVM development and testing, using the
    latest released kvm.ko with your currently installed kernel might be
    a good idea. If you want to get really hard-core, use Avi's kernel
    git tree.

  * if you just want some KVM feature that isn't in your currently 
    installed kernel, the latest released kvm.ko might make sense.

  * if your main concern is stability, use an unmodified kernel release
    and stable updates - e.g. 2.6.27.x or 2.6.28.x

Which version of kvm-userspace/qemu you use is a very different story -
unless you have a very old kernel version, just use the latest release
kvm/qemu release.

Cheers,
Mark.


      parent reply	other threads:[~2009-01-23  9:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-22 23:47 Questions about relation between kernel version and KVM userspace version Kenni Lund
2009-01-23  1:39 ` Sheng Yang
2009-01-23  9:34 ` Mark McLoughlin [this message]

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=1232703242.5115.68.camel@blaa \
    --to=markmc@redhat.com \
    --cc=kelu@kelu.dk \
    --cc=kvm@vger.kernel.org \
    /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