Re: [Qemu-devel] kvmclock_current_nsec: Assertion `time.tsc_timestamp <= migration_tsc'

[Paolo Bonzini <pbonzini@redhat.com>]

On 10/02/2015 14:58, Peter Lieven wrote:
>>
>>>> Yes, but it is still not ready.  It only works with 3.18 and 3.16.
>>> Okay, but for testing I will use 3.19 with the patch for testing if the
>>> assertion disappears?!
>> If you use 3.19 in the host, you don't need kvm-kmod.
>>
>> If you use 3.19 with kvm-kmod, you can use origin/next but only if your
>> host kernel is 3.16 or 3.18.
> 
> Ah okay. I currently have to use 3.13 on the host. The kvm-kmod with
> branch origin/next
> compiles just fine with the linux submodule at v3.19.

The buildbot (http://buildbot.kiszka.org/kvm-kmod/builders/3-next) tells
me that it shouldn't have compiled :) but maybe you have a more recent
3.13 stable release than the buildbot.  So if it compiles, you can use
it to test.

Paolo