From: Avi Kivity <avi@redhat.com>
To: Nikola Ciprich <nikola.ciprich@linuxbox.cz>
Cc: Gleb Natapov <gleb@redhat.com>, kvm@vger.kernel.org
Subject: Re: KVM got slow after adding more physical memory to host
Date: Tue, 06 Sep 2011 20:01:47 +0300 [thread overview]
Message-ID: <4E6651FB.3050208@redhat.com> (raw)
In-Reply-To: <20110906163029.GC2152@nik-comp.lan>
On 09/06/2011 07:30 PM, Nikola Ciprich wrote:
> OK, seems like Avi's right, at least the windows guest is not using DMA
> though the question is, why did it got disabled
It can happen due to a timeout, perhaps a temporary load spike.
> and how can I reenable it,
Google knows.
> I'm not experienced that much with XP :(
>
>
> > It is rep/in-out. But why it became noticeable only after adding more
> > physical memory to the host is a mystery.
>
> now that I'm thinking about it, we had similar problem in the past, the windows guest
> was unusably slow, and the whole host was slow as well... upgrading to 0.14.1 seemingly
> solved this issue, but maybe the DMA just got randomly enabled, and now after adding
> the memory (and restarting of course), it just got disabled again?
> but why could this be??
>
I don't think it's related to the memory.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2011-09-06 17:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-06 14:02 KVM got slow after adding more physical memory to host Nikola Ciprich
2011-09-06 15:13 ` Avi Kivity
2011-09-06 15:38 ` Nikola Ciprich
2011-09-06 15:45 ` Avi Kivity
2011-09-06 16:01 ` Nikola Ciprich
2011-09-06 16:06 ` Avi Kivity
2011-09-06 16:06 ` Avi Kivity
2011-09-06 16:10 ` Gleb Natapov
2011-09-06 16:30 ` Nikola Ciprich
2011-09-06 17:01 ` Avi Kivity [this message]
2011-09-06 19:22 ` KVM got slow after adding more physical memory to host - SOLVED Nikola Ciprich
2011-09-08 14:58 ` Michael Tokarev
2011-09-06 16:08 ` KVM got slow after adding more physical memory to host Avi Kivity
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=4E6651FB.3050208@redhat.com \
--to=avi@redhat.com \
--cc=gleb@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=nikola.ciprich@linuxbox.cz \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.