From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: KVM on old kernels pre-2.6.28 Date: Sun, 30 Jan 2011 15:03:08 +0200 Message-ID: <4D45618C.2060102@redhat.com> References: <4D405116.2040206@shiftmail.org> <4D41412A.2090001@redhat.com> <4D41B4E6.7040106@cisco.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: Asdo , KVM mailing list To: David Ahern Return-path: Received: from mx1.redhat.com ([209.132.183.28]:54308 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753804Ab1A3NDO (ORCPT ); Sun, 30 Jan 2011 08:03:14 -0500 In-Reply-To: <4D41B4E6.7040106@cisco.com> Sender: kvm-owner@vger.kernel.org List-ID: 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