[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH v2 00/20] block/export: Allow exporting BDSs via FUSE
From: |
Kevin Wolf |
Subject: |
Re: [PATCH v2 00/20] block/export: Allow exporting BDSs via FUSE |
Date: |
Thu, 15 Oct 2020 14:01:01 +0200 |
Am 22.09.2020 um 12:49 hat Max Reitz geschrieben:
> Based-on: <20200907182011.521007-1-kwolf@redhat.com>
> (“block/export: Add infrastructure and QAPI for block exports”)
>
> (Though its patch 16 needs a s/= \&blk_exp_nbd/= drv/ on top.)
>
> v1: https://lists.nongnu.org/archive/html/qemu-block/2019-12/msg00451.html
>
> Branch: https://github.com/XanClic/qemu.git fuse-exports-v2
> Branch: https://git.xanclic.moe/XanClic/qemu.git fuse-exports-v2
>
>
> Hi,
>
> Ever since I found out that you can mount FUSE filesystems on regular
> files (not just directories), I had the idea of adding FUSE block
> exports to qemu where you can export block nodes as raw images. The
> best thing is that you’d be able to mount an image on itself, so
> whatever format it may be in, qemu lets it appear as a raw image (and
> you can then use regular tools like dd on it).
>
> The performance is quite bad so far, but we can always try to improve it
> if the need arises. For now I consider it mostly a cute feature to get
> easy access to the raw contents of image files in any format (without
> requiring root rights).
>
> In this version (as opposed to v1 linked above), I integrated the FUSE
> export code into Kevin’s proposed common infrastructure for block
> exports.
Patches 5-16, 19 and 20:
Reviewed-by: Kevin Wolf <kwolf@redhat.com>
- Re: [PATCH v2 00/20] block/export: Allow exporting BDSs via FUSE,
Kevin Wolf <=