All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcelo Tosatti <mtosatti@redhat.com>
To: Peter Lieven <pl@kamp.de>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
	"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 08:50:38 -0200	[thread overview]
Message-ID: <20150210105038.GA32350@amt.cnet> (raw)
In-Reply-To: <54D9CEC9.9040902@kamp.de>

On Tue, Feb 10, 2015 at 10:26:33AM +0100, Peter Lieven wrote:
> Hi,
> 
> while migrating vServers from 2.1.0 to 2.2.0 I see the following assertion that seems to have
> been introduced between 2.1.0 and 2.2.0 trigger on the destination. This happens in a serious
> amount of cases. In most cases it works flawlessly on the second attempt to migrate the vServer
> (same source and same destination).
> 
> Any hints how to debug the root cause?
> 
> Thank you,
> Peter

Peter,

Make sure you have the following commit applied to the host:

commit 7f187922ddf6b67f2999a76dcb71663097b75497
KVM: x86: update masterclock values on TSC writes

  parent reply	other threads:[~2015-02-10 10:52 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 [this message]
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=20150210105038.GA32350@amt.cnet \
    --to=mtosatti@redhat.com \
    --cc=agraf@suse.de \
    --cc=pbonzini@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.