Soren Hansen wrote:
> Well, anyhow, let's focus on getting this fixed, shall we?
>
> The kernel modules shipped in 2.6.24 was causing all sorts of issues, so
> in an effort to fix those, IIRC I grabbed what was in 2.6.25 at the time
> and backported that, so if I were to get this issue fixed, it should be
> sufficient to find anything that touches the kvm clock ABI between
> 2.6.25-rc<whatever I used> and 2.6.25 final. Does that sound about
> right?
guest side: turn off CONFIG_KVM_CLOCK for kernels older than -rc8
host side: either apply the kvmclock fixes or disable support by
removing kvm clock from the capabilities bit mask.
To fix the host you need this one:
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=50d0a0f987b83a8dadb1134d834e35ec410392b5
Also this as dependency to make it build:
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=7af192c954017499ec163bc9dbaaee2e593d7ef2ke
> I'm a bit confused about this, though. I was under the impression that
> for the KVM_CLOCK stuff to work, it'd would have to be in the host *and*
> the guest kernel, but our kernels don't have KVM_CLOCK enabled at all?
Host support doesn't depend on CONFIG_KVM_CLOCK.
HTH,
Gerd
--
http://kraxel.fedorapeople.org/xenner/
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
