All of lore.kernel.org
 help / color / mirror / Atom feed
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:47:15 +0100	[thread overview]
Message-ID: <54D9E1B3.50709@redhat.com> (raw)
In-Reply-To: <54D9DDAF.2050200@kamp.de>



On 10/02/2015 11:30, Peter Lieven wrote:
>>>
>> QEMU64 does not resemble any actual processor.  You want the lowest
>> denominator of your cluster, probably Nehalem.
> 
> Ah okay. Normally, I compare the available cpu flags of my cluster
> and pass those flags individually. Maybe I have to revisit that logic.

Seems to be okay, but that work has been already done for you. :)

If you use "-cpu Nehalem,enforce" it will also fail to start on
pre-Nehalem processors.

Paolo

  reply	other threads:[~2015-02-10 10:47 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 [this message]
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=54D9E1B3.50709@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.