|
From: | Peter Lieven |
Subject: | Re: [Qemu-devel] kvmclock_current_nsec: Assertion `time.tsc_timestamp <= migration_tsc' |
Date: | Tue, 10 Feb 2015 14:58:06 +0100 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 |
Am 10.02.2015 um 14:40 schrieb Paolo Bonzini:
On 10/02/2015 14:31, 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. Is that supposed to work? Peter
[Prev in Thread] | Current Thread | [Next in Thread] |