From: Marcelo Tosatti <mtosatti@redhat.com>
To: Erik Rull <erik.rull@rdsoftware.de>
Cc: kvm@vger.kernel.org, Gleb Natapov <gleb@redhat.com>
Subject: Re: kvm-77 Excessive Disk Access causes real time clock hang!
Date: Fri, 24 Apr 2009 20:30:27 -0300 [thread overview]
Message-ID: <20090424233027.GD15714@amt.cnet> (raw)
In-Reply-To: <49F1DAF5.2060805@rdsoftware.de>
Erik,
On Fri, Apr 24, 2009 at 05:29:57PM +0200, Erik Rull wrote:
> Hi all,
>
> I'm running kvm-77 and windows xp as guest. When I start the
> defragmentation of the virtualized drive within the windows guest (well
> this is not a fine way, but it should work :-)), the real time clock
> starts hanging - I recognized that because some underlying hardware with
> own timers began to run out of synchronization. I did some research, took
> a stopwatch and measured against the system time. During the measurement
> of ~ 30 seconds I got a difference to the linux time (I just called
> "watch -n 1 date" which should come from the mainboard system time,
> doesn't it?) of ~10 seconds! This was the biggest difference I could
> measure, sometimes it was a little bit less.
Can you try kvm-85 with -rtc-td-hack option? kvm-84 added this option,
from Gleb (CC'ed), to reinject lost RTC interrupts.
> What's happening here? I reduced the io priority and the guest process
> priority to a very low one - it didn't help!
>
> Oh - I'm running the stuff on an Intel Core2Duo T5600 @ 1.83GHz with 2
> Gig of RAM (Windows gets 1.5 Gig), the disk is an SATA with 40 Gigs.
>
> Best regards,
>
> Erik
next prev parent reply other threads:[~2009-04-24 23:31 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 [this message]
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
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=20090424233027.GD15714@amt.cnet \
--to=mtosatti@redhat.com \
--cc=erik.rull@rdsoftware.de \
--cc=gleb@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