From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tomasz Chmielewski Subject: Re: strange guest slowness after some time Date: Mon, 09 Mar 2009 12:37:10 +0100 Message-ID: <49B4FF66.8040609@wpkg.org> References: <49B29705.6000904@wpkg.org> <49B4E7A6.3090601@redhat.com> <49B4EDC9.9020504@wpkg.org> <49B4EE8F.7050001@redhat.com> <49B4F01E.9030402@wpkg.org> <49B4F185.5020605@redhat.com> <49B4F563.1080903@wpkg.org> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit To: Avi Kivity , "kvm@vger.kernel.org" Return-path: Received: from mx03.syneticon.net ([78.111.66.105]:57767 "EHLO mx03.syneticon.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750840AbZCILhQ (ORCPT ); Mon, 9 Mar 2009 07:37:16 -0400 In-Reply-To: <49B4F563.1080903@wpkg.org> Sender: kvm-owner@vger.kernel.org List-ID: Tomasz Chmielewski schrieb: > Avi Kivity schrieb: > >>>>>> I'm guessing there's a problem with timers or timer interrupts. >>>>>> >>>>>> What is the host cpu? >>>>> >>>>> 4 entries like this in /proc/cpuinfo: >>>>> >>>>> processor : 3 >>>>> vendor_id : AuthenticAMD >>>>> cpu family : 15 >>>>> model : 65 >>>>> model name : Dual-Core AMD Opteron(tm) Processor 2212 >>>>> >>>> >>>> That's probably the kvmclock issue that hit older AMDs. It was >>>> fixed in kvm-84, please try that. >>> >>> It is kvm-84, I have it running since Saturday (but I had this issue >>> with kvm-83 as well). >>> >> >> And the problem continues? >> >> What's your current clocksource (in the guest)? Does changing it help? >> >> See /sys/devices/system/clocksource/clocksource0/*. > > It was kvm-clock. > I tried changing it to acpi_pm, jiffies, tsc, but it made no difference. Actually, I don't think that I checked tsc, because when I changed to jiffies, the time has stopped: # echo jiffies > /sys/devices/system/clocksource/clocksource0/current_clocksource # date Mon Mar 9 12:29:00 CET 2009 # date Mon Mar 9 12:29:00 CET 2009 # date Mon Mar 9 12:29:00 CET 2009 # date Mon Mar 9 12:29:00 CET 2009 # date Mon Mar 9 12:29:00 CET 2009 And I couldn't change to anything else any more: # echo tsc > /sys/devices/system/clocksource/clocksource0/current_clocksource # cat /sys/devices/system/clocksource/clocksource0/current_clocksource jiffies # echo kvm-clock > /sys/devices/system/clocksource/clocksource0/current_clocksource # cat /sys/devices/system/clocksource/clocksource0/current_clocksource jiffies So I had to kill the guest and start it again (the above is reproduced on another, "non-poisoned" guest). -- Tomasz Chmielewski http://wpkg.org