From: Alper Nebi Yasak <alpernebiyasak@gmail.com>
To: u-boot@lists.denx.de
Cc: Bin Meng <bmeng.cn@gmail.com>,
Heinrich Schuchardt <xypron.glpk@gmx.de>,
Tom Rini <trini@konsulko.com>,
Daniel Schwierzeck <daniel.schwierzeck@gmail.com>,
Simon Glass <sjg@chromium.org>,
Marek Vasut <marek.vasut@gmail.com>,
Alper Nebi Yasak <alpernebiyasak@gmail.com>
Subject: [PATCH 1/4] tools: docker: Install a readable kernel for libguestfs-tools
Date: Fri, 4 Jun 2021 22:02:03 +0300 [thread overview]
Message-ID: <20210604190207.44805-2-alpernebiyasak@gmail.com> (raw)
In-Reply-To: <20210604190207.44805-1-alpernebiyasak@gmail.com>
The filesystem and EFI (capsule and secure boot) test setups try to use
guestmount and virt-make-fs respectively to prepare disk images to run
tests on. However, these libguestfs tools need a kernel image and fail
with the following message (revealed in debug/trace mode) if it can't
find one:
supermin: failed to find a suitable kernel (host_cpu=x86_64).
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
supermin use, you shouldn't boot the Xen guest with it).
This failure then causes these tests to be skipped in CIs. Install a
kernel package in the Docker containers so the CIs can run these
tests with libguestfs tools again (assuming the container is run with
necessary host devices and privileges). As this kernel would be only
used for virtualization, we can use the kernel package specialized for
that. On Ubuntu systems kernel images are not readable by non-root
users, so explicitly add read permissions with chmod as well.
Signed-off-by: Alper Nebi Yasak <alpernebiyasak@gmail.com>
---
tools/docker/Dockerfile | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/tools/docker/Dockerfile b/tools/docker/Dockerfile
index d2f0074ee8a6..563b16639e54 100644
--- a/tools/docker/Dockerfile
+++ b/tools/docker/Dockerfile
@@ -71,6 +71,7 @@ RUN apt-get update && apt-get install -y \
libssl-dev \
libudev-dev \
libusb-1.0-0-dev \
+ linux-image-kvm \
lzma-alone \
lzop \
mount \
@@ -99,6 +100,9 @@ RUN apt-get update && apt-get install -y \
zip \
&& rm -rf /var/lib/apt/lists/*
+# Make kernels readable for libguestfs tools to work correctly
+RUN chmod +r /boot/vmlinu* /lib/modules/*/vmlinu* || true
+
# Manually install libmpfr4 for the toolchains
RUN wget http://mirrors.kernel.org/ubuntu/pool/main/m/mpfr4/libmpfr4_3.1.4-1_amd64.deb && dpkg -i libmpfr4_3.1.4-1_amd64.deb && rm libmpfr4_3.1.4-1_amd64.deb
--
2.32.0.rc2
next prev parent reply other threads:[~2021-06-04 19:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-04 19:02 [PATCH 0/4] Fix CIs skipping filesystem, EFI secure boot and EFI capsule tests Alper Nebi Yasak
2021-06-04 19:02 ` Alper Nebi Yasak [this message]
2021-06-05 0:21 ` [PATCH 1/4] tools: docker: Install a readable kernel for libguestfs-tools Heinrich Schuchardt
2021-06-05 5:17 ` AKASHI Takahiro
2021-06-04 19:02 ` [PATCH 2/4] Azure: Add fuse device for sandbox test.py tests Alper Nebi Yasak
2021-06-09 20:59 ` Tom Rini
2021-06-04 19:02 ` [PATCH 3/4] Azure: Add loop devices and CAP_SYS_ADMIN " Alper Nebi Yasak
2021-06-04 19:02 ` [PATCH 4/4] Azure/GitLab: Install a readable kernel for libguestfs-tools Alper Nebi Yasak
2021-06-05 0:26 ` Heinrich Schuchardt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210604190207.44805-2-alpernebiyasak@gmail.com \
--to=alpernebiyasak@gmail.com \
--cc=bmeng.cn@gmail.com \
--cc=daniel.schwierzeck@gmail.com \
--cc=marek.vasut@gmail.com \
--cc=sjg@chromium.org \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=xypron.glpk@gmx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.