Eino Malinen wrote:
Can you try a bisect?
I confirm having the same trouble with kvm. Bisect with the vanilla kernel
gave the following result:
(f438349...|BISECTING)$ git bisect log
# bad: [8d7bff2d72660d9d60aa371ae3d1356bbf329a09] Linux 2.6.29.1
# good: [8e0ee43bc2c3e19db56a4adaa9a9b04ce885cd84] Linux 2.6.29
git bisect start 'v2.6.29.1' 'v2.6.29' '--' 'arch/x86/kvm/' 'virt/kvm/'
# bad: [f438349efb8247cd0c1d453a4131b1f801bf5691] KVM: VMX: Don't allow
uninhibited access to EFER on i386
git bisect bad f438349efb8247cd0c1d453a4131b1f801bf5691
Are the commits splitted more precisely in kvm.git?
No (and this is pretty fine granularity -- that commit is a one liner).
So 2.6.29 worked and 2.6.29.1 did not? What is your host cpu type? Are
you running an i386 or x86_64 host?
--
error compiling committee.c: too many arguments to function
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
