From: Erik Rull <spamfolder@rdsoftware.de>
To: Avi Kivity <avi@redhat.com>
Cc: Erik Rull <erik.rull@rdsoftware.de>, kvm@vger.kernel.org
Subject: Re: kvm-77 Excessive Disk Access causes real time clock hang!
Date: Mon, 04 May 2009 21:30:01 +0200 [thread overview]
Message-ID: <49FF4239.5000608@rdsoftware.de> (raw)
In-Reply-To: <49F80E13.2070806@redhat.com>
Hi Avi,
Avi Kivity wrote:
> Erik Rull wrote:
> The file system is the guest's business. Instead of '-hda /dev/hda2', try
>
> -drive file=/dev/hda2,cache=none
great!
cache=off worked - none caused an error.
The Timing problem is still present but the XP system is now much more
interactive during file access (copy / defrag,...)
I will try out the 84 kvm with the irq-reinjection.
Best regards,
Erik
next prev parent reply other threads:[~2009-05-04 19:30 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
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 [this message]
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=49FF4239.5000608@rdsoftware.de \
--to=spamfolder@rdsoftware.de \
--cc=avi@redhat.com \
--cc=erik.rull@rdsoftware.de \
--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