kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: David Ahern <daahern@cisco.com>
Cc: Asdo <asdo@shiftmail.org>, KVM mailing list <kvm@vger.kernel.org>
Subject: Re: KVM on old kernels pre-2.6.28
Date: Sun, 30 Jan 2011 15:03:08 +0200	[thread overview]
Message-ID: <4D45618C.2060102@redhat.com> (raw)
In-Reply-To: <4D41B4E6.7040106@cisco.com>

On 01/27/2011 08:09 PM, David Ahern wrote:
>
> On 01/27/11 02:55, Avi Kivity wrote:
> >  On 01/26/2011 06:51 PM, Asdo wrote:
> >>  Some time ago in this list it was mentioned that old kernels pre-2.6.28
> >>  don't work well with KVM.
> >>  (in particular we have a machine with 2.6.24)
> >>
> >
> >  pre 2.6.27 kernels don't have mmu notifiers and thus don't handle
> >  overcommit well.  No idea if there's anything wrong with 2.6.27 itself.
>
> The KVM code in the 2.6.27 kernel is broken. qemu-kvm emits:
>
> KVM kernel module broken (DESTROY_MEMORY_REGION).
> Please upgrade to at least kernel 2.6.29 or recent kvm-kmod
> (see http://sourceforge.net/projects/kvm).
>
> You'll need to use newer kvm-kmod versions.

Ah, but that's not a host kernel issue.  So you could have 
kvm-kmod-2.6.37 atop 2.6.27 (still I wouldn't recommend it).

-- 
error compiling committee.c: too many arguments to function


  reply	other threads:[~2011-01-30 13:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-26 16:51 KVM on old kernels pre-2.6.28 Asdo
2011-01-27  9:55 ` Avi Kivity
2011-01-27 18:09   ` David Ahern
2011-01-30 13:03     ` Avi Kivity [this message]
2011-01-30 16:37       ` David Ahern
2011-01-30 17:03         ` Avi Kivity
2011-02-03 14:33   ` Asdo
2011-02-03 14:38     ` Avi Kivity

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=4D45618C.2060102@redhat.com \
    --to=avi@redhat.com \
    --cc=asdo@shiftmail.org \
    --cc=daahern@cisco.com \
    --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;
as well as URLs for NNTP newsgroup(s).