similar to: Re: [PATCH v2 1/2] appliance: search all types of appliances for each path separately

Eric, what do you think of Pavel's analysis and/or suggested fix below? It seems all too plausible to me unfortunately :-( On Fri, May 05, 2017 at 03:46:45PM +0300, Pavel Butsykin wrote: > On 05.05.2017 12:27, Richard W.M. Jones wrote: > > > >Looks good. I'll push this if it passes 'make check && make check-valgrind' > >which I'm currently

On Thu, May 04, 2017 at 02:20:28PM +0300, Pavel Butsykin wrote: > This patch changes appliance search using paths with multiple directories. Now > all appliance checks will be done separately for each directory. For example > if the path LIBGUESTFS_PATH=/a:/b:/c, then all applainces are searched first in > /a, then in /b and then in /c. It allows to flexibly configure the libguestfs

On 05/05/2017 12:07 PM, Richard W.M. Jones wrote: > Eric, what do you think of Pavel's analysis and/or suggested fix > below? It seems all too plausible to me unfortunately :-( > >> There NULL is macros which can be defined as 0 or (void*)0, again in >> accordance with c99: C99 permits: #define NULL 0 but POSIX does not. POSIX _requires_ #define NULL ((void*)0) or

On Tue, Apr 25, 2017 at 03:58:45PM +0300, Pavel Butsykin wrote: > On 25.04.2017 15:11, Richard W.M. Jones wrote: > >On Tue, Apr 25, 2017 at 02:35:26PM +0300, Pavel Butsykin wrote: > >>The patch changes the order of the steps to search for fixed/supermin > >>appliance in accordance with documentation: > >> > >>"If the fixed appliance is found,

On Mon, Dec 03, 2018 at 12:55:58PM -0600, Eric Blake wrote: > A GNU make-ism - but you already mention requiring GNU make in > README. Should we make ./configure error out hard if $MAKE is not > GNU Make, rather than risking someone getting 80% though a build on > BSD make and then choking when it gets here? Yes that would be a good idea as a separate patch. I'm always annoyed

On Fri, Jun 23, 2017 at 04:12:36PM +0300, Pavel Butsykin wrote: > Signed-off-by: Pavel Butsykin <pbutsykin@virtuozzo.com> > --- > m4/guestfs_appliance.m4 | 11 +++++++++++ > 1 file changed, 11 insertions(+) > > diff --git a/m4/guestfs_appliance.m4 b/m4/guestfs_appliance.m4 > index 81c43879f..7e8d28271 100644 > --- a/m4/guestfs_appliance.m4 > +++

On Sun, Mar 13, 2016 at 04:24:53PM +0200, Török Edwin wrote: > Hi, > > I remembered reading about Intel Clear Containers [1], and Hyper/Qboot [2] > that support startup times measured in the hundreds of miliseconds range. > > On an AMD FX(tm)-8350 'guestfish -a /dev/null run' takes ~4s when run the 2nd/3rd time: > real 0m4.152s > user 0m2.120s > sys 0m0.564s

A lot of people ask where they can get virt-p2v & virt-v2v for RHEL or CentOS. All the answers are here: http://libguestfs.org/virt-v2v/ Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com Fedora Windows cross-compiler. Compile Windows programs, test, and build Windows installers.

On Wed, May 29, 2019 at 04:14:06PM +0100, Ioanna Alifieraki wrote: > Hi, > > Is there any chance you will merge the suggested patch? It's this one right? https://www.redhat.com/archives/libguestfs/2019-April/msg00129.html Yes I can push this. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog:

On Mon, Mar 21, 2016 at 04:01:29PM +0100, Kashyap Chamarthy wrote: > https://kashyapc.fedorapeople.org/virt/stdouts/faster-supermin-custom-qemu-appliance-boot-analysis.txt That's good. Next one to try is this Ceph build: http://koji.fedoraproject.org/koji/taskinfo?taskID=13411776 I removed the initialization of Cycles::init (RHBZ#1319483), so it should show some improvements in the

On Fri, Sep 27, 2019 at 11:48:47PM -0500, Eric Blake wrote: > Fixes the fact that clients could not request the maximum string > length except with NBD_OPT_EXPORT_LEN. Updates the testsuite to > match. > > Signed-off-by: Eric Blake <eblake@redhat.com> > --- > server/protocol-handshake-newstyle.c | 12 +++++++----- > tests/test-long-name.sh | 10

In 1.11.1 / git, I have made some changes to the way that you run guestfish, guestmount and the virt tools from the build directory without installing. Firstly you can't just run ./fish/guestfish or ./fuse/guestmount any more and have those programs magically set LIBGUESTFS_PATH. The automagic code was always error-prone and I have removed it. Secondly, all of the run-*-local scripts have

On Tue, Apr 25, 2017 at 06:13:37PM +0300, Pavel Butsykin wrote: > On 25.04.2017 16:04, Richard W.M. Jones wrote: > >Can you see what: > > > > guestfish get-path > > /usr/lib64/guestfs > > >prints? Are you setting LIBGUESTFS_PATH at all? > > > > No. > > # ls /usr/lib64/guestfs > initrd kernel README.fixed root supermin.d > >

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:

This patch series adds support for outputing an ext2-based appliance from febootstrap-supermin-helper. The usage is very simple, you just add '-f ext2' flag and the name of the appliance file that you want to write to. The implementation uses libext2fs, which is a very low level way to create ext2 filesystems from scratch. We'd like to use libguestfs, but that's an obvious

On Thu, Apr 27, 2017 at 03:54:44PM +0300, Pavel Butsykin wrote: [...] > >(2) If the fixed appliance was located somewhere else, you could do: > > > > LIBGUESTFS_PATH=/path/to/somewhere/else:/usr/lib64/guestfs > > export LIBGUESTFS_PATH > > > >and then it would look for the fixed appliance in > >/path/to/somewhere/else and use it. If the fixed

On Thu, Oct 04, 2018 at 01:34:59PM +0100, Richard W.M. Jones wrote: > On Wed, Sep 26, 2018 at 06:36:47PM +0200, Pino Toscano wrote: > > On Friday, 21 September 2018 11:53:52 CEST Richard W.M. Jones wrote: > > > +/** > > > + * Test if the qemu-img info command supports the C<-U> option to > > > + * disable locking. The result is memoized in the handle.

On Mon, Oct 01, 2018 at 04:40:19PM +0200, Pino Toscano wrote: > -o rhv-upload requires python3, and nbdkit with the python3 plugin, so > skip this test if they are not installed. > --- > > v1 is: > https://www.redhat.com/archives/libguestfs/2018-October/msg00008.html > > v2v/test-v2v-o-rhv-upload.sh | 2 ++ > 1 file changed, 2 insertions(+) > > diff --git

On Sat, Nov 23, 2019 at 06:11:47PM +0200, Nir Soffer wrote: > On Sat, Nov 23, 2019 at 3:10 PM Richard W.M. Jones <rjones@redhat.com> wrote: > > > > 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): > > >

On Thu, Jul 27, 2017 at 04:58:52PM +0200, Pino Toscano wrote: > Hi Olaf and Cédric, > > On Monday, 24 July 2017 18:10:12 CEST Richard W.M. Jones wrote: > > Replace GUESTFSD_EXT_CMD with a command line option > > ‘./guestfsd --print-external-commands’ > > This mini-series basically changes the way external programs used in > the appliance are collected; this was done