search for: supermin_modules

SUPERMIN_KERNEL and SUPERMIN_MODULES don't work to guestfish. Since guestfish sets --if-newer parameter to supermin, so the environment variables are not used under the following conditions. - the output directory exists and, - the dates of both input files and package database are older than the output To solve that, re...

On Monday, 4 March 2019 12:18:58 CET Masayoshi Mizuma wrote: > SUPERMIN_KERNEL and SUPERMIN_MODULES don't work to guestfish. > > Since guestfish sets --if-newer parameter to supermin, so the environment > variables are not used under the following conditions. > - the output directory exists and, > - the dates of both input files and package database are > older than...

...estfs-test-tool.pod b/test-tool/libguestfs-test-tool.pod index c4284684f8c4ca3dfba0cb734d9cc46f0330b5b9..8999286848d79225c43c8fead674b998be93d4b3 100644 --- a/test-tool/libguestfs-test-tool.pod +++ b/test-tool/libguestfs-test-tool.pod @@ -87,7 +87,7 @@ variables C<SUPERMIN_KERNEL> and/or C<SUPERMIN_MODULES> (C<FEBOOTSTRAP_KERNEL> and C<FEBOOTSTRAP_MODULES> if still using the old febootstrap 3.21 program). -Refer to L<supermin-helper(1)/ENVIRONMENT VARIABLES> +Refer to L<febootstrap-supermin-helper(8)/ENVIRONMENT VARIABLES> for further information. =head1 TRYING OUT...

...me -aLinux t4240-ubuntu1310 > 3.8.13-rt9-QorIQ-SDK-V1.4 #10 SMP Tue May 27 10:48:24 IST 2014 ppc64 ppc64 > ppc64 GNU/Linux* > Thanks I couldn't read this part of the email. Anyway, you can tell supermin to use a specific kernel and modules directory by setting the SUPERMIN_KERNEL and SUPERMIN_MODULES environment variables. See the supermin(1) man page. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com libguestfs lets you edit virtual machines. Supports shell scripting, bindings from...

....8.13-rt9-QorIQ-SDK-V1.4 > > > uname -a > Linux t4240-ubuntu1310 3.8.13-rt9-QorIQ-SDK-V1.4 #10 SMP Tue May 27 > 10:48:24 IST 2014 ppc64 ppc64 ppc64 GNU/Linux Well, assuming the modules directory matches the kernel (uImage) you could try: export SUPERMIN_KERNEL=/boot/uImage export SUPERMIN_MODULES=/lib/modules/3.8.13-rt9-QorIQ-SDK-V1.4 Are these homebrew kernels? I'm surprised that an official Ubuntu ppc kernel would have such a non-standard name. Anyway, if homebrew you'll also need to ensure the kernel supports all the usual virtio devices (especially virtio-serial, which is req...

...mlink_file copy_kernel dtb_file dtb > > and no_dtb_dir kernel_name = > eprintf "\ > supermin: failed to find a dtb (device tree) directory. > > I expected to take '%s' and to > replace vmlinuz- with dtb- to form a directory. > > You can set SUPERMIN_KERNEL, SUPERMIN_MODULES and SUPERMIN_DTB > to override automatic selection. See supermin(1).\n" > kernel_name; > exit 1 > > and no_dtb dtb_dir wildcard = > eprintf "\ > supermin: failed to find a matching device tree. > > I looked for a file matching '%s' in directory...

Hi Rich But there is no src/kernel.ml file on my ubuntu powerpc to which the above patch is reffering. I have installed supermin as supermin_5.1.8-2_powerpc.deb debian package. Thanks On Tue, Jun 3, 2014 at 7:16 PM, Richard W.M. Jones <rjones@redhat.com> wrote: > On Tue, Jun 03, 2014 at 06:55:49PM +0530, abhishek jain wrote: > > supermin: failed to find a suitable kernel

...ubuntu1310 3.8.13-rt9-QorIQ-SDK-V1.4 #10 SMP Tue May 27 > > > 10:48:24 IST 2014 ppc64 ppc64 ppc64 GNU/Linux > > > > Well, assuming the modules directory matches the kernel (uImage) > > you could try: > > > > export SUPERMIN_KERNEL=/boot/uImage > > export SUPERMIN_MODULES=/lib/modules/3.8.13-rt9-QorIQ-SDK-V1.4 > > > > Are these homebrew kernels? I'm surprised that an official Ubuntu > > ppc kernel would have such a non-standard name. Anyway, if homebrew > > you'll also need to ensure the kernel supports all the usual virtio > &gt...

Hello, I am running into problems with virt-builder on my Ubuntu-14.04 install. Please find the checklist below: 1. What are you trying to achieve? I'm trying to build a standard Ubuntu 14.04 disk image. 2. What exact commands did you run? I ran "virt-builder ubuntu-14.04" 3. What was the precise error/output of these commands? The process gets stuck indefinitely at

Hi, Rich: I met a supermin issue on CentOS 7.1: supermin: version: 5.1.10 supermin: rpm: detected RPM version 4.11 supermin: package handler: fedora/rpm supermin: acquiring lock on /root/test/aaa/lock supermin: build: /usr/lib64/guestfs/supermin.d supermin: build: visiting /usr/lib64/guestfs/supermin.d/base.tar.gz type gzip base image (tar) supermin: build: visiting

...: make quickcheck - Try a different appliance kernel by setting these variables, but choose different kernel versions by looking in your /boot directory first: export SUPERMIN_KERNEL_VERSION=3.13.0-55-generic export SUPERMIN_KERNEL=/boot/vmlinuz-$SUPERMIN_KERNEL_VERSION export SUPERMIN_MODULES=/lib/modules/$SUPERMIN_KERNEL_VERSION rm -rf tmp/.guestfs-* make quickcheck - Add debugging 'set -x' to the top of appliance/init in the source tree to see if it fails while running a specific command. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat....

...kernels. The concern was that the lpae kernels don't boot under qemu. If they do, then I can remove this check. Can you see if supermin works if you set some variation of: export SUPERMIN_KERNEL=/boot/vmlinuz-<version>.lpae export SUPERMIN_KERNEL_VERSION=<version> export SUPERMIN_MODULES=/lib/modules/<version>.lpae which should bypass the check. You might also need to set SUPERMIN_DTB to point to a DTB, or maybe not if qemu is generating device trees correctly on ARM 32 bit these days. Roll on aarch64 :-) Rich. -- Richard Jones, Virtualization Group, Red Hat http://peop...

This patch series fixes several problems in the way that supermin handles kernels. The most pressing problem is that supermin doesn't handle bogus vmlinuz files which aren't actual kernels. Along the way there is a lot of clean up. The patches look much better if you view them with ‘-w’. This series will require plenty of time to be tested in Fedora, especially on non-x86 arches.

...thing to worry about. However I am not aware of any CentOS distributed kernels which are configured like that. You can also try choosing a different kernel, by setting: export SUPERMIN_KERNEL_VERSION=3.10.0-123.el7.x86_64 export SUPERMIN_KERNEL=/boot/vmlinuz-$SUPERMIN_KERNEL_VERSION export SUPERMIN_MODULES=/lib/modules/$SUPERMIN_KERNEL_VERSION > But it works fine on another centos 7.1 machine. > > Could you please give me some hints on how to debug this kind of issue? You can get more debugging by adding more -v options, eg: supermin5 --build -f ext2 -v -v -v /usr/lib64/guestfs/supermi...

...dtb and no_dtb_dir kernel_name = - eprintf "\ -supermin: failed to find a dtb (device tree) directory. + error "\ +failed to find a dtb (device tree) directory. I expected to take '%s' and to replace vmlinuz- with dtb- to form a directory. You can set SUPERMIN_KERNEL, SUPERMIN_MODULES and SUPERMIN_DTB -to override automatic selection. See supermin(1).\n" - kernel_name; - exit 1 +to override automatic selection. See supermin(1)." + kernel_name and no_dtb dtb_dir wildcard = - eprintf "\ -supermin: failed to find a matching device tree. + error "\...

...a different appliance kernel by setting these variables, but > choose different kernel versions by looking in your /boot directory > first: > > export SUPERMIN_KERNEL_VERSION=3.13.0-55-generic > export SUPERMIN_KERNEL=/boot/vmlinuz-$SUPERMIN_KERNEL_VERSION > export SUPERMIN_MODULES=/lib/modules/$SUPERMIN_KERNEL_VERSION > rm -rf tmp/.guestfs-* > make quickcheck > > - Add debugging 'set -x' to the top of appliance/init in the source > tree to see if it fails while running a specific command. > > Rich. > > -- > Richard Jones, Virtu...

Hi Rich I'm noe getting the below logs after running libguestfs-test-tool.. SUPERMIN_MODULES=/lib/modules/3.8.13-rt9-QorIQ-SDK-V1.4 SUPERMIN_KERNEL=/boot/vmlinuz-3.8.13-rt9-QorIQ-SDK-V1.4 PATH=/bin:/sbin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/sbin:/usr/local/bin SELinux: sh: getenforce: command not found guestfs_get_append: (null) guestfs_get_autosync: 1 guestfs_get_backend: direct guest...

...o Which found on the machine supermin works fine. It looks strange. Regards, - Chen > >You can also try choosing a different kernel, by setting: > > export SUPERMIN_KERNEL_VERSION=3.10.0-123.el7.x86_64 > export SUPERMIN_KERNEL=/boot/vmlinuz-$SUPERMIN_KERNEL_VERSION > export SUPERMIN_MODULES=/lib/modules/$SUPERMIN_KERNEL_VERSION > >> But it works fine on another centos 7.1 machine. >> >> Could you please give me some hints on how to debug this kind of issue? > >You can get more debugging by adding more -v options, eg: > > supermin5 --build -f ext2 -v...

...ependent packages @@ -497,14 +497,14 @@ If this environment variable is set, then automatic selection of the kernel is bypassed and this kernel is used. The environment variable should point to a kernel file, -eg. C</boot/vmlinuz-3.0.x86_64> +eg. F</boot/vmlinuz-3.0.x86_64> =item SUPERMIN_MODULES This specifies the kernel modules directory to use. The environment variable should point to a module directory, -eg. C</lib/modules/3.0.x86_64/> +eg. F</lib/modules/3.0.x86_64/> =item SUPERMIN_DTB -- 2.1.0

Hi, few cleanups in the supermin codebase; no actual functional change. Thanks, -- Pino Toscano (3): ext2: simplify tracking of visited modules utils: remove unused run_python function Add and use an helper error function src/build.ml | 20 +++++----------- src/dpkg.ml | 4 +--- src/ext2_initrd.ml | 10 ++++---- src/kernel.ml | 27