From mboxrd@z Thu Jan  1 00:00:00 1970
From: Erik Rull <erik.rull@rdsoftware.de>
Subject: Re: kvm-77 Excessive Disk Access causes real time clock hang!
Date: Mon, 27 Apr 2009 01:12:08 +0200
Message-ID: <49F4EA48.2070208@rdsoftware.de>
References: <49F1DAF5.2060805@rdsoftware.de> <49F43B77.4080102@redhat.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: kvm@vger.kernel.org
To: Avi Kivity <avi@redhat.com>
Return-path: <kvm-owner@vger.kernel.org>
Received: from moutng.kundenserver.de ([212.227.126.177]:54027 "EHLO
	moutng.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1751056AbZDZXMZ (ORCPT <rfc822;kvm@vger.kernel.org>);
	Sun, 26 Apr 2009 19:12:25 -0400
In-Reply-To: <49F43B77.4080102@redhat.com>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

Hi Avi,

Avi Kivity 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 :-)

Best regards,

Erik