From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: strange guest slowness after some time Date: Mon, 09 Mar 2009 12:37:57 +0200 Message-ID: <49B4F185.5020605@redhat.com> References: <49B29705.6000904@wpkg.org> <49B4E7A6.3090601@redhat.com> <49B4EDC9.9020504@wpkg.org> <49B4EE8F.7050001@redhat.com> <49B4F01E.9030402@wpkg.org> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: "kvm@vger.kernel.org" To: Tomasz Chmielewski Return-path: Received: from mx2.redhat.com ([66.187.237.31]:45073 "EHLO mx2.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753050AbZCIKiB (ORCPT ); Mon, 9 Mar 2009 06:38:01 -0400 In-Reply-To: <49B4F01E.9030402@wpkg.org> Sender: kvm-owner@vger.kernel.org List-ID: Tomasz Chmielewski wrote: > Avi Kivity schrieb: >> Tomasz Chmielewski wrote: >>> 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/*. >> >> I meant 'taskset 01 qemu ...' but it wouldn't have helped if it's >> kvmclock. > > It can be done on a running process as well (22906 is the PID of the > affected gue Right, but if the guest is poisoned somehow, this won't help. -- error compiling committee.c: too many arguments to function