From: "Morten P.D. Stevens" <mstevens@imt-systems.com>
To: Victor Stinner <victor.stinner@haypocalc.com>
Cc: <linux-btrfs@vger.kernel.org>
Subject: Re: Issues with KVM
Date: Fri, 22 Jul 2011 23:03:43 +0200 [thread overview]
Message-ID: <31d58f70e3887e23ad38664e29dda5ee@imt-systems.com> (raw)
In-Reply-To: <4E29D318.7050602@haypocalc.com>
On Fri, 22 Jul 2011 21:44:24 +0200, Victor Stinner wrote:
> Should I try other KVM option (e.g. use another type of image)? Try
> btrfs RAID instead of Linux MD RAID? Try to disable some CPU cores?
> Or
> maybe not using btrfs for KVM images? :-)
Hi,
I would suggest you the following points:
- qemu-img create -f qcow2 -o size=40000000000,preallocation=metadata
vdisk.img
- disk: cache=none
- controller: virtio
Best regards,
Morten
prev parent reply other threads:[~2011-07-22 21:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-22 19:44 Issues with KVM Victor Stinner
2011-07-22 19:59 ` C Anthony Risinger
2011-07-22 20:00 ` C Anthony Risinger
2011-07-23 9:20 ` Victor Stinner
2011-07-25 14:04 ` Victor Stinner
2011-07-25 16:22 ` Christoph Hellwig
2011-07-22 20:44 ` Josef Bacik
2011-07-22 21:03 ` Morten P.D. Stevens [this message]
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=31d58f70e3887e23ad38664e29dda5ee@imt-systems.com \
--to=mstevens@imt-systems.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=victor.stinner@haypocalc.com \
/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;
as well as URLs for NNTP newsgroup(s).