Bug 30307

Summary: Kernel panic for aarch64 on KVM
Product: Mageia Reporter: Jybz <j.biernacki+mga>
Component: RPM PackagesAssignee: Kernel and Drivers maintainers <kernel>
Status: NEW --- QA Contact:
Severity: normal    
Priority: Normal CC: fri, pterjan
Version: 8   
Target Milestone: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Source RPM: CVE:
Status comment:
Attachments: Full startup log

Description Jybz 2022-04-20 13:45:19 CEST 
Hello !

This might be a duplicate of bug #8614 but not really.

I'm trying to generate an aarch64 image of Mageia to be run under the Freebox-Delta.

See proposal of Neoclust:
https://wiki.mageia.org/en/Feature:Create_arm_cloudinit_images

WIP on my side, I'm not used with KVM, does it need something in particular in the initrd?

Short extract:
> [    4.507778] Run /init as init process
> mount: error while loading shared libraries: libmount.so.1: cannot open shared object file: No such file or directory
> Cannot mount proc on /proc! Compile the kernel with CONFIG_PROC_FS!
> [    4.796360] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000100
> [    4.797304] CPU: 1 PID: 1 Comm: init Not tainted 5.15.32-desktop-1.mga8 #1
> [    4.798499] Hardware name: QEMU QEMU Virtual Machine, BIOS 0.0.0 02/06/2015
> [    4.799148] Call trace:
> [    4.799314]  dump_backtrace+0x0/0x1ac
> [    4.799779]  show_stack+0x18/0x24
> [    4.799969]  dump_stack_lvl+0x68/0x84
> [    4.800162]  dump_stack+0x18/0x34
> [    4.800345]  panic+0x15c/0x31c
> [    4.800507]  do_exit+0x950/0x994
> [    4.800672]  do_group_exit+0x38/0xa0
> [    4.800844]  __arm64_sys_exit_group+0x18/0x20
> [    4.801039]  invoke_syscall+0x48/0x114
> [    4.801223]  el0_svc_common.constprop.0+0x44/0xec
> [    4.801434]  do_el0_svc+0x24/0x90
> [    4.801597]  el0_svc+0x28/0xe0
> [    4.801758]  el0t_64_sync_handler+0x1a4/0x1b0
> [    4.801958]  el0t_64_sync+0x1a0/0x1a4
> [    4.802577] SMP: stopping secondary CPUs
> [    4.803203] Kernel Offset: 0x51900b6e0000 from 0xffff800008000000
> [    4.803479] PHYS_OFFSET: 0xffff94e1c0000000
> [    4.803684] CPU features: 0x22000cf1,00000846
> [    4.804166] Memory Limit: none
> [    4.804868] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000100 ]---

I tried to add 
> add_dracutmodules+=" fs-lib"
in /etc/dracut.conf.d/30-kvm.conf
(because it mentions there https://wiki.gentoo.org/wiki/Dracut 
> fs-lib 	Includes filesystem tools (including mount).
)
And I regenerate the initrd afterwards.

But the issue is still present.
Comment 1 Jybz 2022-04-20 13:46:00 CEST 
Created attachment 13223 [details]
Full startup log

See in attachment a full startup log.
David Walser 2022-04-20 15:36:54 CEST

Assignee: bugsquad => kernel

Comment 2 Pascal Terjan 2022-04-20 19:42:01 CEST 
This doesn't seem related to either KVM or the kernel, dracut doesn't include the libraries needed to run the mount command.

How do you generate the image or run dracut? My guess would be that ldd or something like that used by dracut to find libraries used by a binary is failing when building the image.

CC: (none) => pterjan

Comment 3 Jybz 2022-04-20 20:03:38 CEST 
It is still a WIP, I just pushed the latest modifications on the branch for you in order to investigate.

source: https://gitweb.mageia.org/software/mageia4arm/tree/?h=user/jibz/freebox-delta
Command :
> git checkout "user/jibz/freebox-delta"
> ./create_arm_image.sh --log --config freebox-delta --all && chown -R jybz:jybz ./build/
Comment 4 Morgan Leijström 2023-02-17 12:33:26 CET 
Status?

(In reply to Jybz from comment #3)
> It is still a WIP, I just pushed the latest modifications on the branch for
> you in order to investigate.

CC: (none) => fri