From mboxrd@z Thu Jan 1 00:00:00 1970 From: Paolo Bonzini Subject: Re: Is kvm-kmod still supported? Date: Tue, 29 Dec 2015 00:16:13 +0100 Message-ID: <5681C2BD.9080009@redhat.com> References: <5681B317.10403@illinois.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit To: "Estrada, Zachary J" , kvm@vger.kernel.org Return-path: Received: from mail-wm0-f47.google.com ([74.125.82.47]:34789 "EHLO mail-wm0-f47.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752566AbbL1XQT (ORCPT ); Mon, 28 Dec 2015 18:16:19 -0500 Received: by mail-wm0-f47.google.com with SMTP id l126so276648473wml.1 for ; Mon, 28 Dec 2015 15:16:18 -0800 (PST) In-Reply-To: <5681B317.10403@illinois.edu> Sender: kvm-owner@vger.kernel.org List-ID: On 28/12/2015 23:09, Estrada, Zachary J wrote: > I've been maintaining a fork for research and tinkering. Is the kvm-kmod > standalone module still supported or should I be using the full Linux > tree? I find kvm-kmod convenient to keep the source independent of the > kernel tree, but I also want to be using the latest and greatest. > > The repository I'm referring to is here: > http://git.kiszka.org/?p=kvm-kmod.git;a=summary > > However, the "next" branch appears to be out of sync with the latest > upstream in the Linux tree. I'm using it occasionally and I have patches that bring it up to date, but only with recent base kernel versions (3.10+ *should* work). Paolo