Kernel Offset: 0x11400000 from 0xffffffff81000000 (relocation range: 0xffffffff80000 000-0xffffffffb fffffff) Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)ĬPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.4.0-1034-kvm #35-Ubuntu
VFS: Cannot open root device "LABEL= cloudimg- rootfs" or unknown-block(0,0): error -6 This was the default behavior before the March 12th change. * The changes are forcing a boot without initramfs for all minimal images. * Verify cloud-specific minimal builds still operate as intended (single boot, no double boot fallback)
* Launch it through qemu to verify it boots: qemu-system-x86_64 -cpu host -machine type=q35,accel=kvm -m 2048 -snapshot -netdev id=net00, type=user, hostfwd= tcp::2222- :22 -device virtio- net-pci, netdev= net00 -drive if=virtio, format= qcow2,file= focal-server- cloudimg- amd64.img -drive if=virtio, format= raw,file= seed.img -nographic * Build a minimal image from livecd-rootfs in the focal branch. Cloud-specific minimal images are unaffected, as they do the proper steps in their build hooks to mitigate this problem. com, but no further images will be published until this is fixed.
There are no broken images on cloud-images. * Minimal images built from livecd-rootfs after March 12th do not boot.
0 kommentar(er)
