[Bug 1890612] [NEW] ITP: Please support loading microcode early, whilst otherwise booting without initrd
Launchpad Bug Tracker
1890612 at bugs.launchpad.net
Thu Oct 22 14:47:42 UTC 2020
You have been subscribed to a public bug by Dimitri John Ledkov (xnox):
[Impact]
* New package to provide micorocode-only initrd for application of
microcode on boot, when otherwise no initrd is in use.
[Test Case]
* install microcode-initrd in AWS cloud x86 metal instance
* reboot, observe that microcode has been applied, and yet the boot was without initrd (observe journalctl -b -k to see that initrd was not used for boot)
[Regression Potential]
* This is a brand new package, that will be used by AWS images.
Otherwise this package will not be automatically installed anywhere. Re
spinning & promoting AWS images are tested and gated by the CPC team.
[Other Info]
* Original bug report for groovy:
Normally Ubuntu boots using initrd that has three archives: early amd64
microcode, early intel microcode, and compressed main initrd.
When booting without initrd, simply kernel is loaded without any initrd
and thus without microcode.
However, grub supports booting with multiple initrds and one can specify
a standalone early initrd which contains microcode only, and separate
main initrd.
As an added bonus one can also specify just eary microcode initrd
without a main one, to allow kernel to load microcode early, but
otherwise boot without an initrd.
To achieve that I need to introduce a microcode-initrd package will will
only provide early initrd which only has microcode.
The intention is to seed microcode-initrd to targets that boot on
baremental without initrd.
** Affects: cloud-images
Importance: Undecided
Status: Fix Committed
** Affects: microcode-initrd (Ubuntu)
Importance: Undecided
Status: Fix Released
** Affects: microcode-initrd (Ubuntu Focal)
Importance: Undecided
Status: New
--
ITP: Please support loading microcode early, whilst otherwise booting without initrd
https://bugs.launchpad.net/bugs/1890612
You received this bug notification because you are a member of Ubuntu Package Archive Administrators, which is subscribed to the bug report.
More information about the ubuntu-archive
mailing list