[Bug 1877088] Comment bridged from LTC Bugzilla
bugproxy
1877088 at bugs.launchpad.net
Tue Jun 2 14:19:56 UTC 2020
------- Comment From Niklas.Schnelle at ibm.com 2020-06-02 10:15 EDT-------
"make install" also triggers initramfs creation as does manual
invocation of the installkernel script. In fact both even trigger
boot loader update/install.
This is the output:
$ sudo make install
sh -x ./arch/s390/boot/install.sh 5.4.27 arch/s390/boot/bzImage \
System.map "/boot"
+ [ -x /root/bin/installkernel ]
+ [ -x /sbin/installkernel ]
+ exec /sbin/installkernel 5.4.27 arch/s390/boot/bzImage System.map /boot
run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 5.4.27 /boot/vmlinuz-5.4.27
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 5.4.27 /boot/vmlinuz-5.4.27
update-initramfs: Generating /boot/initrd.img-5.4.27
Using config file '/etc/zipl.conf'
Run /lib/s390-tools/zipl_helper.device-mapper /boot
Building bootmap in '/boot'
Building menu 'menu'
Adding #1: IPL section 'ubuntu' (default)
Adding #2: IPL section 'old'
Preparing boot device: dm-0.
Done.
run-parts: executing /etc/kernel/postinst.d/unattended-upgrades 5.4.27 /boot/vmlinuz-5.4.27
run-parts: executing /etc/kernel/postinst.d/update-notifier 5.4.27 /boot/vmlinuz-5.4.27
run-parts: executing /etc/kernel/postinst.d/zz-zipl 5.4.27 /boot/vmlinuz-5.4.27
Using config file '/etc/zipl.conf'
Run /lib/s390-tools/zipl_helper.device-mapper /boot
Building bootmap in '/boot'
Building menu 'menu'
Adding #1: IPL section 'ubuntu' (default)
Adding #2: IPL section 'old'
Preparing boot device: dm-0.
Done.
I did already have /etc/kernel-img.conf
with the following content:
# Kernel image management overrides
# See kernel-img.conf(5) for details
do_symlinks = yes
do_bootloader = yes
do_initrd = yes
link_in_boot = yes
Could this depend on the legacy installer?
Our automatically installed systems are currently all installed with it
and I also used that for this test LPAR (that has PCI Physical Functions)
since the legacy installer allowed a much nicer
manual network configuration using the HMC console.
Sadly that's also why I can't currently test on another fresh install
as our automatic installation system is currently being changed
to support the new installer and I couldn't get the previous workaround
to work today.
I'm not knowledgeable enough to give a good opinion on initrd less
boot but I would suspect that the deployments at our customers are much
more varied than the average cloud so I would be hesitant about defaulting
to it. Also in my experience s390 boot times are already quite good.
Afaik with our defconfig a lot of us developers regularly boot
without initrd or even any modules, so supporting it shouldn't be
a problem. As the defconfig doesn't include the
drivers for PCI devices into the Kernel I usually use both modules
and an initrd, which might be why I stumbled over this first.
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to debianutils in Ubuntu.
https://bugs.launchpad.net/bugs/1877088
Title:
[UBUNTU 20.04] installkernel script does not symlink /boot/initrd.img
which is required with the default zipl.conf
Status in Ubuntu on IBM z Systems:
Incomplete
Status in debianutils package in Ubuntu:
New
Status in linux-base package in Ubuntu:
New
Bug description:
When testing development kernels I usually rely on the installkernel
script either through the "make install" target of the Kernel source
or manually. This used to work great on Ubuntu on Z.
On Ubuntu 20.04 (freshly installed up to date) this fails however because
/boot/initrd.img is not updated (/boot/vmlinuz is) and thus zipl installs the
wrong kernel/initrd combination rendering the system unbootable.
(with the correct modules already copied to /usr/lib/modules/5.7.0-rc4-06500-gb67ea026badd/)
# sudo installkernel 5.7.0-rc4-06500-gb67ea026badd bzImage System.map /boot
run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 5.7.0-rc4-06500-gb67ea026badd /boot/vmlinuz-5.7.0-rc4-06500-gb67ea026badd
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 5.7.0-rc4-06500-gb67ea026badd /boot/vmlinuz-5.7.0-rc4-06500-gb67ea026badd
update-initramfs: Generating /boot/initrd.img-5.7.0-rc4-06500-gb67ea026badd
Using config file '/etc/zipl.conf'
Building bootmap in '/boot'
Building menu 'menu'
Adding #1: IPL section 'ubuntu' (default)
Adding #2: IPL section 'old'
Preparing boot device: dasda (3844).
Done.
run-parts: executing /etc/kernel/postinst.d/zz-zipl 5.7.0-rc4-06500-gb67ea026badd /boot/vmlinuz-5.7.0-rc4-06500-gb67ea026badd
Using config file '/etc/zipl.conf'
Building bootmap in '/boot'
Building menu 'menu'
Adding #1: IPL section 'ubuntu' (default)
Adding #2: IPL section 'old'
Preparing boot device: dasda (3844).
Done.
# ls -l /boot
total 178364
-rw------- 1 root root 135168 May 6 11:52 bootmap
-rw-r--r-- 1 root root 90471 Apr 29 15:34 config-5.4.0-29-generic
lrwxrwxrwx 1 root root 27 May 6 11:40 initrd.img -> initrd.img-5.4.0-29-generic <====== should point to new version
-rw-r--r-- 1 root root 19663996 May 6 11:42 initrd.img-5.4.0-29-generic
-rw-r--r-- 1 root root 125339494 May 6 11:52 initrd.img-5.7.0-rc4-06500-gb67ea026badd
lrwxrwxrwx 1 root root 27 May 6 11:40 initrd.img.old -> initrd.img-5.4.0-29-generic
-rw------- 1 root root 3087920 Apr 29 15:34 System.map-5.4.0-29-generic
-rw-r--r-- 1 root root 4031691 May 6 11:52 System.map-5.7.0-rc4-06500-gb67ea026badd
-rw-r--r-- 1 root root 4031691 May 6 11:49 System.map-5.7.0-rc4-06500-gb67ea026badd.old
lrwxrwxrwx 1 root root 37 May 6 11:52 vmlinuz -> vmlinuz-5.7.0-rc4-06500-gb67ea026badd
-rw------- 1 root root 8086072 Apr 29 15:54 vmlinuz-5.4.0-29-generic
-rw-r--r-- 1 root root 9080832 May 6 11:52 vmlinuz-5.7.0-rc4-06500-gb67ea026badd
-rw-r--r-- 1 root root 9080832 May 6 11:49 vmlinuz-5.7.0-rc4-06500-gb67ea026badd.old
lrwxrwxrwx 1 root root 41 May 6 11:52 vmlinuz.old -> vmlinuz-5.7.0-rc4-06500-gb67ea026badd.old
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1877088/+subscriptions
More information about the foundations-bugs
mailing list