Description of problem:
$ libguestfs-supermin-helper: failed to find a suitable kernel.
I looked for kernels in /boot and modules in /lib/modules.
If this is a Xen guest, and you only have Xen domU kernels
installed, try installing a fullvirt kernel (only for
libguestfs use, you shouldn't boot the Xen guest with it).
Version-Release number of selected component (if applicable):
libguestfs 1.16 in RHEL 6.4 (ovirt-node)
Steps to Reproduce:
1. Run libguestfs-test-tool
Fails as above.
Should run and print various diagnostics followed by:
===== TEST FINISHED OK =====
Please add libguestfs-test-tool as a step in regression testing
when creating ovirt-node.
libguestfs-test-tool output reported by a user:
On RHEV-H the kernel and initrd is not located in /boot, they are only exposed in /dev/.initramfs/live/ as vmlinuz0 and initrd0.
A workaround is to symlink the kernel into /boot.
$ ln -s /dev/.initramfs/live/vmlinuz0 /boot/vmlinuz-$(uname -r)
Afterwards libguestfs-test-tool should run fine.
(In reply to Fabian Deutsch from comment #3)
> On RHEV-H the kernel and initrd is not located in /boot, they are only
> exposed in /dev/.initramfs/live/ as vmlinuz0 and initrd0.
> A workaround is to symlink the kernel into /boot.
> $ ln -s /dev/.initramfs/live/vmlinuz0 /boot/vmlinuz-$(uname -r)
It should be
$ ln -s /dev/.initramfs/live/isolinux/vmlinuz0 /boot/vmlinuz-$(uname -r)
> Afterwards libguestfs-test-tool should run fine.
we can probably create that symlink for compatibility, but libguestfs should probably also look fpor kernels in the in the livecd related paths
One problem might be that the kernel found there (vmlinuz9) is "unversioned".
The following might work:
(I can't test this)
It's not great for RHEL users however unless we can add this
environment variable in some place where it will always be set
(for shell users and VDSM hooks at least).
(In reply to Richard W.M. Jones from comment #6)
> The following might work:
> export FEBOOTSTRAP_KERNEL=/dev/.initramfs/live/isolinux/vmlinuz0
> (I can't test this)
The customer reported that this didn't work:
select kernel /dev/.initramfs/live/vmlinuz0
febootstrap-supermin-helper: cannot guess module path.
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.
*** Bug 846956 has been marked as a duplicate of this bug. ***
Anyway we have a program to test if the kernel/appliance
stuff is working or not:
It doesn't require any special permissions.
It is completely self-contained.
It only takes a minute to run.
It can be called from a script (has correct exit statuses for
It should be added to whatever regression test is done on
IIUIC everything is in place (pkgs and configuration), the only thing missing are the correct symlinks to the kernel.
This bug is currently attached to errata RHBA-2013:15277. If this change is not to be documented in the text for this errata please either remove it from the errata, set the requires_doc_text flag to minus (-), or leave a "Doc Text" value of "--no tech note required" if you do not have permission to alter the flag.
Otherwise to aid in the development of relevant and accurate release documentation, please fill out the "Doc Text" field above with these four (4) pieces of information:
* Cause: What actions or circumstances cause this bug to present.
* Consequence: What happens when the bug presents.
* Fix: What was done to fix the bug.
* Result: What now happens when the actions or circumstances above occur. (NB: this is not the same as 'the bug doesn't present anymore')
Once filled out, please set the "Doc Type" field to the appropriate value for the type of change made and submit your edits to the bug.
For further details on the Cause, Consequence, Fix, Result format please refer to:
Thank you for your help.
Hiya, could you let me know how this problem was resolved for the doctext? Thanks
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.