From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: Make QEmu HPET disabled by default for KVM? Date: Sun, 14 Mar 2010 09:05:50 +0200 Message-ID: <4B9C8ACE.4090400@redhat.com> References: <201003111552.54293.sheng@linux.intel.com> <4B98A294.7010104@redhat.com> <20100311190807.GD17264@amt.cnet> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Sheng Yang , kvm@vger.kernel.org, Gleb Natapov To: Marcelo Tosatti Return-path: Received: from mx1.redhat.com ([209.132.183.28]:8121 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751421Ab0CNHFx (ORCPT ); Sun, 14 Mar 2010 03:05:53 -0400 In-Reply-To: <20100311190807.GD17264@amt.cnet> Sender: kvm-owner@vger.kernel.org List-ID: On 03/11/2010 09:08 PM, Marcelo Tosatti wrote: > >> >>> I have kept --no-hpet in my setup for >>> months... >>> >> Any details about the problems? HPET is important to some guests. >> > As Gleb mentioned in the other thread, reinjection will introduce > another set of problems. > > Ideally all this timer related problems should be fixed by correlating > timer interrupts and time source reads. > This still needs reinjection (or slewing of the timer frequency). Correlation doesn't fix drift. > Since one already has to use special timer parameters (-rtc-td-hack, > -no-kvm-pit-reinjection), using -no-hpet for problematic Linux > guests seems fine? > Depends on how common the problematic ones are. If they're common, better to have a generic fix. -- error compiling committee.c: too many arguments to function