[Bug 1920043] Update Released

[Brian Murray]

The verification of the Stable Release Update for livecd-rootfs has
completed successfully and the package is now being released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to livecd-rootfs in Ubuntu.
https://bugs.launchpad.net/bugs/1920043

Title:
  Latest Focal Minimal disk images from livecd-rootfs do not boot

Status in livecd-rootfs package in Ubuntu:
  Fix Released
Status in livecd-rootfs source package in Focal:
  Fix Released

Bug description:
  [Impact]

   * Minimal images built from livecd-rootfs after March 12th do not
  boot. There are no broken images on cloud-images.ubuntu.com, but no
  further images will be published until this is fixed. Cloud-specific
  minimal images are unaffected, as they do the proper steps in their
  build hooks to mitigate this problem.

  [Test Plan]

   * Build a minimal image from livecd-rootfs in the focal branch.
   * 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
   * Verify cloud-specific minimal builds still operate as intended (single boot, no double boot fallback)

  
  [Where problems could occur]

   * The changes are forcing a boot without initramfs for all minimal
  images. This was the default behavior before the March 12th change.

  [Bug Description]
   
  Here is the kernel panic:

  VFS: Cannot open root device "LABEL=cloudimg-rootfs" or unknown-block(0,0): error -6
  Please append a correct "root=" boot option; here are the available partitions:
  fe00         2306048 vda 
   driver: virtio_blk
    fe01         2192367 vda1 eba1d37a-4dc1-4c42-8cab-ed045e561faa

    fe0e            4096 vda14 9bbe6566-13bd-412a-9a58-8d85918ebe0f

    fe0f          108544 vda15 b4d6d9b6-0a70-41eb-9d71-5d64fc7e7d08

  fe10             366 vdb 
   driver: virtio_blk
  Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
  CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.4.0-1034-kvm #35-Ubuntu
  Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.14.0-1 04/01/2014
  Call Trace:
   0xffffffff92b471a8
   0xffffffff92b23a3d
   0xffffffff9332f5d4
   0xffffffff9332f6b0
   0xffffffff9332f7e7
   0xffffffff9332f287
   ? 0xffffffff92b4a5e0
   0xffffffff92b4a5e9
   0xffffffff92c00215
  Kernel Offset: 0x11400000 from 0xffffffff81000000 (relocation range: 0xffffffff80000000-0xffffffffbfffffff)
  ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) ]---

  
  Kernel command line : 

  Linux version 5.4.0-1034-kvm (buildd at lgw01-amd64-033) (gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)) #35-Ubuntu SMP Wed Feb 24 14:09:38 UTC )
  Command line: BOOT_IMAGE=/boot/vmlinuz-5.4.0-1034-kvm root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0

  The root should be set to a PARTUUID, not a label.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1920043/+subscriptions