[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] kvmclock_current_nsec: Assertion `time.tsc_timestamp <=

From: Peter Lieven
Subject: Re: [Qemu-devel] kvmclock_current_nsec: Assertion `time.tsc_timestamp <= migration_tsc'
Date: Thu, 12 Feb 2015 16:31:38 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0

Am 10.02.2015 um 11:50 schrieb Marcelo Tosatti:
On Tue, Feb 10, 2015 at 10:26:33AM +0100, Peter Lieven wrote:

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,

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

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

Thanks for the pointer. It seems that has fixed the assertion issue.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]