similar to: [PATCH] Improve fixed appliance documentation

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

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

thanks for your reply, When I set the debug mode and run "libguestfs-test-tool" the result is: virtTest@06MYRC5:~$ libguestfs-test-tool ************************************************************ * IMPORTANT NOTICE * * When reporting bugs, include the COMPLETE, UNEDITED * output below in your bug report. * ************************************************************

Sorry for the top posting, it's the gmail app behavior. It didn't mention the other aspects because they are not a problem. The only "problem" is the package depency. Cordially Le 11 nov. 2014 19:03, "Pino Toscano" <ptoscano@redhat.com> a écrit : > > Hi, > > (please do not top-reply...) > > On Tuesday 11 November 2014 18:32:10 Mathieu

What I was suggesting, is to let the user manage depencies himself. This is what slackware users are used to do anyway. It means that we should be able to provide an exhaustive list of needed packages on the command line. As the semantic differ from the usual treatment of the PACKAGES arguments of supermin --prepare, this could be managed by a new option implying "do not search or install

On Tue, Apr 07, 2020 at 02:33:20PM +0200, Pino Toscano wrote: > On Tuesday, 7 April 2020 14:18:47 CEST Richard W.M. Jones wrote: > > On Tue, Apr 07, 2020 at 01:25:02PM +0200, Pino Toscano wrote: > > > The important thing is still that that you need to have space for the > > > temporary files somewhere: be it /var/tmp, /mnt/scratch, whatever. > > > Because of

On Thu, Dec 04, 2014 at 04:53:21PM +0800, cuimingwen@incito.com.cn wrote: > Hello， Richard， > I run command as example： " virt-df -d `virsh domuuid 5`" > some errors show : > libguestfs: warning: supermin-helper -f checksum returned a short string > libguestfs: error: cannot find any suitable libguestfs supermin, fixed or old-style appliance on

Hi guys, I've struggled in this error for 1 week and your help is really appreciated. As one EMC software engineer, I need to setup the libguestfs tool in SUSE12 ( SUSE11SP4 is also OK, while SUSE12 is preferred ) to mount some qcow2 image from openstack environment. Then we can read its file system architecture and restore some files. 1. The first thing is we build one SUSE

I download libguestfs from github and fetch to the *origin master*. I tried to build libguestfs in my own linux distro and I followd the http://libguestfs.org/guestfs-building.1.html#using-a-prebuilt-binary-appliance to replace with supermin I download the appliance-1.30.1.tar.xz and appliance-1.30.1.tar.xz.sig and extract the tarball to /home/user/appliance and export

$ libguestfs-test-tool ... libguestfs: launch: version=1.42.0fedora=33,release=5.fc33,libvirt ... libguestfs: build appliance libguestfs: error: cannot find any suitable libguestfs supermin, fixed or old-style appliance on LIBGUESTFS_PATH (search path: /usr/lib/guestfs) ... It appears that this configure test is now failing:

In CentOS 6 with KVM, I have libguestfs-tools installed, but the "virt-xxx" tools like "virt-df" just give, "libguestfs: error: cannot find any suitable libguestfs supermin, fixed or old-style appliance on LIBGUESTFS_PATH (search path: /usr/lib64/guestfs)". What am I missing? All the guests boot and run OK. I just can't get these tools to work.

By passing root=UUID=... to supermin, we make the appliance boot process less sensitive to the non-deterministic process of scanning SCSI disks (of which much more to come). This patch should be tested alongside the supermin patch posted here: https://www.redhat.com/archives/libguestfs/2017-April/msg00174.html which in turn requires this supermin patch series:

Hi all I am trying to run the dockerized version of linaro lava. Unfortunately it is not possible to start libguetsfs inside one of the containers. My settings are: Ubuntu Server 18.04.3, Docker version 18.09.7 running a Debian:stretch based contianer Running libguestfs-test-tool gives me the following output: root at e91c89e0874d:/# libguestfs-test-tool

Hi, all. I've set up an LXC container for various Openstack admin chores, and now I'm being asked to have it used for importing qcow2 images -- on which we want to run utilities like virt-sparsify and virt-sysprep, first. Sadly, when I do that, it dies horribly, e.g., root@openstack-cli:/tmp# virt-sysprep -a cloud-image.qcow2 Examining the guest ... libguestfs: warning:

--- src/supermin.pod | 60 ++++++++++++++++++++++++++++---------------------------- 1 file changed, 30 insertions(+), 30 deletions(-) diff --git a/src/supermin.pod b/src/supermin.pod index f9b7395..53d1b11 100644 --- a/src/supermin.pod +++ b/src/supermin.pod @@ -46,7 +46,7 @@ For example: creates a supermin appliance containing the packages C<bash> and C<coreutils>.

I had some more ideas overnight: (1) Check that libparted0 is installed on the *host*. (2) Try to find out what libraries the parted binary requires on the host and appliance. On the host: ldd /usr/bin/parted On the appliance: virt-rescue --scratch ><rescue> ldd /usr/bin/parted (3) Remove the appliance and recreate it: rm -rf /var/tmp/.guestfs-* libguestfs-test-tool (4)

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

Two (not related to each other) refactorings: Patches 1-12 split configure.ac into smaller files using the m4_include mechanism. Patches 13-15 split out parts of guestfs.pod (ie. guestfs(3)) into three new manual pages: guestfs-hacking(3) - how to extend and contribute to libguestfs guestfs-internals(3) - architecture and internals guestfs-security(3) - security and CVEs Patch 16 is a

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