From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: Re: [kvm] Re: [kvm] Re: [kvm] Re: tcpdump locks up kvm host for a while. Date: Sun, 02 Oct 2011 19:21:08 +0200 Message-ID: <4E889D84.9050506@redhat.com> References: <20110928020137.GK21223@stodi.digitalkingdom.org> <20110929190712.GT11528@stodi.digitalkingdom.org> <20110930190321.GA2414@nik-comp.lan> <20110930221908.GF20043@stodi.digitalkingdom.org> <20111001073643.GA2253@nik-comp.lan> <20111002004540.GJ20043@stodi.digitalkingdom.org> <4E889A1B.4030004@redhat.com> <20111002170728.GE30948@stodi.digitalkingdom.org> <4E889B8A.7010201@redhat.com> <20111002171346.GF30948@stodi.digitalkingdom.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Nikola Ciprich , kvm@vger.kernel.org To: Robin Lee Powell Return-path: Received: from mx1.redhat.com ([209.132.183.28]:35327 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751596Ab1JBRVg (ORCPT ); Sun, 2 Oct 2011 13:21:36 -0400 In-Reply-To: <20111002171346.GF30948@stodi.digitalkingdom.org> Sender: kvm-owner@vger.kernel.org List-ID: On 10/02/2011 07:13 PM, Robin Lee Powell wrote: > On Sun, Oct 02, 2011 at 07:12:42PM +0200, Avi Kivity wrote: > > On 10/02/2011 07:07 PM, Robin Lee Powell wrote: > > >On Sun, Oct 02, 2011 at 07:06:35PM +0200, Avi Kivity wrote: > > >> On 10/02/2011 02:45 AM, Robin Lee Powell wrote: > > >> >I'm afraid clocksource=hpet didn't help much; after about 24 hours > > >> >up, tcpdump hung the machine for for about 10 seconds. That may or > > >> >may not be better than usual; I haven't been timing things > > >> >precisely. My suspicion is that it's slightly better, but it's > > >> >still not great. > > >> > > > >> >Also: > > >> > > > >> >rlpowell@vrici> dmesg | grep -i clock > > >> >[ 0.000000] Command line: ro root=/dev/vda2 rd_NO_LUKS rd_NO_LVM rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYTABLE=us console=ttyS0,115200 clocksource=hpet > > >> >[ 0.000000] kvm-clock: Using msrs 12 and 11 > > >> >[ 0.000000] kvm-clock: cpu 0, msr 0:1b567c1, boot clock > > >> >[ 0.000000] kvm-clock: cpu 0, msr 0:5fc137c1, primary cpu clock > > >> >[ 0.000000] Kernel command line: ro root=/dev/vda2 rd_NO_LUKS rd_NO_LVM rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYTABLE=us console=ttyS0,115200 clocksource=hpet > > >> >[ 0.000000] hpet clockevent registered > > >> >[ 0.260136] Switching to clocksource hpet > > >> >[ 1.009393] rtc_cmos 00:01: setting system clock to 2011-10-01 07:49:50 UTC (1317455390) > > >> >[ 1.821905] Refined TSC clocksource calibration: 2394.030 MHz. > > >> >[60555.473797] Clocksource tsc unstable (delta = -42950328292 ns) > > >> > > > >> >(note the last line) > > >> > > > >> > > >> Do you get a similar error with kvmclock? > > > > > >I don't think I did, no. I'm not completely certain, but pretty > > >sure. > > > > > > > Then let's try to understand why it doesn't work with kvmclock. > > I'd love to. Suggestions? > Well, any messages? Alternatively, detailed instructions to reproduce? -- error compiling committee.c: too many arguments to function