From: Anthony Liguori <anthony@codemonkey.ws>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel][PATCH] qemu-fuse
Date: Wed, 27 Aug 2008 11:28:37 -0500 [thread overview]
Message-ID: <48B580B5.8030804@codemonkey.ws> (raw)
In-Reply-To: <ED2414DB5FBBCF4FA66ECE71F290E9A28EB872@EXVBE011-2.exch011.intermedia.net>
Shahar Frank wrote:
> Hi All,
>
> The attached is a small utility to mount qemu images as pseudo
> partition files. It can be very useful to access (rw) images from the
> host.
> I would not use it for production, but it seems to be stable.
>
Heh, quite similar to:
http://hg.codemonkey.ws/qemu-img-mount/file/9f11265882b3/qemu-img-mount.diff
So this was my first approach to solving this problem that I ended up
abandoning in favor of qemu-nbd (which is now in the tree). The main
limitation I found with fuse is that by default (and it takes a lot to
change this), fuse filesystems are unreadable by root. This means that
you cannot easily mount -oloop something in a fuse filesystem.
What I really wanted, was the ability to say something like:
qemu-img mount -p1 foo.img /mnt
and it would Just Work. The only two options I found that could make
this work is:
1) disable the root readable limitation in fuse, this has to be done
globally and I suspect is unlikely to be done by distros.
2) add support to qemu-img-mount to use filesystems libraries like
libe2fs to read and present the filesystem contents. This has the
advantage of working entirely as the user who issues the command but has
the disadvantage of requiring a lot of effort without being able to
support all filesystems that Linux supports.
So that's why I settled on qemu-nbd.
Regards,
Anthony Liguori
next prev parent reply other threads:[~2008-08-27 16:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-27 15:50 [Qemu-devel][PATCH] qemu-fuse Shahar Frank
2008-08-27 16:28 ` Anthony Liguori [this message]
2008-08-27 17:02 ` Luca Bigliardi
2008-08-27 18:00 ` Anthony Liguori
2008-08-27 18:10 ` Daniel P. Berrange
2008-08-27 18:59 ` Jamie Lokier
2008-08-28 8:03 ` Shahar Frank
2008-08-28 9:27 ` [Qemu-devel][PATCH] block level testing/execersing utility Shahar Frank
2008-08-28 9:47 ` Samuel Thibault
2008-08-28 12:22 ` Shahar Frank
2008-08-28 20:11 ` Anthony Liguori
2008-08-27 18:00 ` [Qemu-devel][PATCH] qemu-fuse Jamie Lokier
2008-08-28 21:05 ` [Qemu-devel] Re: [PATCH] qemu-fuse Szabolcs Szakacsits
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=48B580B5.8030804@codemonkey.ws \
--to=anthony@codemonkey.ws \
--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).