Re: passing options to grub in xen,openfirmware and efi

[Vladimir 'φ-coder/phcoder' Serbinenko]

On 07.05.2015 17:03, Andrei Borzenkov wrote:
> On Thu, May 7, 2015 at 5:59 PM, Vladimir 'φ-coder/phcoder' Serbinenko
> <address@hidden> wrote:
>> On 07.05.2015 16:54, Olaf Hering wrote:
>>> On Thu, May 07, Vladimir 'φ-coder/phcoder' Serbinenko wrote:
>>>
>>>>
>>>>> Sigh..
>>>>> There are likely ways to find out where grub was loaded from even on a
>>>>> PC, and use that as initial root=. In a PV guest no such thing exists
>>>>> because itself grub is the firmware.
>>>> grub-install already takes this into account.
>>>
>>> There is no grub-install in that case.
>>>
>>> We run in circles, and to get out of the loop I have to show code.
>>>
>> No, you need to show an actual usecase with enough details and
>> explanation why the solutions that already exist are inadequate.
> 
> 
> The way pv-grub2 is built by distributions now is grub-mkstandalone
> with grub.cfg that search several predefined directories for "real"
> guest grub.cfg. Passing its location as boot argument would make it
> possible to remove these harcdoded locations.
> 
most other firmwares like EFI or BIOS look for boot image at hardcoded
place e.g. MBR or ESP at predefined locations or uses NVRAM. The trouble
with passing this info from dom0 is that it's difficult to discover for
grub-install where to put image, in some cases this would even make
install impossible without modifying dom0. I feel like location which
changes all the time would create more confusion that hardcoded location
(E.g. I ran grub-install but my system still uses old GRUB)
> _______________________________________________
> Grub-devel mailing list
> address@hidden
> https://lists.gnu.org/mailman/listinfo/grub-devel
>

signature.asc
Description: OpenPGP digital signature