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 19:03:20 +0200 [thread overview]
Message-ID: <4D4599D8.3070904@redhat.com> (raw)
In-Reply-To: <4D4593CD.2000700@cisco.com>
On 01/30/2011 06:37 PM, David Ahern wrote:
>
> On 01/30/11 06:03, Avi Kivity wrote:
>
> >> 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).
> >
>
> I don't understand. If the host kernel is 2.6.27, qemu-kvm complains and
> refuses to open /dev/kvm. Your options are to upgrade the host kernel or
> use a newer kvm-kmod version.
>
> Are you saying kvm-kmod-2.6.37 is not advisable on 2.6.27? What about
> kvm-kmod-2.6.32.27?
No, that kvm-kmod-2.6.27, or a pure 2.6.27 isn't good. kvm-kmod-2.6.29+
over 2.6.27+ (for mmu notifiers) or a pure 2.6.29+ setup is fine. If
you're careful with overcommit you might get away with a pre 2.6.27 host.
(but take all that with a grain of salt, I haven't run kvm-kmod for a
long while apart from the RHEL 5 version, and I won't recommend anything
outside a supported distro kernel or an active Linux stable/longterm tree).
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2011-01-30 17: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
2011-01-30 16:37 ` David Ahern
2011-01-30 17:03 ` Avi Kivity [this message]
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=4D4599D8.3070904@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).