From: Erik Rull <erik.rull@rdsoftware.de>
To: Avi Kivity <avi@redhat.com>
Cc: kvm@vger.kernel.org
Subject: Re: kvm-77 Excessive Disk Access causes real time clock hang!
Date: Mon, 27 Apr 2009 01:12:08 +0200 [thread overview]
Message-ID: <49F4EA48.2070208@rdsoftware.de> (raw)
In-Reply-To: <49F43B77.4080102@redhat.com>
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
next prev parent reply other threads:[~2009-04-26 23:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-24 15:29 kvm-77 Excessive Disk Access causes real time clock hang! Erik Rull
2009-04-24 23:30 ` Marcelo Tosatti
2009-04-26 10:46 ` Avi Kivity
2009-04-26 23:12 ` Erik Rull [this message]
2009-04-27 6:27 ` Avi Kivity
2009-04-27 17:19 ` Erik Rull
2009-04-29 8:21 ` Avi Kivity
2009-05-04 19:30 ` Erik Rull
2009-05-04 19:30 ` Erik Rull
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=49F4EA48.2070208@rdsoftware.de \
--to=erik.rull@rdsoftware.de \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox