From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Ahern Subject: Re: KVM on old kernels pre-2.6.28 Date: Sun, 30 Jan 2011 09:37:33 -0700 Message-ID: <4D4593CD.2000700@cisco.com> References: <4D405116.2040206@shiftmail.org> <4D41412A.2090001@redhat.com> <4D41B4E6.7040106@cisco.com> <4D45618C.2060102@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: Asdo , KVM mailing list To: Avi Kivity Return-path: Received: from sj-iport-6.cisco.com ([171.71.176.117]:42336 "EHLO sj-iport-6.cisco.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751023Ab1A3Qhf (ORCPT ); Sun, 30 Jan 2011 11:37:35 -0500 In-Reply-To: <4D45618C.2060102@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: 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? David