Doug Goldstein wrote:
> On Tue, Jan 12, 2010 at 12:53 PM, Jan Kiszka <jan.kiszka@xxxxxxxxxxx> wrote:
>> Since kvm-kmod-2.6.32.2 we have an alternative source for recent KVM
>> kernel headers. Use it when available and not overruled by --kerneldir.
>>
>
> Would it be possible to turn this into a configure option? Such that I
> could say ./configure --with-kvm-kmod{=optional/path/to} because
> otherwise this adds a potential automagical dependency onto kvm-kmod
> (i.e. if the user had kvm-kmod installed at the time of build but then
> removed them and went back with their kernel provided version)
I don't see the problem yet. Either the qemu version built against the
previously installed headers will detect during runtime that the loaded
kvm support is restricted or even unsuited and handle this properly. Or
the user will happen to generate a new qemu which lacks the same
features as the installed kvm.
There is only the case that the distribution ships more powerful kvm
modules than their kernel headers advertise. But that's a distribution
bug we can only solve by filing bug reports there and installing
kvm-kmod in the meantime.
Jan
Attachment:
signature.asc
Description: OpenPGP digital signature
