From: Zachary J Estrada <zestrad2@illinois.edu>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: <kvm@vger.kernel.org>
Subject: Re: Is kvm-kmod still supported?
Date: Mon, 28 Dec 2015 17:47:33 -0600 [thread overview]
Message-ID: <20151228234733.GA5415@x1> (raw)
In-Reply-To: <5681C2BD.9080009@redhat.com>
On Tue, Dec 29, 2015 at 12:16:13AM +0100, Paolo Bonzini wrote:
>
>
> 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
Got it, found this on github:
https://github.com/bonzini/kvm-kmod.git
Thanks so much!
--Zak
prev parent reply other threads:[~2015-12-28 23:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-28 22:09 Is kvm-kmod still supported? Estrada, Zachary J
2015-12-28 23:16 ` Paolo Bonzini
2015-12-28 23:47 ` Zachary J Estrada [this message]
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=20151228234733.GA5415@x1 \
--to=zestrad2@illinois.edu \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.com \
/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