similar to: [REVIEW ONLY] Ensure atomic creation of a cached appliance

Cached appliances are discovered by their predictable path. Previously we were creating a cached appliance directly in this predictable path. This had at least 2 undesirable effects: * Interrupting appliance creation would leave a corrupt appliance * 2 processes could simultaneously attempt to create the same appliance, causing corruption. This patch causes the cached appliance to be created

Move the "FIXED APPLIANCE" section from libguestfs-make-fixed-appliance(1) to the general guestfs(3), so it's more visible and less hidden in the documentation of a rarely-used tool. Expand the FAQ question about libguestfs without supermin, mentioning the build options needed and pointing to the aforementioned new section. --- appliance/libguestfs-make-fixed-appliance.pod | 28

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 > >

Move the "FIXED APPLIANCE" section from libguestfs-make-fixed-appliance(1) to the "INTERNALS" section of guestfs(3), so it's more visible and less hidden in the documentation of a rarely-used tool. Also slightly improve it. Expand the FAQ question about libguestfs without supermin, mentioning the build options needed and pointing to the aforementioned new section. ---

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

Move the "FIXED APPLIANCE" section from libguestfs-make-fixed-appliance(1) to the general guestfs(3), so it's more visible and less hidden in the documentation of a rarely-used tool. Expand the FAQ question about libguestfs without supermin, mentioning the build options needed and pointing to the aforementioned new section. --- appliance/libguestfs-make-fixed-appliance.pod | 28

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

Hi, this is a prototype of something I've around for some time. Basically it is about adding new appliances in addition to the main one currently used and kept up-to-date automatically: this way it is possible to create new appliances with extra packages, to be used in specific contexts (like virt-rescue, with more network/recovery tools) without filling the main appliance. It's still

# virt-filesystems -v -d 6326ad4e-5805-2ab4-1338-d1dad8c76162 --all libguestfs: libvirt version = 10002 libguestfs: [00000ms] connect to libvirt libguestfs: [00001ms] get libvirt capabilities libguestfs: [00234ms] build appliance libguestfs: [00234ms] create libvirt XML libguestfs: error: error constructing libvirt XML at "xmlTextWriterWriteAttribute (xo, BAD_CAST "file", BAD_CAST

On Thu, Aug 22, Richard W.M. Jones wrote: > On Thu, Aug 22, 2013 at 09:28:36AM +0200, Olaf Hering wrote: > > Why does the toplevel Makefile process appliance/, and creates > > supermin.d during make install, whith configure --disable-appliance? I > > have to double check what actually happens, it seems it causes startup > > failures if the resulting binary packages are

This is largely code motion. --- src/appliance.c | 40 +++++++----------------------------- src/guestfs-internal.h | 1 + src/tmpdirs.c | 55 ++++++++++++++++++++++++++++++++++++++++++++++++++ 3 files changed, 63 insertions(+), 33 deletions(-) diff --git a/src/appliance.c b/src/appliance.c index 2cf6374..d293c2b 100644 --- a/src/appliance.c +++ b/src/appliance.c @@ -48,7 +48,7

On Monday 15 June 2015 15:47:31 Richard W.M. Jones wrote: > On Wed, Jun 10, 2015 at 06:47:44PM +0200, Pino Toscano wrote: > > index e2ee1b5..eebab53 100644 > > --- a/src/guestfs.pod > > +++ b/src/guestfs.pod > > @@ -3540,6 +3540,30 @@ Finally, the child process sends asynchronous messages back to the > > main program, such as kernel log messages. You can register

From: "Richard W.M. Jones" <rjones@redhat.com> AAVMF is an open source UEFI implementation for aarch64 based on OVMF. As aarch64 is heading for requiring UEFI even inside guests, if the AAVMF firmware is installed on the host, use it as a hint that we should boot the guest using AAVMF instead of the default "empty machine". Note this requires very recent AAVMF, libvirt,

Signed-off-by: Hu Tao <hutao@cn.fujitsu.com> --- builder/website/debian.preseed | 2 +- builder/website/index | 120 +++++----- builder/website/index.asc | 120 +++++----- customize/customize_run.mli | 2 +- daemon/mount.c | 2 +- fish/test-file-attrs.sh | 10 +- generator/c.ml | 2 +- guestfs-release-notes.txt | 520

The ELF NEEDED are used to determine guestfsd's library dependencies with help from the dynamic linker and the package manager. This was prompted by Debian bug #972241 which was caused by a libtirpc package renaming in Debian/unstable because the SONAME had been changed. --- appliance/Makefile.am | 26 ++++++++++++++++- appliance/packagelist.in | 62

Thanks Overmind! I had forgotten about the VMware Appliance Page, which has an area for 'community' appliances. I'll work on getting it there. I'll post here again when the appliance is available. regards, Bernardo >As long as it does not exceed a terabyte or 1.5tb or so of download >bandwidth a month, I could host it without issue. Probably something >relating

On Fri, Apr 28, 2017 at 05:03:58PM +0300, Pavel Butsykin wrote: > On 27.04.2017 18:28, Richard W.M. Jones wrote: > > > >On Thu, Apr 27, 2017 at 03:55:10PM +0300, Pavel Butsykin wrote: > >>The flag determines the behavior of working with the appliance, and specifically > >>the choice to use the build supermin appliance or the fixed appliance. If the >

On Wed, Jun 10, 2015 at 06:47:44PM +0200, Pino Toscano wrote: > index e2ee1b5..eebab53 100644 > --- a/src/guestfs.pod > +++ b/src/guestfs.pod > @@ -3540,6 +3540,30 @@ Finally, the child process sends asynchronous messages back to the > main program, such as kernel log messages. You can register a > callback to receive these messages. > > +=head1 FIXED APPLIANCE > +

I'm pleased to announce the latest stable release of libguestfs, a library and a set of tools for reading, writing, managing, inspecting, rescuing, resizing and aligning disk images, and offline and live virtual machines. There are many new features and bug fixes in this release; see the release notes below. You can get libguestfs 1.18.0 from: Main website: http://libguestfs.org Source:

This patch changes libguestfs to use the ext2-based appliance, cached if possible. I've tested this with the alpha version of febootstrap from here: http://koji.fedoraproject.org/koji/buildinfo?buildID=191338 and it at least passes the tests. There are some hacky bits right now: (1) We add the root -drive option last on the command line, then (in the initrd) reverse-search through the