2022-07-12 02:29:52 |
Michael Hudson-Doyle |
bug |
|
|
added bug |
2022-07-25 14:29:56 |
Benjamin Drung |
bug |
|
|
added subscriber Benjamin Drung |
2022-08-12 08:38:50 |
Launchpad Janitor |
initramfs-tools (Ubuntu): status |
New |
Fix Released |
|
2022-09-14 19:33:22 |
Brian Murray |
tags |
|
foundations-triage-discuss |
|
2022-09-15 15:37:01 |
Brian Murray |
tags |
foundations-triage-discuss |
foundations-todo |
|
2022-09-15 15:37:05 |
Benjamin Drung |
nominated for series |
|
Ubuntu Jammy |
|
2022-09-15 15:37:05 |
Benjamin Drung |
bug task added |
|
initramfs-tools (Ubuntu Jammy) |
|
2022-09-15 15:37:25 |
Brian Murray |
initramfs-tools (Ubuntu Jammy): status |
New |
Triaged |
|
2022-09-15 15:37:30 |
Brian Murray |
initramfs-tools (Ubuntu Jammy): importance |
Undecided |
Medium |
|
2022-09-15 15:37:44 |
Brian Murray |
bug |
|
|
added subscriber Ubuntu Foundations Bugs |
2022-09-15 15:39:39 |
Dan Bungert |
bug |
|
|
added subscriber Dan Bungert |
2022-10-27 15:06:22 |
Dan Bungert |
initramfs-tools (Ubuntu Jammy): assignee |
|
Dan Bungert (dbungert) |
|
2022-10-27 19:51:56 |
Dan Bungert |
description |
If you use UEFI http boot to boot an image (rather than an EFI executable) and get all the way to a normal userspace, you can access the boot image as /dev/pmem0. But this is not accessible in the initrd; presumably some modules are missing. Dimitri added some modules that are clearly going to be necessary (kernel/drivers/nvdimm) in 0.140ubuntu14 and I added kernel/drivers/dax too in local experiments but this appears not to be enough to get it to appear.
This is desirable because then you can just feed an installer ISO to a machine via http boot and the installer just works as normal (the speed and, uh, quality, of the implementation of HTTP in a given machine's firmware may mean this isn't always the best option but it would be nice if it worked in case someone's machine actually does this well). |
[ Impact ]
* If you use UEFI http boot to boot an image (rather than an EFI
executable) and get all the way to a normal userspace, you can
access the boot image as /dev/pmem0. But this is not accessible in
the initrd; presumably some modules are missing.
* This is desirable because then you can just feed an installer ISO to
a machine via http boot and the installer just works as normal
* Add support for physical pmem devices, and simulation thereof with
the memmap kernel command line parameter
* The initrd is larger
[ Test Plan ]
* unpack an initrd on a Jammy system with the generic kernel
metapackage with unmkinitramfs
* observe that the directories kernel/drivers/{nvdimm,dax,acpi/nfit}
are not present
* install the updated initramfs-tools packages from proposed
* again unpack an initrd on a Jammy system with the generic kernel
metapackage with unmkinitramfs
* observe that the directories kernel/drivers/{nvdimm,dax,acpi/nfit}
are present now
* reboot to confirm that the system still boots
* modify /etc/default/grub GRUB_CMDLINE_LINUX_DEFAULT to contain a
memmap entry - memmap=1G!4G seems to work on many systems over 4G of
RAM, or do `dmesg | grep BIOS-e820` to observe the memory regions
and select a usable one.
* update-grub and reboot again
* a /dev/pmem device should now be present on the system
[ Where problems could occur ]
* The growth of the files in /boot will accelerate issues for users
who have a dedicated boot partition that is not large enough
[ Other Info ]
* Details on the memmap kernel command line parameter:
https://www.kernel.org/doc/Documentation/admin-guide/kernel-parameters.txt
* PMEM simulation with memmap:
https://docs.pmem.io/persistent-memory/getting-started-guide/creating-development-environments/linux-environments/linux-memmap
[ Original Bug Description ]
If you use UEFI http boot to boot an image (rather than an EFI executable) and get all the way to a normal userspace, you can access the boot image as /dev/pmem0. But this is not accessible in the initrd; presumably some modules are missing. Dimitri added some modules that are clearly going to be necessary (kernel/drivers/nvdimm) in 0.140ubuntu14 and I added kernel/drivers/dax too in local experiments but this appears not to be enough to get it to appear.
This is desirable because then you can just feed an installer ISO to a machine via http boot and the installer just works as normal (the speed and, uh, quality, of the implementation of HTTP in a given machine's firmware may mean this isn't always the best option but it would be nice if it worked in case someone's machine actually does this well). |
|
2022-10-27 20:44:50 |
Dan Bungert |
initramfs-tools (Ubuntu Jammy): status |
Triaged |
In Progress |
|
2022-10-27 20:45:55 |
Dan Bungert |
initramfs-tools (Ubuntu Jammy): assignee |
Dan Bungert (dbungert) |
|
|
2022-12-06 21:50:23 |
Brian Murray |
initramfs-tools (Ubuntu Jammy): status |
In Progress |
Fix Committed |
|
2022-12-06 21:50:24 |
Brian Murray |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
2022-12-06 21:50:26 |
Brian Murray |
bug |
|
|
added subscriber SRU Verification |
2022-12-06 21:50:30 |
Brian Murray |
tags |
foundations-todo |
foundations-todo verification-needed verification-needed-jammy |
|
2022-12-12 20:54:30 |
Dan Bungert |
tags |
foundations-todo verification-needed verification-needed-jammy |
foundations-todo verification-done verification-done-jammy |
|
2022-12-14 21:08:19 |
Launchpad Janitor |
initramfs-tools (Ubuntu Jammy): status |
Fix Committed |
Fix Released |
|
2022-12-14 22:03:38 |
Benjamin Drung |
tags |
foundations-todo verification-done verification-done-jammy |
verification-done verification-done-jammy |
|
2022-12-14 22:03:40 |
Benjamin Drung |
removed subscriber Ubuntu Foundations Bugs |
|
|
|
2024-03-06 18:27:05 |
Benjamin Drung |
initramfs-tools (Ubuntu): importance |
Undecided |
Medium |
|
2024-03-06 18:27:05 |
Benjamin Drung |
initramfs-tools (Ubuntu): status |
Fix Released |
Fix Committed |
|
2024-03-27 17:59:27 |
Launchpad Janitor |
initramfs-tools (Ubuntu): status |
Fix Committed |
Fix Released |
|