[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: Making reqpart in kickstart to do BIOS+UEFI with GPT on x86?



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!



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]