From: Peter Lieven <pl@kamp.de>
To: Paolo Bonzini <pbonzini@redhat.com>,
Marcelo Tosatti <mtosatti@redhat.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>, agraf@suse.de
Subject: Re: [Qemu-devel] kvmclock_current_nsec: Assertion `time.tsc_timestamp <= migration_tsc'
Date: Tue, 10 Feb 2015 14:58:06 +0100 [thread overview]
Message-ID: <54DA0E6E.1050204@kamp.de> (raw)
In-Reply-To: <54DA0A34.7030109@redhat.com>
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
next prev parent reply other threads:[~2015-02-10 13:58 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-10 9:26 [Qemu-devel] kvmclock_current_nsec: Assertion `time.tsc_timestamp <= migration_tsc' Peter Lieven
2015-02-10 9:49 ` Paolo Bonzini
2015-02-10 10:03 ` Peter Lieven
2015-02-10 10:17 ` Paolo Bonzini
2015-02-10 10:24 ` Peter Lieven
2015-02-10 10:25 ` Paolo Bonzini
2015-02-10 10:30 ` Peter Lieven
2015-02-10 10:47 ` Paolo Bonzini
2015-02-10 10:27 ` Peter Lieven
2015-02-10 10:50 ` Marcelo Tosatti
2015-02-10 12:17 ` Peter Lieven
2015-02-10 12:35 ` Paolo Bonzini
2015-02-10 12:56 ` Peter Lieven
2015-02-10 13:15 ` Paolo Bonzini
2015-02-10 13:31 ` Peter Lieven
2015-02-10 13:40 ` Paolo Bonzini
2015-02-10 13:58 ` Peter Lieven [this message]
2015-02-10 14:24 ` Paolo Bonzini
2015-02-12 15:31 ` Peter Lieven
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=54DA0E6E.1050204@kamp.de \
--to=pl@kamp.de \
--cc=agraf@suse.de \
--cc=mtosatti@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).