All of lore.kernel.org
 help / color / mirror / Atom feed
From: Roman Mamedov <rm@romanrm.ru>
To: Alex <alex@bpmit.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: KVM on top of BTRFS
Date: Tue, 12 Jun 2012 13:33:11 +0600	[thread overview]
Message-ID: <20120612133311.58af9d8f@natsu> (raw)
In-Reply-To: <loom.20120612T013031-188@post.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 1538 bytes --]

On Mon, 11 Jun 2012 23:53:34 +0000 (UTC)
Alex <alex@bpmit.com> wrote:

> Running KVM image files on btrfs as of yesterday.
> Used mkfs.btrfs -l 32k -n 32k to create and default options only (no mount
> options bar defaults, so no compression (just asking for trouble!), or
> autodefrag). 3.4.1 official Debian AMD64 kernel. Multi-subvol including root
> with set-default enacted. 32k's adopted per Chris's post.
> 
> Install:
> virt-install --connect qemu:///system -n china -r 256 --disk
> path=/var/lib/libvirt/images/china.img,size=4 -c
> /home/alex/debian-testing-amd64-CD-1.iso --vnc --noautoconsole --os-type linux
> --os-variant debianwheezy --accelerate --network=bridge:br0 --hvm 
> 
> This runs much slower than expected - have done many debian bare minimum
> installs like this before. Can't hear any disk thrashing. Doesn't appear to be
> CPU or memory bound - will double check.


From man kvm:

           cache=cache
               cache is "none", "writeback", "unsafe", "directsync" or
               "writethrough" and controls how the host cache is used to
               access block data.

The default setting is writethrough, can you try writeback, then unsafe, to
see if they help increase performance in your case? AFAIK the default setting
may cause KVM to call sync a bit too often, and sync can be slow on btrfs.

-- 
With respect,
Roman

~~~~~~~~~~~~~~~~~~~~~~~~~~~
"Stallman had a printer,
with code he could not see.
So he began to tinker,
and set the software free."

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  parent reply	other threads:[~2012-06-12  7:33 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
2012-06-12  7:33   ` Roman Mamedov [this message]
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=20120612133311.58af9d8f@natsu \
    --to=rm@romanrm.ru \
    --cc=alex@bpmit.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.