On Sun, Mar 14, 2010 at 09:05:50AM +0200, Avi Kivity wrote: > 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. > But only when all time sources are synchronised and correlated with interrupts we can slew time frequency without guest noticing (and only if guest disables NTP) > >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 -- Gleb. -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
