[Bug 1987567] Re: Xen Dom0 linux boot fails with multiple initrd files

[Łukasz Zemczak]

Hello Mauricio, or anyone else affected,

Accepted grub2 into jammy-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/grub2/2.06-2ubuntu7.2
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
jammy to verification-done-jammy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-jammy. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Description changed:

  [Impact]
  
  The linux_xen template seems to be broken for multiple initrd files.
  
  Linux fails to boot when it needs a real initrd but early/microcode
  initrd(s) are found by grub-mkconfig.
  
  The 2 patches (merged upstream [2]) allow more than one initrd to be
  actually loaded, and the real/non-microcode initrd get used by Linux.
  
  More details in the patchset cover letter [1].
  
  [Test Plan]
  
      $ sudo apt install microcode-initrd
  
      $ du --bytes /boot/...
      13660416 /boot/vmlinuz-5.4.0-122-generic
      33062542 /boot/initrd.img-5.4.0-122-generic
      5045248  /boot/microcode.cpio
+ 
+     $ sudo reboot
  
  - Original:
  
      [    2.505207] Kernel panic - not syncing: VFS: Unable to mount root
      fs on unknown-block(0,0)
  
  - Patch 1:
  
      [    1.890498] Freeing initrd memory: 4928K
      ...
      [    2.710948] Kernel panic - not syncing: VFS: Unable to mount root
      fs on unknown-block(0,0)
  
  - Patch 2:
  
      [    1.968578] Freeing initrd memory: 32288K
      ...
      [    2.844889] Run /init as init process
      [    2.916532] systemd-udevd[148]: Starting version 245.4-4ubuntu3.17
  
  [Where problems could occur]
  
  Regressions would be likely to manifest when booting Linux under Xen
  with more than one initrd file (changes contained in this code path).
  
  [Other Info]
  
  [1] https://lists.gnu.org/archive/html/grub-devel/2022-08/msg00137.html
  [PATCH 0/2] templates/linux_xen: Properly handle multiple initrd files
  
  grub.git commits:
  18d8eafdea23 templates/linux_xen: Properly order the multiple initrd files
  b4b4acaf4ec7 templates/linux_xen: Properly load multiple initrd files

** Changed in: grub2 (Ubuntu Jammy)
       Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-jammy

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

Title:
  Xen Dom0 linux boot fails with multiple initrd files

Status in grub2 package in Ubuntu:
  Fix Released
Status in grub2 source package in Focal:
  In Progress
Status in grub2 source package in Jammy:
  Fix Committed
Status in grub2 source package in Kinetic:
  Fix Released

Bug description:
  [Impact]

  The linux_xen template seems to be broken for multiple initrd files.

  Linux fails to boot when it needs a real initrd but early/microcode
  initrd(s) are found by grub-mkconfig.

  The 2 patches (merged upstream [2]) allow more than one initrd to be
  actually loaded, and the real/non-microcode initrd get used by Linux.

  More details in the patchset cover letter [1].

  [Test Plan]

      $ sudo apt install microcode-initrd

      $ du --bytes /boot/...
      13660416 /boot/vmlinuz-5.4.0-122-generic
      33062542 /boot/initrd.img-5.4.0-122-generic
      5045248  /boot/microcode.cpio

      $ sudo reboot

  - Original:

      [    2.505207] Kernel panic - not syncing: VFS: Unable to mount root
      fs on unknown-block(0,0)

  - Patch 1:

      [    1.890498] Freeing initrd memory: 4928K
      ...
      [    2.710948] Kernel panic - not syncing: VFS: Unable to mount root
      fs on unknown-block(0,0)

  - Patch 2:

      [    1.968578] Freeing initrd memory: 32288K
      ...
      [    2.844889] Run /init as init process
      [    2.916532] systemd-udevd[148]: Starting version 245.4-4ubuntu3.17

  [Where problems could occur]

  Regressions would be likely to manifest when booting Linux under Xen
  with more than one initrd file (changes contained in this code path).

  [Other Info]

  [1] https://lists.gnu.org/archive/html/grub-devel/2022-08/msg00137.html
  [PATCH 0/2] templates/linux_xen: Properly handle multiple initrd files

  grub.git commits:
  18d8eafdea23 templates/linux_xen: Properly order the multiple initrd files
  b4b4acaf4ec7 templates/linux_xen: Properly load multiple initrd files

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1987567/+subscriptions