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 11:54:27 +0100 Message-ID: <49B4F563.1080903@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> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: "kvm@vger.kernel.org" To: Avi Kivity Return-path: Received: from mx03.syneticon.net ([78.111.66.105]:52203 "EHLO mx03.syneticon.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753248AbZCIKyg (ORCPT ); Mon, 9 Mar 2009 06:54:36 -0400 In-Reply-To: <49B4F185.5020605@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: 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. >>> 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. Yep, it seems poisoned. I'll start the guest again in the evening, will add it a e1000 card. If the problem reappears, it would be good to see if it affect only virtio card or not (I've never seen this issue on a guest which doesn't use virtio drivers - so far at least). -- Tomasz Chmielewski http://wpkg.org