From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: KVM on old kernels pre-2.6.28 Date: Thu, 03 Feb 2011 16:38:43 +0200 Message-ID: <4D4ABDF3.906@redhat.com> References: <4D405116.2040206@shiftmail.org> <4D41412A.2090001@redhat.com> <4D4ABCC8.4060300@shiftmail.org> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: KVM mailing list To: Asdo Return-path: Received: from mx1.redhat.com ([209.132.183.28]:34232 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751689Ab1BCOiv (ORCPT ); Thu, 3 Feb 2011 09:38:51 -0500 In-Reply-To: <4D4ABCC8.4060300@shiftmail.org> Sender: kvm-owner@vger.kernel.org List-ID: On 02/03/2011 04:33 PM, Asdo wrote: > On 01/27/2011 10:55 AM, Avi Kivity wrote: > > ... Using kvm-kmod allows you to run a newer kvm on an older kernel ... > > ok thanks > > Regarding this: I can't find the kmod version requirements for every KVM > version. I don't think there is an exhaustive list. > What happens if the kernel module version I'm running is too old for the > KVM I'm trying to run? Will it fail at startup giving an error, or I > won't be warned and then weird things will happen sometime during runtime? > If it's the latter, can I at least be sure that always installing the > latest kvm-kmod will not do harm to any KVM, even if the KVM is older? There is no warranty. -- error compiling committee.c: too many arguments to function