From: Hanna Reitz <hreitz@redhat.com>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [qemu-web PATCH] Add a blog post about FUSE block exports
Date: Fri, 20 Aug 2021 09:56:54 +0200 [thread overview]
Message-ID: <46a68d5c-cfc1-e521-8c6b-90eb74c85ede@redhat.com> (raw)
In-Reply-To: <YR6FauCbECxehubc@stefanha-x1.localdomain>
On 19.08.21 18:23, Stefan Hajnoczi wrote:
> On Thu, Aug 19, 2021 at 12:25:01PM +0200, Hanna Reitz wrote:
>> This post explains when FUSE block exports are useful, how they work,
>> and that it is fun to export an image file on its own path so it looks
>> like your image file (in whatever format it was) is a raw image now.
>>
>> Signed-off-by: Hanna Reitz <hreitz@redhat.com>
>> ---
>> You can also find this patch here:
>> https://gitlab.com/hreitz/qemu-web fuse-blkexport-v1
>>
>> My first patch to qemu-web, so I hope I am not doing anything overly
>> stupid here (adding SVGs with extremely long lines comes to mind)...
>> ---
>> _posts/2021-08-18-fuse-blkexport.md | 488 ++++++++++++++++++++++
>> screenshots/2021-08-18-block-graph-a.svg | 2 +
>> screenshots/2021-08-18-block-graph-b.svg | 2 +
>> screenshots/2021-08-18-block-graph-c.svg | 2 +
>> screenshots/2021-08-18-block-graph-d.svg | 2 +
>> screenshots/2021-08-18-block-graph-e.svg | 2 +
>> screenshots/2021-08-18-root-directory.svg | 2 +
>> screenshots/2021-08-18-root-file.svg | 2 +
>> 8 files changed, 502 insertions(+)
>> create mode 100644 _posts/2021-08-18-fuse-blkexport.md
>> create mode 100644 screenshots/2021-08-18-block-graph-a.svg
>> create mode 100644 screenshots/2021-08-18-block-graph-b.svg
>> create mode 100644 screenshots/2021-08-18-block-graph-c.svg
>> create mode 100644 screenshots/2021-08-18-block-graph-d.svg
>> create mode 100644 screenshots/2021-08-18-block-graph-e.svg
>> create mode 100644 screenshots/2021-08-18-root-directory.svg
>> create mode 100644 screenshots/2021-08-18-root-file.svg
> Great! Two ideas:
>
> It would be nice to include a shoutout to libguestfs and mention that
> libguestfs avoids exposing the host kernel's file systems and partion
> code to untrusted disk images. If you don't mount the image then the
> FUSE export has similar security properties.
Oh, right! Absolutely.
Though now I do wonder why one would actually want to use QEMU’s FUSE
exports then...
Looks like the performance isn’t as bad as I claimed (for me around
1.5G/s for reading/writing from/to a raw image on tmpfs), so perhaps
that’s one point. Another is probably that FUSE exports are better
suited when you actually want access to the whole image. I guess.
> This is a long blog post. One idea is to show a quickstart
> qemu-storage-daemon FUSE export command-line in the beginning before
> explaining all the details. That way people who just want to see what
> this is about can get an idea without learning all the background first.
Sounds good, will do. Thanks!
Hanna
next prev parent reply other threads:[~2021-08-20 7:58 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-19 10:25 [qemu-web PATCH] Add a blog post about FUSE block exports Hanna Reitz
2021-08-19 10:37 ` Philippe Mathieu-Daudé
2021-08-19 11:00 ` Hanna Reitz
2021-08-19 11:09 ` Philippe Mathieu-Daudé
2021-08-19 11:17 ` Hanna Reitz
2021-08-19 16:23 ` Stefan Hajnoczi
2021-08-20 7:56 ` Hanna Reitz [this message]
2021-08-20 9:21 ` Daniel P. Berrangé
2021-08-20 14:27 ` Stefan Hajnoczi
2021-08-22 13:18 ` Thomas Huth
2021-08-23 8:30 ` Hanna Reitz
2021-08-23 8:49 ` Thomas Huth
2021-08-19 18:22 ` Klaus Kiwi
2021-08-20 9:03 ` Hanna Reitz
2021-08-20 21:24 ` Eric Blake
2021-08-23 8:23 ` Hanna Reitz
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=46a68d5c-cfc1-e521-8c6b-90eb74c85ede@redhat.com \
--to=hreitz@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.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).