From mboxrd@z Thu Jan 1 00:00:00 1970 From: "David S. Ahern" Subject: Re: RHEL5.5, 32-bit VM repeatedly locks up due to kvmclock Date: Fri, 23 Apr 2010 17:21:11 -0600 Message-ID: <4BD22B67.6030800@cisco.com> References: <4BD1D406.1040508@cisco.com> <201004231539.32205.iggy@theiggy.com> <4BD213AA.7070601@redhat.com> <4BD21459.9010903@cisco.com> <20100423222135.GB18563@c3sl.ufpr.br> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: Zachary Amsden , Brian Jackson , kvm-devel To: BRUNO CESAR RIBAS Return-path: Received: from sj-iport-1.cisco.com ([171.71.176.70]:27740 "EHLO sj-iport-1.cisco.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750910Ab0DWXVM (ORCPT ); Fri, 23 Apr 2010 19:21:12 -0400 In-Reply-To: <20100423222135.GB18563@c3sl.ufpr.br> Sender: kvm-owner@vger.kernel.org List-ID: On 04/23/2010 04:21 PM, BRUNO CESAR RIBAS wrote: > > Could you try hpet? I had similar problem with multicore and multiCPU (per > mother board) [even with constant_tsc]. > > Since I changed the guest to hpet i had no more problems. It's stable in the sense of no lockups yet, but is a much slower time source from a gettimeofday perspective compared to tsc and jiffies (based on speed jiffies appears to be tsc-based). David > >> >> David >> >>> >>> Zach >> -- >> To unsubscribe from this list: send the line "unsubscribe kvm" in >> the body of a message to majordomo@vger.kernel.org >> More majordomo info at http://vger.kernel.org/majordomo-info.html >