similar to: nbdkit -c /dev/nbdX option

(This email is largely me just thinking aloud ... So ideas welcome!) For the RISC-V builders (http://fedora.riscv.rocks) I'm using an NBD disk to host the heavily used /var/lib/mock build directory. This is because the build machines have only SD-cards as local disk and SD is both slow and unreliable. The builders (NBD clients) are set up with an /etc/rc.d/rc.local file which runs these

On Sat, Nov 07, 2015 at 12:21:29AM -0600, Jason Pepas wrote: > Hi, > > So I've been hacking together an nbdkit plugin (similar to the "file" > plugin, but it splits the file up into chunks): > https://github.com/pepaslabs/nbdkit-chunks-plugin > > I got it to the point of being a working prototype. Then I threw it > onto a raspberry pi, which it turns out

Hi, So I've been hacking together an nbdkit plugin (similar to the "file" plugin, but it splits the file up into chunks): https://github.com/pepaslabs/nbdkit-chunks-plugin I got it to the point of being a working prototype. Then I threw it onto a raspberry pi, which it turns out only has a 50/50 shot of fallocate() working correctly. I'm checking the return code of

I’m pleased to announce the next stable release of nbdkit. This release concentrates on performance and fuzzing, along with numerous other enhancements (full list below). NBD — Network Block Device — is a protocol for accessing Block Devices (hard disks and disk-like things) over a Network. nbdkit is a toolkit for creating NBD servers. The key features are: * Multithreaded NBD server written

On Thu, May 28, 2020 at 12:24:22AM +0000, Eric Wheeler wrote: > On Mon, 15 Oct 2018, Nir Soffer wrote: > > On Sat, Oct 13, 2018 at 9:45 PM Eric Wheeler <nbd@lists.ewheeler.net> wrote: > > Hello all, > > > > It might be neat to attach ISOs to KVM guests via websockets.  Basically > > the  browser would be the NBD "server" and an

[adding nbdkit readers] On 10/13/18 1:39 PM, Eric Wheeler wrote: > Hello all, > > It might be neat to attach ISOs to KVM guests via websockets. Basically > the browser would be the NBD "server" and an NBD client would run on the > hypervisor, then use `virsh change-media vm1 hdc --insert /dev/nbd0` could > use an ISO from my desk to boot from. Are you using qemu as

On Thu, 28 May 2020, Richard W.M. Jones wrote: > On Thu, May 28, 2020 at 12:24:22AM +0000, Eric Wheeler wrote: > > On Mon, 15 Oct 2018, Nir Soffer wrote: > > > On Sat, Oct 13, 2018 at 9:45 PM Eric Wheeler <nbd@lists.ewheeler.net> wrote: > > > Hello all, > > > > > > It might be neat to attach ISOs to KVM guests via websockets. 

I would really like to release a new stable nbdkit (1.8) soon. The reasons are not only because of the many great new features (which I summarise below) but also a few practical reasons: - Dropping mandatory [key=].. (ie. "magic config key") for many plugin parameters makes nbdkit much easier to use and easier to describe to potential users. - Demonstrated utility of log filter

Going back to the original email from 2018: > It might be neat to attach ISOs to KVM guests via websockets.  Basically > the  browser would be the NBD "server" and an NBD client would run on the > hypervisor, then use `virsh change-media vm1 hdc --insert /dev/nbd0` could > use an ISO from my desk to boot from. > > Here's an HTML5 open file example: >

This creates filesystems on demand. A client simply connects with a desired export name and a new export is created. The export is persistent (until deleted by the server admin), and clients may disconnect and reconnect. In some respects this is similar to the nbdkit-tmpdisk-plugin, or nbdkit-file-plugin with the dir= option. --- plugins/ondemand/nbdkit-ondemand-plugin.pod | 190 ++++++

On Mon, 15 Oct 2018, Nir Soffer wrote: > On Sat, Oct 13, 2018 at 9:45 PM Eric Wheeler <nbd@lists.ewheeler.net> wrote: > Hello all, > > It might be neat to attach ISOs to KVM guests via websockets.  Basically > the  browser would be the NBD "server" and an NBD client would run on the > hypervisor, then use `virsh change-media vm1 hdc

[adding qemu list] On 5/29/20 4:37 AM, Richard W.M. Jones wrote: > Going back to the original email from 2018: > >> It might be neat to attach ISOs to KVM guests via websockets.  Basically >> the  browser would be the NBD "server" and an NBD client would run on the >> hypervisor, then use `virsh change-media vm1 hdc --insert /dev/nbd0` could >> use

On 10/12/19 9:21 AM, Richard W.M. Jones wrote: > This program allows you to turn a network block device source into a > FUSE filesystem containing a virtual file: > > $ nbdkit memory 128M > $ mkdir mp > $ nbdfuse mp/ramdisk nbd://localhost & > $ ls -l mp > total 0 > -rw-rw-rw-. 1 rjones rjones 134217728 Oct 12 15:09 ramdisk > $ dd

This can be used for creating temporary disks to thin clients, as a kind of "remote tmpfs". See also: https://www.redhat.com/archives/libguestfs/2020-March/msg00134.html --- plugins/data/nbdkit-data-plugin.pod | 1 + plugins/file/nbdkit-file-plugin.pod | 1 + plugins/linuxdisk/nbdkit-linuxdisk-plugin.pod | 7 +- plugins/memory/nbdkit-memory-plugin.pod |

Modern distributions are moving toward a common boot scheme called "The Boot Loader Specification". This patch enables syslinux to parse the drop-in files that are defined by this new specification. Link to documentation of the options added to syslinux by this patch: https://drive.google.com/uc?export=download&id=1nuRISVJeE1whYggFURywoQFpPzc6s1MC MD5 (syslinux-bls1.txt) =

On 11/21/2017 03:21 PM, Richard W.M. Jones wrote: > This works OK on x86_64, but fails on our fast new Amberwing (aarch64) > machine. I've attached the test-suite.log file, but I'm not very sure > what's going wrong from that. > I'll see what I can spot... > FAIL: test-parallel-file.sh > =========================== > > read 1/1 bytes at offset 0 > 1

If we bump NBDKIT_API_VERSION, we have forcefully made older nbdkit reject all plugins that opt to the newer API: $ nbdkit ./plugins/nbd/.libs/nbdkit-nbd-plugin.so --dump-plugin nbdkit: ./plugins/nbd/.libs/nbdkit-nbd-plugin.so: plugin is incompatible with this version of nbdkit (_api_version = 2) But with a bit of finesse, we can make opting in to FUA support orthogonal to NBDKIT_API_VERSION, by

The docs are a lot more useful with a graphic showing how to wire together nbdkit as a bridge from old-to-new. The converse, bridging new-to-old, is best deferred until I add support for the nbd plugin connecting to a TCP socket. It is also worth mentioning use of nbdkit filters (after all, qemu-nbd 4.0 was able to deprecate its --partition option by pointing to 'nbdkit --filter=partition nbd

qemu-nbd defaults to permitting only a single NBD client. Of course, you can run qemu-nbd -t to work around it, but other servers may have similar restrictions, at which point nbdkit's nbd plugin can provide the automatic fanout to multiple clients via a single server link. Note that the shared=true parameter makes the previously-added retry=N parameter more useful, as it is much easier to

If nbdkit has a bug (such as the nbd-standalone bug fixed in the previous commit), qemu-io ends up waiting forever rather than realizing that if the server disappears unexpectedly then qemu-io should quit. So add timeouts so the testsuite will flag the problem instead of hang (tested by reordering this commit before the previous). It's trickier than I expected: from the command line,