From: Jan Kiszka <jan.kiszka@web.de>
To: Christoph Hellwig <hch@lst.de>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] qemu-img: add FUSE-based image access
Date: Mon, 29 Mar 2010 09:46:30 +0200 [thread overview]
Message-ID: <4BB05AD6.9060408@web.de> (raw)
In-Reply-To: <20100328110248.GA9094@lst.de>
[-- Attachment #1: Type: text/plain, Size: 1300 bytes --]
Christoph Hellwig wrote:
> On Thu, Mar 25, 2010 at 06:52:59PM +0100, Jan Kiszka wrote:
>> This adds the "map" subcommand to qemu-img. It is able to expose the raw
>> content of a disk image via a FUSE filesystem. Both the whole disk can
>> be accessed, e.g. to run partitioning tools against it, as well as
>> individual partitions. This allows to create new filesystems in the
>> image or loop-back mount exiting ones. Using the great mountlo tool
>> from the FUSE collection [1][2], the latter can even be done by non-root
>> users (the former anyway).
>
> Is there a good reason to throw this into qemu-img instead of making
> a separate qemu-fuse or similar tool? It's doing something quite
> different than the rest of qemu-img.
>
qemu-img is the swiss knife for QEMU disk image manipulation (like git
is for everything around a git repository). So, IHMO, mapping the image
content into the host filesystem for further manipulation with standard
tools belongs to this.
If the "map" thing works out for most users, I could even imagine some
helper sub-command "mount" that encapsulates map and mountlo (or some
other unprivileged mounting mechanism). This should make it easier for
users to explore all possibilities they have when working with disk images.
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 257 bytes --]
next prev parent reply other threads:[~2010-03-29 7:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-25 17:52 [Qemu-devel] [PATCH] qemu-img: add FUSE-based image access Jan Kiszka
2010-03-25 20:58 ` Anthony Liguori
2010-03-25 21:46 ` Jan Kiszka
2010-03-25 22:04 ` Anthony Liguori
2010-03-25 22:27 ` Jan Kiszka
2010-03-25 22:54 ` Anthony Liguori
2010-03-26 7:59 ` Jan Kiszka
2010-03-28 11:02 ` Christoph Hellwig
2010-03-29 7:46 ` Jan Kiszka [this message]
2010-03-29 8:57 ` Alexander Graf
2010-03-29 9:37 ` Jan Kiszka
2010-03-29 9:39 ` Alexander Graf
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=4BB05AD6.9060408@web.de \
--to=jan.kiszka@web.de \
--cc=hch@lst.de \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).