generic arm64 kernel can not boot initrdless and there is no -kvm kernel
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
The CPC team wants to build minimal arm64 images. Those images should boot initrdless (similar to the amd64 images where the -kvm kernel is used).
But booting an initrdless image (build with livecd-rootfs) does fail with:
$ sudo qemu-system-aarch64 -m 2G -M virt -cpu max -bios /usr/share/
[snipped]
[ 0.945928] VFS: Cannot open root device "PARTUUID=
[ 0.946117] Please append a correct "root=" boot option; here are the available partitions:
[ 0.947611] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
[ 0.948139] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.4.0-74-generic #83-Ubuntu
[ 0.948237] Hardware name: QEMU QEMU Virtual Machine, BIOS 0.0.0 02/06/2015
[ 0.948453] Call trace:
[ 0.948736] dump_backtrace+
[ 0.948864] show_stack+
[ 0.948918] dump_stack+
[ 0.948974] panic+0x150/0x364
[ 0.949027] mount_block_
[ 0.949090] mount_root+
[ 0.949145] prepare_
[ 0.949205] kernel_
[ 0.949274] kernel_
[ 0.949336] ret_from_
[ 0.949913] Kernel Offset: disabled
[ 0.950175] CPU features: 0x0952,20e0a230
[ 0.950251] Memory Limit: none
[ 0.950595] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) ]---
The reason is, that the the virtio drivers are modules (CONFIG_
Expected behavior:
Booting an arm64 image without an initrd does work in a virtualized environment similar to an amd64 image (that uses the -kvm kernel)
summary: |
- generic arm64 kernel can not boot initrdless + generic arm64 kernel can not boot initrdless and there is no -kvm kernel |
Changed in linux (Ubuntu): | |
status: | Incomplete → Confirmed |
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
apport-collect 1931841
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the Ubuntu Kernel Team.