Hey all,
Last week, Dan Horak notified the Cloud WG that we accidentally broke ppc64le images[1] with our Hybrid BIOS+UEFI on GPT setup[2] because now there's no PReP partition being made for POWER images.
He suggested in the ticket that it might be worth asking if we could have the reqpart command extended to do BIOS+UEFI setup when on GPT. If not by default, perhaps adding a flag to do it?
This would make it a lot easier for me to get this working across architectures with Fedora Cloud and would probably be beneficial for RHEL 9+ as well.
What do y'all think?
Thanks in advance and best regards, Neal
[1]: https://pagure.io/cloud-sig/issue/346 [2]: https://pagure.io/fedora-kickstarts/blob/ec56783946dcd3c81ab55f33a8df8d30cd3...
On Tue, Aug 31, 2021 at 4:58 AM Neal Gompa ngompa13@gmail.com wrote:
Hey all,
Last week, Dan Horak notified the Cloud WG that we accidentally broke ppc64le images[1] with our Hybrid BIOS+UEFI on GPT setup[2] because now there's no PReP partition being made for POWER images.
He suggested in the ticket that it might be worth asking if we could have the reqpart command extended to do BIOS+UEFI setup when on GPT. If not by default, perhaps adding a flag to do it?
What's would be the difference from the current behavior ?
The docs[0] say about x86 GPT:
"Automatically create partitions required by your hardware platform. These include a /boot/efi for x86_64 and Aarch64 systems with UEFI firmware, biosboot for x86_64 systems with BIOS firmware and GPT, and PRePBoot for IBM Power Systems."
So it would create biosboot and UEFI partitions at the same time (possibly after a flag being passed) ? Also, does this also impact autopart - should it provide similar functionality ?
In any case, as this is a but over my head, I'm adding Vendy a Vojta to chime in on the storage stuff and Javier to possibly comment on the bootloader related aspects.
[0] https://pykickstart.readthedocs.io/en/latest/kickstart-docs.html#reqpart
This would make it a lot easier for me to get this working across architectures with Fedora Cloud and would probably be beneficial for RHEL 9+ as well.
What do y'all think?
Thanks in advance and best regards, Neal
-- 真実はいつも一つ！/ Always, there's only one truth!
Anaconda-devel-list mailing list Anaconda-devel-list@redhat.com https://listman.redhat.com/mailman/listinfo/anaconda-devel-list
On Wed, 1 Sep 2021 15:57:28 +0200 Martin Kolman mkolman@redhat.com wrote:
On Tue, Aug 31, 2021 at 4:58 AM Neal Gompa ngompa13@gmail.com wrote:
Hey all,
Last week, Dan Horak notified the Cloud WG that we accidentally broke ppc64le images[1] with our Hybrid BIOS+UEFI on GPT setup[2] because now there's no PReP partition being made for POWER images.
He suggested in the ticket that it might be worth asking if we could have the reqpart command extended to do BIOS+UEFI setup when on GPT. If not by default, perhaps adding a flag to do it?
What's would be the difference from the current behavior ?
my idea would be adding a "--hybrid" option to "reqpart" that would create both "BIOS" + "EFI" partitions on x86 systems. For remaining systems I believe they use only a single boot partition kind, so nothing will change there. This way you could create a "works everywhere" image the easiest way.
Dan
The docs[0] say about x86 GPT:
"Automatically create partitions required by your hardware platform. These include a /boot/efi for x86_64 and Aarch64 systems with UEFI firmware, biosboot for x86_64 systems with BIOS firmware and GPT, and PRePBoot for IBM Power Systems."
So it would create biosboot and UEFI partitions at the same time (possibly after a flag being passed) ? Also, does this also impact autopart - should it provide similar functionality ?
In any case, as this is a but over my head, I'm adding Vendy a Vojta to chime in on the storage stuff and Javier to possibly comment on the bootloader related aspects.
[0] https://pykickstart.readthedocs.io/en/latest/kickstart-docs.html#reqpart
This would make it a lot easier for me to get this working across architectures with Fedora Cloud and would probably be beneficial for RHEL 9+ as well.
What do y'all think?
Thanks in advance and best regards, Neal
-- 真実はいつも一つ！/ Always, there's only one truth!
Anaconda-devel-list mailing list Anaconda-devel-list@redhat.com https://listman.redhat.com/mailman/listinfo/anaconda-devel-list
On Wed, Sep 1, 2021 at 10:14 AM Dan Horák dan@danny.cz wrote:
On Wed, 1 Sep 2021 15:57:28 +0200 Martin Kolman mkolman@redhat.com wrote:
On Tue, Aug 31, 2021 at 4:58 AM Neal Gompa ngompa13@gmail.com wrote:
Hey all,
Last week, Dan Horak notified the Cloud WG that we accidentally broke ppc64le images[1] with our Hybrid BIOS+UEFI on GPT setup[2] because now there's no PReP partition being made for POWER images.
He suggested in the ticket that it might be worth asking if we could have the reqpart command extended to do BIOS+UEFI setup when on GPT. If not by default, perhaps adding a flag to do it?
What's would be the difference from the current behavior ?
my idea would be adding a "--hybrid" option to "reqpart" that would create both "BIOS" + "EFI" partitions on x86 systems. For remaining systems I believe they use only a single boot partition kind, so nothing will change there. This way you could create a "works everywhere" image the easiest way.
It would also make sense for that flag to exist for autopart too, since reqpart and autopart are mutually exclusive, and we do have appliance images that use the latter. In fact, Cloud did[1] until we needed to support the hybrid configuration.
[1]: https://pagure.io/fedora-kickstarts/c/611edda1490ebb93d996acb29692805ec9e481...
-- 真実はいつも一つ！/ Always, there's only one truth!
On Wed, Sep 01, 2021 at 04:08:30PM +0200, Dan Horák wrote:
my idea would be adding a "--hybrid" option to "reqpart" that would create both "BIOS" + "EFI" partitions on x86 systems. For remaining systems I believe they use only a single boot partition kind, so nothing will change there. This way you could create a "works everywhere" image the easiest way.
I'd like to see adding flags an option of last resort :) If it's possible for anaconda to figure out what's needed automatically that's would be best.
Brian
On Wed, Sep 1, 2021 at 1:47 PM Brian C. Lane bcl@redhat.com wrote:
On Wed, Sep 01, 2021 at 04:08:30PM +0200, Dan Horák wrote:
my idea would be adding a "--hybrid" option to "reqpart" that would create both "BIOS" + "EFI" partitions on x86 systems. For remaining systems I believe they use only a single boot partition kind, so nothing will change there. This way you could create a "works everywhere" image the easiest way.
I'd like to see adding flags an option of last resort :) If it's possible for anaconda to figure out what's needed automatically that's would be best.
How would Anaconda be able to figure it out? The idea is that this works *regardless* of what the host says it does. Unless you're just going to make Anaconda always do hybrid for x86, there's no reasonable way for that to be "auto-detected".
On Wednesday, September 1, 2021, 01:58:21 PM EDT, Neal Gompa ngompa13@gmail.com wrote:
On Wed, Sep 1, 2021 at 1:47 PM Brian C. Lane bcl@redhat.com wrote:
On Wed, Sep 01, 2021 at 04:08:30PM +0200, Dan Horák wrote:> > > my idea would be adding a "--hybrid" option to "reqpart" that would> > > create both "BIOS" + "EFI" partitions on x86 systems. For remaining> > > systems I believe they use only a single boot partition kind, so> > > nothing will change there. This way you could create a "works> > > everywhere" image the easiest way.> >> > I'd like to see adding flags an option of last resort :) If it's> > possible for anaconda to figure out what's needed automatically that's> > would be best.> >> > How would Anaconda be able to figure it out? The idea is that this> works *regardless* of what the host says it does. Unless you're just> going to make Anaconda always do hybrid for x86, there's no reasonable> way for that to be "auto-detected".>
When I kickstart, I check "/sys/firmware" for 'efi' which exists, which I later use to influence which command to use to rebuild grub.My point is that anaconda should be able to check for /sys/firmware/efi, for forcing hybrid usage, or it is only a BIOS host.
_______________________________________________ Anaconda-devel-list mailing list Anaconda-devel-list@redhat.com https://listman.redhat.com/mailman/listinfo/anaconda-devel-list
Hi everyone,
Dne 01. 09. 21 v 20:22 Joe Wulf napsal(a):
On Wednesday, September 1, 2021, 01:58:21 PM EDT, Neal Gompa ngompa13@gmail.com wrote:
On Wed, Sep 1, 2021 at 1:47 PM Brian C. Lane <bcl@redhat.com
mailto:bcl@redhat.com> wrote:
On Wed, Sep 01, 2021 at 04:08:30PM +0200, Dan Horák wrote:
my idea would be adding a "--hybrid" option to "reqpart" that would create both "BIOS" + "EFI" partitions on x86 systems. For remaining systems I believe they use only a single boot partition kind, so nothing will change there. This way you could create a "works everywhere" image the easiest way.
I'd like to see adding flags an option of last resort :) If it's possible for anaconda to figure out what's needed automatically that's would be best.
How would Anaconda be able to figure it out? The idea is that this works *regardless* of what the host says it does. Unless you're just going to make Anaconda always do hybrid for x86, there's no reasonable way for that to be "auto-detected".
When I kickstart, I check "/sys/firmware" for 'efi' which exists, which I later use to influence which command to use to rebuild grub. My point is that anaconda should be able to check for /sys/firmware/efi, for forcing hybrid usage, or it is only a BIOS host.
Yes, Anaconda could look if we can install also UEFI next to the BIOS but the point is that most of the users do not want this and we are not able to figure out if we should install only UEFI or both BIOS boot + UEFI.
Jirka
Anaconda-devel-list mailing list Anaconda-devel-list@redhat.com mailto:Anaconda-devel-list@redhat.com https://listman.redhat.com/mailman/listinfo/anaconda-devel-list https://listman.redhat.com/mailman/listinfo/anaconda-devel-list
Anaconda-devel-list mailing list Anaconda-devel-list@redhat.com https://listman.redhat.com/mailman/listinfo/anaconda-devel-list
On Thu, Sep 2, 2021 at 9:20 AM Jiri Konecny jkonecny@redhat.com wrote:
Hi everyone,
Dne 01. 09. 21 v 20:22 Joe Wulf napsal(a):
On Wednesday, September 1, 2021, 01:58:21 PM EDT, Neal Gompa ngompa13@gmail.com ngompa13@gmail.com wrote:
On Wed, Sep 1, 2021 at 1:47 PM Brian C. Lane bcl@redhat.com wrote:
On Wed, Sep 01, 2021 at 04:08:30PM +0200, Dan Horák wrote:
my idea would be adding a "--hybrid" option to "reqpart" that would create both "BIOS" + "EFI" partitions on x86 systems. For remaining systems I believe they use only a single boot partition kind, so nothing will change there. This way you could create a "works everywhere" image the easiest way.
I'd like to see adding flags an option of last resort :) If it's possible for anaconda to figure out what's needed automatically that's would be best.
How would Anaconda be able to figure it out? The idea is that this works *regardless* of what the host says it does. Unless you're just going to make Anaconda always do hybrid for x86, there's no reasonable way for that to be "auto-detected".
When I kickstart, I check "/sys/firmware" for 'efi' which exists, which I later use to influence which command to use to rebuild grub. My point is that anaconda should be able to check for /sys/firmware/efi, for forcing hybrid usage, or it is only a BIOS host.
Yes, Anaconda could look if we can install also UEFI next to the BIOS but the point is that most of the users do not want this and we are not able to figure out if we should install only UEFI or both BIOS boot + UEFI.
Yeah, I'm afraid some sort of flag will be needed as we certainly don't want this to be the default behavior.
The use case we are discussing is about (cloud) image generation, right ? Eq. you want to generate an image that will boot on both BIO or UEFI system, with Anaconda. I think that makes perfect sense for (cloud) images, to make them boot anywhere.
Yet for an installation to physical hardware, I don't think it makes sense - it's either configured to boot as a BIOS machine or an UEFI machine, so making the thing both BIOS + UEFI capable IMHO does not make sense. Having both options in place would just complicate things, consume extra space & make it more fragile.
Ho do you invoke Anaconda in this case ? With --image or something like that ? Maybe that could be wired to make the resulting image hybrid, but not trigger on installations to physical or virtual hardware ?
Jirka
Anaconda-devel-list mailing list Anaconda-devel-list@redhat.com https://listman.redhat.com/mailman/listinfo/anaconda-devel-list
Anaconda-devel-list mailing listAnaconda-devel-list@redhat.comhttps://listman.redhat.com/mailman/listinfo/anaconda-devel-list
Anaconda-devel-list mailing list Anaconda-devel-list@redhat.com https://listman.redhat.com/mailman/listinfo/anaconda-devel-list
On Fri, Sep 3, 2021 at 8:34 AM Martin Kolman mkolman@redhat.com wrote:
On Thu, Sep 2, 2021 at 9:20 AM Jiri Konecny jkonecny@redhat.com wrote:
Hi everyone,
Dne 01. 09. 21 v 20:22 Joe Wulf napsal(a):
On Wednesday, September 1, 2021, 01:58:21 PM EDT, Neal Gompa ngompa13@gmail.com wrote:
On Wed, Sep 1, 2021 at 1:47 PM Brian C. Lane bcl@redhat.com wrote:
On Wed, Sep 01, 2021 at 04:08:30PM +0200, Dan Horák wrote:
my idea would be adding a "--hybrid" option to "reqpart" that would create both "BIOS" + "EFI" partitions on x86 systems. For remaining systems I believe they use only a single boot partition kind, so nothing will change there. This way you could create a "works everywhere" image the easiest way.
I'd like to see adding flags an option of last resort :) If it's possible for anaconda to figure out what's needed automatically that's would be best.
How would Anaconda be able to figure it out? The idea is that this works *regardless* of what the host says it does. Unless you're just going to make Anaconda always do hybrid for x86, there's no reasonable way for that to be "auto-detected".
When I kickstart, I check "/sys/firmware" for 'efi' which exists, which I later use to influence which command to use to rebuild grub. My point is that anaconda should be able to check for /sys/firmware/efi, for forcing hybrid usage, or it is only a BIOS host.
Yes, Anaconda could look if we can install also UEFI next to the BIOS but the point is that most of the users do not want this and we are not able to figure out if we should install only UEFI or both BIOS boot + UEFI.
Yeah, I'm afraid some sort of flag will be needed as we certainly don't want this to be the default behavior.
The use case we are discussing is about (cloud) image generation, right ? Eq. you want to generate an image that will boot on both BIO or UEFI system, with Anaconda. I think that makes perfect sense for (cloud) images, to make them boot anywhere.
Yet for an installation to physical hardware, I don't think it makes sense - it's either configured to boot as a BIOS machine or an UEFI machine, so making the thing both BIOS + UEFI capable IMHO does not make sense. Having both options in place would just complicate things, consume extra space & make it more fragile.
Ho do you invoke Anaconda in this case ? With --image or something like that ? Maybe that could be wired to make the resulting image hybrid, but not trigger on installations to physical or virtual hardware ?
Anaconda is invoked with either Lorax or ImageFactory+Oz for producing these images. But if it's a kickstart flag, I can also extend appliance-tools to handle it too.
-- 真実はいつも一つ！/ Always, there's only one truth!
anaconda-devel@lists.stg.fedoraproject.org
-
Brian C. Lane -
Dan Horák -
Jiri Konecny -
Joe Wulf -
Martin Kolman -
Neal Gompa