From: Avi Kivity <avi@redhat.com>
To: Nikola Ciprich <nikola.ciprich@linuxbox.cz>
Cc: kvm@vger.kernel.org
Subject: Re: KVM got slow after adding more physical memory to host
Date: Tue, 06 Sep 2011 18:45:58 +0300 [thread overview]
Message-ID: <4E664036.20308@redhat.com> (raw)
In-Reply-To: <20110906153801.GA2152@nik-comp.lan>
On 09/06/2011 06:38 PM, Nikola Ciprich wrote:
> Hello Avi,
> thanks for quick reply!
>
> > How many guests in there?
> two currently (one x86_64 centos, one winXP), with more, the box get even more unresponsive.
>
> >
> > Please post a trace as per http://www.linux-kvm.org/page/Tracing.
> here it goes:
> http://nelide.cz/nik/trace.dat.bz2
404
>
> >
> > Please post /proc/mtrr and /proc/iomem.
> [root@virtualbox ~]# cat /proc/mtrr
> reg00: base=0x000000000 ( 0MB), size=16384MB, count=1: write-back
> reg01: base=0x400000000 (16384MB), size= 4096MB, count=1: write-back
> reg02: base=0x500000000 (20480MB), size= 1024MB, count=1: write-back
> reg03: base=0x0c0000000 ( 3072MB), size= 1024MB, count=1: uncachable
>
>
These seem fine - all your memory is write-back.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2011-09-06 15:46 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 [this message]
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
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=4E664036.20308@redhat.com \
--to=avi@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.