Re: 23.04: desktop iso peculiarity compared to the live-server one
On Tue, 27 Jun 2023 at 13:59, Michael Hudson-Doyle < michael.hud...@canonical.com> wrote: > On Fri, 23 Jun 2023 at 11:38, Adam Vodopjan > wrote: > >> Mby you're the correct person to report another issue with install images. >> Since 21.04 the boot/grub/loopback.cfg in live-server is broken: the >> 'iso-scan/filename=' piece is gone. >> > > Argh that was an unintended consequence of removing 'quiet' from the > default kernel command line. This should fix it: > > https://code.launchpad.net/~mwhudson/debian-cd/+git/ubuntu/+merge/445395 > So this should be fixed in the next mantic and jammy dailies. Thanks for the report! Cheers, mwh > > -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: 23.04: desktop iso peculiarity compared to the live-server one
On Fri, 23 Jun 2023 at 11:38, Adam Vodopjan wrote: > Mby you're the correct person to report another issue with install images. > Since 21.04 the boot/grub/loopback.cfg in live-server is broken: the > 'iso-scan/filename=' piece is gone. > Argh that was an unintended consequence of removing 'quiet' from the default kernel command line. This should fix it: https://code.launchpad.net/~mwhudson/debian-cd/+git/ubuntu/+merge/445395 Cheers, mwh -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: 23.04: desktop iso peculiarity compared to the live-server one
Mby you're the correct person to report another issue with install images. Since 21.04 the boot/grub/loopback.cfg in live-server is broken: the 'iso-scan/filename=' piece is gone. -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: 23.04: desktop iso peculiarity compared to the live-server one
On Fri, 23 Jun 2023 at 10:24, Adam Vodopjan wrote: > > THE QUESTION I WANTED TO ASK, is: was it intentional to not set the default > layer in initrd in the desktop iso case? > > I don't think we ever got around to discussing it properly. I think the desktop ISO should be changed to do things the same way as the server ISO does, for the same sort of reason you talk about (although my motivation for the server ISOs was mostly to make netbooting easier, it's the same thing really). Cheers, mwh -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
23.04: desktop iso peculiarity compared to the live-server one
Since live-server 21.10 the squashes under casper/ are organized a new way and
there is conf/conf.d/default-layer.conf in initrd with content like this:
LAYERFS_PATH=ubuntu-server-minimal.ubuntu-server.installer.generic.squashfs
Since 23.04 the desktop iso uses the same way to organize the squashes as
live-server does but there is no conf/conf.d/default-layer.conf in its initrd,
the layer is explicitly set in grub conf:
linux /casper/vmlinuz layerfs-path=minimal.standard.live.squashfs ..
The problem in my case is it breaks a very generic way to loop-boot ubuntu
desktop and live-server isos. Grub conf example:
menuitem ubuntu-xx.yy--amd64.iso {
set iso_path="/path/ubuntu-xx.yy--amd64.iso"
loopback loop "$iso_path"
linux (loop)/casper/vmlinuz* boot=casper iso-scan/filename="$iso_path"
initrd (loop)/casper/initrd*
}
For desktop isos it works since at least 12.04. But 23.04 (and 23.10 daily)
cant boot into the live environment with just that because there is no correct
'layerfs-path=..' piece. It boots into this https://imgur.com/C5NQPpX
Looking into casper:setup_overlay() function I see there are two ways to deal
with squashes. When LAYERFS_PATH ('layerfs-path=..' translates to it) is not
set, it mounts ALL the squashes under casper/ and makes the root out of ALL
those overlayed in reversed lexical order. So what I end up with booting
without layerfs-path set is this bunch of squashes overlayed as root (the order
is preserved):
minimal.zh.squashfs
minimal.standard.zh.squashfs
minimal.standard.squashfs
minimal.standard.ru.squashfs
minimal.standard.pt.squashfs
minimal.standard.no-languages.squashfs
minimal.standard.live.squashfs
minimal.standard.it.squashfs
minimal.standard.fr.squashfs
minimal.standard.es.squashfs
minimal.standard.en.squashfs
minimal.standard.de.squashfs
minimal.squashfs
minimal.ru.squashfs
minimal.pt.squashfs
minimal.no-languages.squashfs
minimal.it.squashfs
minimal.fr.squashfs
minimal.es.squashfs
minimal.en.squashfs
minimal.de.squashfs
To see it yourself, boot the iso in a vm, press 'e' on the default grub entry
to edit it, replace the 'layerfs-path=..' piece with 'break=casper-bottom' and
press C-x to continue. If would end up in a shell were you can run 'mount' to
witness 21 loop mounts for all the squashes along with the massive root overlay
mount.
If only the default layer was set in the initrd the same way as in the
live-server case, it would work.
THE QUESTION I WANTED TO ASK, is: was it intentional to not set the default
layer in initrd in the desktop iso case?
--
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
