From: Marcelo Tosatti <mtosatti@redhat.com>
To: "Alberto Treviño" <alberto@byu.edu>
Cc: "kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: Avoiding I/O bottlenecks between VM's
Date: Fri, 19 Sep 2008 15:41:46 -0300 [thread overview]
Message-ID: <20080919184146.GA12928@dmt.cnet> (raw)
In-Reply-To: <200809191126.09889.alberto@byu.edu>
Hi Alberto,
On Fri, Sep 19, 2008 at 11:26:09AM -0600, Alberto Treviño wrote:
> I am using KVM 69 and kernel 2.6.25.17 to host several VM's in a large
> server. So far, everything has been great. Except I'm adding a Windows
> Server VM that will run a SQL Server database. A few times I've noticed
> that I/O becomes a bottleneck for the VM and Windows VM freezes for a few
> seconds. Oh well, no biggie. Except, every so often, these I/O bottlenecks
> start to affect other VM's and they freeze as well for a few seconds. I
> don't really care of one VM does so much I/O that it freezes itself
> temporarily. I just don't want I/O bottlenecks on one VM to affect other
> VM's.
>
> My questions are:
>
> 1. Is this a problem anyone else has experienced and has it been fixed in a
> later KVM release?
>
> 2. I'm using the CFQ scheduler. Would the deadline scheduler do a better
> job?
>
> 3. Any other suggestions to improve this problem?
Are you using filesystem backed storage for the guest images or direct
block device storage? I assume there's heavy write activity on the
guests when these hangs happen?
ext3 with ordered data mode has latency issues on fsync.
next prev parent reply other threads:[~2008-09-19 18:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-19 17:26 Avoiding I/O bottlenecks between VM's Alberto Treviño
2008-09-19 18:41 ` Marcelo Tosatti [this message]
2008-09-19 18:53 ` Alberto Treviño
2008-09-19 19:14 ` Javier Guerra
2008-09-19 19:53 ` Marcelo Tosatti
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=20080919184146.GA12928@dmt.cnet \
--to=mtosatti@redhat.com \
--cc=alberto@byu.edu \
--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