From: dima <dolenin@parallels.com>
To: <linux-btrfs@vger.kernel.org>
Subject: Re: KVM on top of BTRFS
Date: Tue, 12 Jun 2012 10:08:17 +0900 [thread overview]
Message-ID: <4FD69681.4000404@parallels.com> (raw)
In-Reply-To: <loom.20120612T013031-188@post.gmane.org>
On 06/12/2012 08:53 AM, Alex wrote:
> Matthew Hawn <steamraven <at> yahoo.com> writes:
>> What are the recommendations for running KVM images on BTRFS systems using
> kernel 3.4? I saw older
>> posts on the web complaining about poor performance, but I know a lot of work
> has gone into btrfs since then.
>> There also seemed to be the nocow option, but I didn't find anything that
> said it actualy helped.
I don't think it is about the kernel version, but rather about choosing
the right option for KVM.
I am running KVM via libvirt on btrfs with lzo compression, autodefrag,
inode and space cache for quite some time. Yes, I did set nocow for the
directory with images. I have no proof that it actually helps with disk
images, but being set for the build directory my build time is down 5
minutes.
I used raw virtio images with no caching. I guess this is the key if we
talk about disk I/O. The performance looks fine, though I only use it
for testing.
The last time I tried to install WinXP on KVM it was a disaster. But I
guess I did not choose the right options, nor did I install virtio
drivers inside the guest.
VirtualBox still outperforms KVM on btrfs in my view.
best
next prev parent reply other threads:[~2012-06-12 1:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-11 23:22 KVM on top of BTRFS Matthew Hawn
2012-06-11 23:53 ` Alex
2012-06-12 1:08 ` dima [this message]
2012-06-12 7:33 ` Roman Mamedov
2012-06-12 15:39 ` Alex
2012-06-12 15:45 ` Alex
2012-06-12 20:33 ` steamraven
2012-06-13 21:42 ` Ernst Sjöstrand
2012-06-13 21:47 ` steamraven
2012-06-15 20:10 ` steamraven
2012-06-12 14:48 ` Hubert Kario
2012-06-12 15:43 ` Alex
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=4FD69681.4000404@parallels.com \
--to=dolenin@parallels.com \
--cc=linux-btrfs@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 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.