search for: supermin_kernel

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

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

...3 ubuntu ubuntu 4096 Jun 3 07:21 3.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 (e...

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.

On Wed, Jun 04, 2014 at 03:29:11PM +0530, abhishek jain wrote: > supermin: kernel: SUPERMIN_KERNEL environment variable /boot/uImage > supermin: failed to find a suitable kernel (host_cpu=powerpc64). > > I looked for kernels in /boot and modules in /lib/modules. If you follow the code in src/kernel.ml you'll see that this means supermin was unable to get the kernel version from th...

...-) diff --git a/test-tool/libguestfs-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 i...

...t9-QorIQ-SDK-V1.4uname -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 scri...

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

...el_version; > printf "supermin: kernel: modules %s\n%!" modpath; > ); > > (kernel_version, modpath) > > and find_kernel debug host_cpu copy_kernel kernel = > let kernel_file, kernel_name, kernel_version = > try > let kernel_env = getenv "SUPERMIN_KERNEL" in > if debug >= 1 then > printf "supermin: kernel: SUPERMIN_KERNEL environment variable > %s\n%!" > kernel_env; > let kernel_version = get_kernel_version_from_file kernel_env in > if debug >= 1 then > printf &qu...

Hello, I'm using virt-sparsify on a new server and I get an error message: # virt-sparsify img img2 [   0.0] Create overlay file in /tmp to protect source disk [   0.1] Examine source disk virt-sparsify: error: libguestfs error: guestfs_launch failed. This usually means the libguestfs appliance failed to start or crashed. Here is libguestfs-test-tool output:

> > Apparently this: > > https://wiki.manjaro.org/index.php?title=Pacman_troubleshooting#.22Unable_to_lock_database.22_Error > I didn't mentioned it, but I already ran # rm /var/lib/pacman/db.lck I even tried building with make -j1 just in case some other thread was locking the DB. In fact, some process during the build is already locking the DB.

when run libguestfs-test-tool in the two pc,but the result is different. please tell me what cause the result and what cause the guest fail to run in the ram ? thanks !! At 2019-11-28 21:30:53, "Richard W.M. Jones" <rjones@redhat.com> wrote: >Could you please run: > > libguestfs-test-tool > >and attach the complete output to your email. > >Rich.

...quot;supermin: kernel: modules %s\n%!" modpath; - ); - - (kernel_version, modpath) - -and find_kernel debug host_cpu copy_kernel kernel = - let kernel_file, kernel_name, kernel_version = + let kernel_file, kernel_name, kernel_version, modpath = try let kernel_env = getenv "SUPERMIN_KERNEL" in if debug >= 1 then @@ -78,38 +57,58 @@ and find_kernel debug host_cpu copy_kernel kernel = printf "supermin: kernel: SUPERMIN_KERNEL version %s\n%!" kernel_version; let kernel_name = Filename.basename kernel_env in - kernel_env, kernel_na...

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'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 guestfs_get_backend_settings: [] guestfs_get_cachedir: /var/...

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

...- Use 'libguestfs-test-tool' for testing to see if that makes a difference. In the build directory, run: 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...

...on 4.8.5 20150623 (Red Hat 4.8.5-36) (GCC) ) #1 SMP Fri Nov 1 10:40:29 UTC 2019 The kernel that fails isn't the Red Hat kernel, so I suppose it lacks the right drivers or has some different configuration which breaks libguestfs. You can tell libguestfs to use a different kernel by setting the SUPERMIN_KERNEL parameter and removing the /var/tmp/.guestfs-* directory between runs. See the FAQ here: http://libguestfs.org/guestfs-faq.1.html#broken-kernel-or-trying-a-different-kernel For comparison the successful run is using the ordinary CentOS kernel: [ 0.000000] Linux version 3.10.0-957.10.1.el7.x8...

[This email is either empty or too large to be displayed at this time]

....lpae or .tegra kernel. The vexpress-aX emulation we are using in qemu doesn't support these 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 AR...