From: Jim Fehlig <jfehlig@suse.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: xen-devel@lists.xensource.com,
Ian Campbell <Ian.Campbell@citrix.com>,
Chunyan Liu <cyliu@suse.com>
Subject: Re: [PATCH] vhd-util create: add -C|nocow option
Date: Thu, 21 Nov 2013 17:57:38 -0700 [thread overview]
Message-ID: <528EAC02.9010009@suse.com> (raw)
In-Reply-To: <21134.7091.735293.78218@mariner.uk.xensource.com>
Ian Jackson wrote:
> Ian Campbell writes ("Re: [Xen-devel] [PATCH] vhd-util create: add -C|nocow option"):
>
>> On Thu, 2013-11-21 at 15:46 +0800, Chunyan Liu wrote:
>>
>>> Add '-C' (nocow) option to vhd-util create.
>>>
>>> Btrfs has terrible performance when hosting VM images, even more when the guest
>>> in those VM are also using btrfs as file system. One way to mitigate this bad
>>> performance is to turn off COW attributes on VM files (since having copy on
>>> write for this kind of data is not useful). According to 'chattr' manpage, NOCOW
>>> could be set to new or empty file only on btrfs, so add a option here so that
>>> users could have a chance to set NOCOW to a vhd image.
>>>
>> Is there not some btrfs (or generic) utility which could be used to do
>> this after image creation rather than trying to build it in to every
>> utility which creates an image file?
>>
>
> This may seem like a daft question, but why do we even have a vhd
> utility in our tree ? Is there not some vhd tools package that this
> should be in ?
>
Newer qemu-img supports vhd and vhdx right? Is there even a need for
this tool at all anymore?
Regards,
Jim
next prev parent reply other threads:[~2013-11-22 0:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-21 7:46 [PATCH] vhd-util create: add -C|nocow option Chunyan Liu
2013-11-21 9:39 ` Ian Campbell
2013-11-21 14:41 ` Ian Jackson
2013-11-21 14:51 ` Ian Campbell
2013-11-21 14:59 ` Ian Jackson
2013-11-21 15:01 ` Ian Campbell
2013-11-22 0:57 ` Jim Fehlig [this message]
2013-11-22 3:42 ` Chunyan Liu
2013-11-22 16:09 ` Jim Fehlig
-- strict thread matches above, loose matches on Subject: below --
2013-11-21 7:48 Chunyan Liu
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=528EAC02.9010009@suse.com \
--to=jfehlig@suse.com \
--cc=Ian.Campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=cyliu@suse.com \
--cc=xen-devel@lists.xensource.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 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.