From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: qemu-kvm-0.13.0 - winsows 2008 - chkdisk too slow Date: Thu, 06 Jan 2011 11:08:32 +0200 Message-ID: <4D258690.4070904@redhat.com> References: <20110106074822.GB17772@pcnci.linuxbox.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: KVM list , nikola.ciprich@linuxbox.cz To: Nikola Ciprich Return-path: Received: from mx1.redhat.com ([209.132.183.28]:45797 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751319Ab1AFJIp (ORCPT ); Thu, 6 Jan 2011 04:08:45 -0500 In-Reply-To: <20110106074822.GB17772@pcnci.linuxbox.cz> Sender: kvm-owner@vger.kernel.org List-ID: On 01/06/2011 09:48 AM, Nikola Ciprich wrote: > Hi, > I'd like to ask for advice with following problem. > I have windows 2008 terminal server guest running on 2.6.36 x86_64 > host (kvm 0.13.0). > guest has 4GB of RAM, 40GB storage on top of LVM volume and two cores. > So far everything was running fine, but during periodic maintenance > I wanted to force chkdisk after reboot. > So windows started checking disk integrity, but the problem is, that > it's waaay too slow - after ~12 hours, it's still running and seeems > like it'll take ages to finish. > Both CPU cores seem to be fully loaded. > Is there some way I could check why it's taking so long, and fix > it eventually? > can I use kvm_trace to achieve this task? how? Let's start with a few 'kvm_stat -1' snapshots while this is going on. http://git.kernel.org/?p=virt/kvm/qemu-kvm.git;a=blob_plain;f=kvm/kvm_stat;hb=HEAD -- error compiling committee.c: too many arguments to function