public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Jan Kiszka <jan.kiszka@web.de>,
	Marcelo Tosatti <mtosatti@redhat.com>,
	kvm-devel <kvm@vger.kernel.org>
Subject: Re: Installing kernel headers in kvm-kmod
Date: Thu, 10 Dec 2009 15:12:46 +0200	[thread overview]
Message-ID: <4B20F3CE.2070904@redhat.com> (raw)
In-Reply-To: <4B20F27D.3000006@codemonkey.ws>

On 12/10/2009 03:07 PM, Anthony Liguori wrote:
> QEMU 0.12.0-rc1 does not support KVM
> https://bugs.launchpad.net/bugs/494500
>
> Boils down to the fact that 1) we don't include kernel headers in qemu 
> (whereas qemu-kvm does) and 2) kvm-kmod does not install those headers 
> on make install.
>
> I think we've discussed (2) as being the preferred solution.  Does 
> everyone agree with that?  Anyone care to volunteer to make the 
> change? :-)
>

While I definitely agree with (2), for the bug you cite Ubuntu should 
backport KVM_CAP_DESTROY_MEMORY_REGION_WORKS to their kernel (and 
headers).  Distributions shouldn't require kvm-kmod.

-- 
error compiling committee.c: too many arguments to function


  reply	other threads:[~2009-12-10 13:12 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-10 13:07 Installing kernel headers in kvm-kmod Anthony Liguori
2009-12-10 13:12 ` Avi Kivity [this message]
2009-12-10 13:35 ` Jan Kiszka
2009-12-10 14:50   ` Arnd Bergmann
2009-12-10 15:01     ` Avi Kivity
2009-12-10 15:25       ` Arnd Bergmann
2009-12-10 16:42         ` Jan Kiszka
2009-12-10 16:44           ` Avi Kivity
2009-12-10 17:14             ` Jan Kiszka
2009-12-10 20:26               ` Arnd Bergmann
2009-12-10 20:36                 ` Avi Kivity
2009-12-10 21:44       ` Anthony Liguori
2009-12-10 15:01     ` Jan Kiszka

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=4B20F3CE.2070904@redhat.com \
    --to=avi@redhat.com \
    --cc=anthony@codemonkey.ws \
    --cc=jan.kiszka@web.de \
    --cc=kvm@vger.kernel.org \
    --cc=mtosatti@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