|
From: | Peter Lieven |
Subject: | Re: [Qemu-devel] kvmclock_current_nsec: Assertion `time.tsc_timestamp <= migration_tsc' |
Date: | Tue, 10 Feb 2015 11:30:07 +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:25 schrieb Paolo Bonzini:
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. kvm64QEMU64 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. Peter
[Prev in Thread] | Current Thread | [Next in Thread] |