From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: kvm-77 Excessive Disk Access causes real time clock hang! Date: Mon, 27 Apr 2009 09:27:29 +0300 Message-ID: <49F55051.1000409@redhat.com> References: <49F1DAF5.2060805@rdsoftware.de> <49F43B77.4080102@redhat.com> <49F4EA48.2070208@rdsoftware.de> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: kvm@vger.kernel.org To: Erik Rull Return-path: Received: from mx2.redhat.com ([66.187.237.31]:57576 "EHLO mx2.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750997AbZD0G1c (ORCPT ); Mon, 27 Apr 2009 02:27:32 -0400 In-Reply-To: <49F4EA48.2070208@rdsoftware.de> Sender: kvm-owner@vger.kernel.org List-ID: Erik Rull wrote: >> Are you using qcow2? In some cases qcow2 will stall the guest cpu. >> >> Note that defragmenting the guest drive may cause the qcow2 file to >> fragment even more, and will certainly increase its size. I >> recommend only defragmenting when using raw storage. > > I don't think so. I created a partition on my host "real" harddrive > and provided this partition to my windows guest. > > If you have an idea, which virtualized drive system could be the > fastest (except giving a complete disk to the guest), your comments > are welcome :-) > > interface: virtio cache: none format: raw, using a partition or logical volume What are you using? -- Do not meddle in the internals of kernels, for they are subtle and quick to panic.