From: Paolo Bonzini <pbonzini@redhat.com>
To: Peter Lieven <pl@kamp.de>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Cc: mtosatti@redhat.com, agraf@suse.de
Subject: Re: [Qemu-devel] kvmclock_current_nsec: Assertion `time.tsc_timestamp <= migration_tsc'
Date: Tue, 10 Feb 2015 11:25:52 +0100 [thread overview]
Message-ID: <54D9DCB0.8030407@redhat.com> (raw)
In-Reply-To: <54D9DC74.1020502@kamp.de>
On 10/02/2015 11:24, Peter Lieven wrote:
>>>
>> First of all (but unrelated to the bug) do not use "-cpu qemu64" with
>> KVM.
>
> I remember there was an issue with kvm64 anytime in the past, but this
> is ages ago I think. I will change that for new vserver starts. What
> (which flag) is the exact issue with qemu64 vs. kvm64
QEMU64 does not resemble any actual processor. You want the lowest
denominator of your cluster, probably Nehalem.
Paolo
next prev parent reply other threads:[~2015-02-10 10:26 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 [this message]
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
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=54D9DCB0.8030407@redhat.com \
--to=pbonzini@redhat.com \
--cc=agraf@suse.de \
--cc=mtosatti@redhat.com \
--cc=pl@kamp.de \
--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).