Yes, the design here is that, since we provide custom kernels for our
cloud partners which have all the drivers needed to boot built in,
loading an initrd is a waste of time at boot.
If someone is using a kernel other than the one we provide for the
cloud, or in the case of a bug, the system will still boot (slower)
after a panic and a reboot to try again with the initrd.
Removing this functionality would be a pessimization. The vast majority
of Ubuntu instances in Azure are expected to be booted with the provided
linux-azure kernel, which does not require an initrd. Canonical does
not support the use of other kernels on Azure. And if someone needs to
use a different kernel on an instance without the double-boot process,
they can edit the /etc/default/grub.d/40-force-partuuid.cfg config file
that is provided with the image at the same time they are installing the
different kernel to get the previous behavior.
** Changed in: grub2 (Ubuntu)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1870189
Title:
initramfs does not get loaded
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1870189/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
