Bug#958311: cloud kernel 5.5.0-2 does not boot under xen
Hi,
On 16/02/2023 18:18, Samuel Thibault wrote:
Andy Smith, le jeu. 16 févr. 2023 15:44:21 +, a ecrit:
- The PV part of grub is quite old and from what I understand
implemented in a strange way
Ah, uh :/
that no one wants to maintain any
more, so this part of grub is stuck without ability to
understand the newer kernel compressions.
I've been using the attached script to get around the problem. It tries
to decompress the cloud kernel and then recompress it with something
that grub-xen can handle. If recompression fails, it leaves an
uncompressed kernel, which also works, in place.
The script needs to be installed in /etc/kernel/postinst.d/.
--
Aleksi Suhonen
() ascii ribbon campaign
/\ support plain text e-mail
#!/bin/sh
# SPDX-License-Identifier: GPL-2.0-only
# --
# kernel-recompress-hook - recompress cloud kernels for grub-xen
# Place this script in /etc/kernel/postinst.d/
# Requires: binutils, lz4, xz-utils
# (c) 2021-2023 Aleksi Suhonen
#
# Distilled from extract-vmlinux by
# (c) 2009,2010 Dick Streefland
# (c) 2011 Corentin Chary
#
# --
KERNEL_VERSION="$1"
KERNEL_PATH="$2"
# The KERNEL_PATH must be valid
if [ ! -f "${KERNEL_PATH}" ]; then
echo >&2 "Kernel file '${KERNEL_PATH}' not found. Aborting"
exit 1
fi
# Prepare temp files:
tmp=$(mktemp /boot/vmlinux-X)
trap "rm -f $tmp ${tmp}.xz" 0
# Try to find the LZ4 header and decompress from here
LZ4_HEADER="$(printf '\002!L\030')"
for pos in `fgrep -abo "$LZ4_HEADER" "$KERNEL_PATH"`
do
# grep counts bytes from 0, while tail counts from 1...
pos=$((1+${pos%%:*}))
rm -f $tmp
tail -c+$pos "$KERNEL_PATH" | lz4 -d >$tmp
readelf -h $tmp >/dev/null 2>&1 && break
echo "False LZ4 header at ${pos}, looking for more..."
done
if ! readelf -h $tmp > /dev/null; then
echo >&2 "Decompression of kernel file '${KERNEL_PATH}' failed!, not a
valid ELF image"
exit 0
fi
echo "Decompression of kernel file '${KERNEL_PATH}' successful"
if xz --check=crc32 --x86 --lzma2=dict=32MiB $tmp; then
echo "Recompression also successful"
mv -fv ${tmp}.xz ${KERNEL_PATH}
echo "Replacement of kernel file successful"
else
echo "Recompression unsuccessful"
mv -fv ${tmp} ${KERNEL_PATH}
echo "Replacement of kernel file successful"
fi
exit 0
#EOF
Bug#958311: cloud kernel 5.5.0-2 does not boot under xen
Hello, On 07/06/2022 16:36, Diederik de Haas wrote: Here's the error message: Loading Linux 5.6.0-1-cloud-amd64 ... error: not xen image. Loading initial ramdisk ... error: you need to load the kernel first. Can you still reproduce this issue on a more recent kernel (5.10 or later)? 5.10 and many later kernels still have this issue. I haven't tried 5.17 or 5.18, but I suspect they still do. The underlying problem is that the cloud kernel is compressed with an algorithm that grub can't uncompress. What I've been doing as a workaround is that I decompress the kernel myself in a kernel install hook. I'm a bit busy this week and next with a couple of huge events, so I don't have to provide more details until after those are done. Best Regards, -- Aleksi Suhonen () ascii ribbon campaign /\ support plain text e-mail
Bug#958311: still an issue with 5.6.0-1
Hello,
As an update to my earlier message, I upgraded my test DomU to the
following versions and I still have the problem:
ii grub-xen 2.04-7
ii linux-image-5.6.0-1-cloud-amd64 5.6.7-1
Here's the error message:
Loading Linux 5.6.0-1-cloud-amd64 ...
error: not xen image.
Loading initial ramdisk ...
error: you need to load the kernel first.
Best Regards,
--
Aleksi Suhonen
() ascii ribbon campaign
/\ support plain text e-mail
Bug#958311: cloud kernel 5.5.0-2 does not boot under xen
Package: linux-image-cloud-amd64
Version: 5.5.17-1
Severity: important
Linux cloud image 5.5.0-2 refuses to boot in a Xen VM for me. Older
versions up to and including 5.5.0-1 work. I'm using grub-xen to boot
the VMs.
The grub-xen (i think) complains that it's not a Xen kernel and goes
back to the menu after a few seconds.
DomU package versions on the test machine:
ii grub-xen2.04-6
ii linux-image-5.5.0-2-cloud-amd64 5.5.17-1
Dom0 package versions on the test machine:
ii grub-xen-host 2.02+dfsg1-9
ii linux-image-4.18.0-3-amd64 4.18.20-2
ii xen-hypervisor-4.11-amd64 4.11.1~pre.20180911.5acdd26fdc+dfsg-5
I skimmed through the patch notes, and couldn't find anything that
should cause this behaviour.
--
Aleksi Suhonen
() ascii ribbon campaign
/\ support plain text e-mail
Bug#932881: add dependency on logsave
Package: initramfs-tools Severity: grave Version: 0.133 After upgrading e2fsprogs to 1.45.3-1, computer fails to boot because rootfs fails to fsck. And fsck fails because binary for logsave is missing. Or in fact, fsck doesn't fail, but the init script reports it did, because it cannot tell the difference... This is because logsave has just been split into its own package "logsave." The initrd builder scripts should depend on it, except it seems that not all hardware platforms have the logsave package yet... Excerpt from the other package's changelog: e2fsprogs (1.45.3-1) unstable; urgency=medium * New upstream version * Automatic online file system scrubs is now disabled by default. They can be enabled by editing /etc/e2scrub.conf. ... * Only require the udev, systemd, and cron build dependencies when building on Linux. (Closes: #931266) * Move logsave to its own package. (Closes: #923372) * Update the Czech and Dutch translations -- Theodore Y. Ts'o Sun, 14 Jul 2019 21:01:11 -0400 Best Regards, -- Aleksi Suhonen
Bug#655314: linux-image-3.1.0-1-amd64: ICMPv6 debugging message
Package: linux-2.6 Version: 3.1.6-1 Severity: normal Tags: ipv6 I'm running a Teredo relay/server using miredo-server and the system logs are being filled with this message: Jan 10 09:24:33 6to4 kernel: [93060.760149] icmpv6_send: no reply to icmp error Jan 10 09:24:42 6to4 kernel: [93069.812879] icmpv6_send: no reply to icmp error This message is generated when the kernel feels it should send an ICMP error for a packet that itself was an ICMP error. RFC says that you don't send errors for errors, so it's dropped, but the developers have decided to put a debugging message in that if-branch. Normally that debugging message should never be displayed, because under normal server conditions it should never occur. However, due to the way Teredo works, this can and will happen quite often. Would it be possible to remove or comment out this particular debuggin message, because on normal servers it has no value and on Teredo servers ... well ... it has no value either but it fills the logs. Or if it can't be removed, it should be possible to turn it on and off using some sysctl. -- Package-specific info: ** Kernel log: boot messages should be attached -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.0.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages linux-image-3.1.0-1-amd64 depends on: ii debconf [debconf-2.0] 1.5.41 ii initramfs-tools [linux-initramfs-tool] 0.99 ii linux-base 3.4 ii module-init-tools 3.16-1 Versions of packages linux-image-3.1.0-1-amd64 recommends: ii firmware-linux-free 3 Versions of packages linux-image-3.1.0-1-amd64 suggests: pn grub-pc1.99-14 pn linux-doc-3.1 Versions of packages linux-image-3.1.0-1-amd64 is related to: pn firmware-bnx2 pn firmware-bnx2x pn firmware-ipw2x00 pn firmware-ivtv pn firmware-iwlwifi pn firmware-linux pn firmware-linux-nonfree 0.34 pn firmware-qlogic pn firmware-ralink pn xen-hypervisor -- debconf information excluded -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120110093458.5046.1240.report...@halli.atm.tut.fi
Bug#564010: iwlwifi-6050-4.ucode missing
Hi,
I have similar problems with my laptop and
I read the bug report logs and I still can't find
iwlwifi-6050-4.ucode
needed by iwlagn driver. This is forcing me to use
an older kernel where that driver still works. )-;
I've had this problem since 2.6.31. Also, why do
2.6.31 and 2.6.32 kernels turn my bluetooth radio
on at boot? 2.6.30 leaves it off until I want it,
so that it doesn't eat up my battery life.
--
Aleksi Suhonen
() ascii ribbon campaign
/\ support plain text e-mail
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
