similar to: nbdkit Windows binaries

When virtualizing a physical machine ("P2V"), the conversion step is done by virt-v2v, but there is a small GUI / front end component called virt-p2v which has to run on the source physical machine in a special environment. http://libguestfs.org/virt-p2v.1.html#network-setup Because the nature of the problem is that we want to virtualize old machines, this means virt-p2v sometimes

Context: https://bugzilla.redhat.com/show_bug.cgi?id=1837809#c28 https://rwmj.wordpress.com/2020/03/21/new-nbdkit-remote-tmpfs-tmpdisk-plugin/ http://libguestfs.org/nbdkit-tmpdisk-plugin.1.html https://github.com/libguestfs/nbdkit/blob/0632acc76bfeb7d70d3eefa42fc842ce6b7be4f8/plugins/tmpdisk/tmpdisk.c#L182 I did a bit of testing to try to see if this is really feasible, and yes I think it is.

Hi Pino: I've suppressed some OCaml and libosinfo valgrind errors in virt-v2v. The remaining valgrind errors are here: http://oirase.annexia.org/tmp/v2vvg/ They all seem to be basically the same. But I couldn't work out if these are expected leaks in the libosinfo code (in which case we should suppress them), or if they are actual bugs because we are missing a true destructor here:

I'm pleased to announce the release of nbdkit 1.20, a high performance plugin-based Network Block Device (NBD) server. https://en.wikipedia.org/wiki/Network_block_device Key features of nbdkit: * Multithreaded NBD server written in C with good performance. * Minimal dependencies for the basic server. * Liberal license (BSD) allows nbdkit to be linked to proprietary libraries or

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

On Fri, Aug 09, 2019 at 02:58:18AM +0300, Nir Soffer wrote: > On Thu, Aug 8, 2019 at 5:05 PM Richard W.M. Jones <rjones@redhat.com> wrote: > > > > + if disk.status == types.DiskStatus.OK: > > > + debug("finalized after %s seconds", time.time() - > > start) > > > > Maybe this was the real error? (using ,

On Fri, Oct 25, 2013 at 01:14:04PM -0700, Scott Baker wrote: > On 10/25/2013 12:56 PM, Richard W.M. Jones wrote: > > F20 - it's in the beta now (as of yesterday). > > > > Rich. > > Wow this has a lot of dependencies :) Two questions... Let's put this on the mailing list so others can help. > Do I need OCaml installed? > Where does guestfs_protocol.x come

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 Fri, Nov 22, 2019 at 02:55:31PM -0600, Eric Blake wrote: > Unrelated side topic: in your recent addition of eval.sh, you > wondered if we should promote it to a full-blown plugin rather than > just an example script. But reading 'man nbdkit-sh-plugin', there > is no mention of turning an executable script into a full-blown > plugin via a shebang, the way that python

On Mon, Sep 26, 2016 at 02:18:02PM +0200, Carl-Daniel Hailfinger wrote: > Hi, > > has anyone ever run "make check" from nbd against nbdkit with a python > plugin? I usually get segfaults during such a run, and sometimes various > other errors happen before the segfault, suggesting that some memory > corruption is underway. > AFAICS a pure python plugin should not be

On Wed, Jul 22, 2020 at 12:58:07PM -0500, Eric Blake wrote: [...] This is fine, but there is a minor thing: > docs/nbdkit-protocol.pod | 2 +- In the original patch I removed this hunk from nbdkit-protocol.pod: @@ -5,7 +5,7 @@ nbdkit - which parts of the NBD protocol nbdkit supports =head1 SYNOPSIS nbdkit [-n|--newstyle] [--mask-handshake MASK] [--no-sr] [-o|--oldstyle] -

On Tue, Sep 11, 2018 at 03:02:47PM -0500, Eric Blake wrote: [Lots of issues] I'll fix all these, thanks. > > files="blocksize1.img blocksize1.log blocksize1.sock blocksize1.pid > >@@ -72,27 +73,13 @@ cleanup () > > trap cleanup INT QUIT TERM EXIT ERR > > # Run two parallel nbdkit; to compare the logs and see what changes. > >-nbdkit -P blocksize1.pid -U

On Tue, Jun 25, 2019 at 09:35:11PM -0500, Eric Blake wrote: > The existing --run '$nbd' outputs an older form that differs between > libguestfs and qemu, and which is not always a valid URI. For > historical compatibility, we probably can't change that; but we can > instead add a new '$uri' that outputs a valid URI. Note that the > libguestfs '$nbd' TCP

I’m pleased to announce the next stable release of nbdkit. This release concentrates on numerous feature enhancements - see the release notes 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 in C with good

Some thoughts on nbdkit and libnbd in RHEL Advanced Virtualization 8.3.0. We have two bugs open for rebases: * https://bugzilla.redhat.com/show_bug.cgi?id=1809231 "Rebase nbdkit to at least 1.18+ in RHEL AV 8.3.0" * https://bugzilla.redhat.com/show_bug.cgi?id=1809674 "Rebase libnbd for RHEL-AV 8.3.0" The rules for rebasing are (well, these are _my_ rules): (1) Must not

On Sat, Apr 04, 2020 at 05:02:37PM -0500, Eric Blake wrote: > This is what I've been playing with in response to my earlier question > about what to do with 'nbdkit -s sh -' > (https://www.redhat.com/archives/libguestfs/2020-April/msg00032.html) > > I'm still open to ideas on a better name, and/or whether adding > <stdbool.h> to our public include files is

On Tue, Oct 27, 2020 at 01:48:31PM -0500, Eric Blake wrote: > On 10/27/20 1:38 PM, Richard W.M. Jones wrote: > > This library proved useful in nbdkit where we need to construct an > > array or vector of arbitrary objects, with the easy ability to append > > at the end. Wherever code uses realloc(3) to build an array of > > objects is a candidate for replacement by this

The error is the following libtool: link: (cd .libs/nbdkit-perl-plugin.lax/libutils.a && ar x "/c/Users/yifangu/Documents/devel/nbdkit/plugins/perl/../../common/utils/.libs/libutils.a") libtool: link: ar cru .libs/nbdkit-perl-plugin.a .libs/nbdkit_perl_plugin_la-perl.o .libs/nbdkit-perl-plugin.lax/libutils.a/libutils_la-cleanup-nbdkit.o

On Sat, Nov 23, 2019 at 01:42:15AM +0200, Nir Soffer wrote: > On Fri, Nov 22, 2019 at 9:55 PM Richard W.M. Jones <rjones@redhat.com> wrote: > > +def pread(h, count, offset, flags): > > + assert flags == 0 > > + return h['disk'][offset:offset+count] > > Very nice and simple test plugin! > > But this returns always a bytearray, which is also

On Tue, Nov 06, 2018 at 09:02:17AM +0000, Richard W.M. Jones wrote: > Finally about the list of failing tests: > > https://pastebin.com/1PFG85DS > > Mostly these are because of the old qemu-io binary. The qemu-io -f > option was added 4 years ago :-/ so it could be time to upgrade. FWIW this turns out to be a problem in RHEL 7 as well :-( I worked around it (in RHEL 7