From: Avi Kivity <avi@redhat.com>
To: Nikola Ciprich <extmaillist@linuxbox.cz>
Cc: KVM list <kvm@vger.kernel.org>, nikola.ciprich@linuxbox.cz
Subject: Re: qemu-kvm-0.13.0 - winsows 2008 - chkdisk too slow
Date: Thu, 06 Jan 2011 11:08:32 +0200 [thread overview]
Message-ID: <4D258690.4070904@redhat.com> (raw)
In-Reply-To: <20110106074822.GB17772@pcnci.linuxbox.cz>
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
next prev parent reply other threads:[~2011-01-06 9:08 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-06 7:48 qemu-kvm-0.13.0 - winsows 2008 - chkdisk too slow Nikola Ciprich
2011-01-06 9:03 ` Stefan Hajnoczi
2011-01-06 9:06 ` Nikola Ciprich
2011-01-06 9:08 ` Avi Kivity [this message]
2011-01-06 9:20 ` Nikola Ciprich
2011-01-06 9:27 ` Avi Kivity
2011-01-06 9:30 ` Avi Kivity
2011-01-06 9:42 ` Nikola Ciprich
2011-01-06 10:19 ` Avi Kivity
2011-01-06 10:25 ` Nikola Ciprich
2011-01-06 10:50 ` Avi Kivity
2011-01-06 11:06 ` Daniel P. Berrange
2011-01-06 12:19 ` Nikola Ciprich
2011-01-06 12:18 ` Nikola Ciprich
2011-01-06 13:26 ` Avi Kivity
2011-01-06 13:55 ` Nikola Ciprich
2011-01-06 14:37 ` Avi Kivity
2011-01-06 15:38 ` Nikola Ciprich
2011-01-09 12:36 ` Nikola Ciprich
2011-01-09 12:39 ` Avi Kivity
2011-01-09 13:36 ` Nikola Ciprich
2011-01-09 13:44 ` Nikola Ciprich
2011-01-09 14:13 ` Avi Kivity
2011-01-09 14:13 ` Avi Kivity
2011-01-09 14:27 ` Nikola Ciprich
2011-01-09 14:36 ` Avi Kivity
2011-01-09 15:15 ` Nikola Ciprich
2011-01-09 20:10 ` Nikola Ciprich
2011-01-10 9:23 ` Avi Kivity
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D258690.4070904@redhat.com \
--to=avi@redhat.com \
--cc=extmaillist@linuxbox.cz \
--cc=kvm@vger.kernel.org \
--cc=nikola.ciprich@linuxbox.cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.