On Thu, May 07, Vladimir 'φ-coder/phcoder' Serbinenko wrote: > 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)
What do you expect from grub-install in a PV guest? Whatever it does today its result will be a noop. All that needs to be done is to write /boot/grub2/grub.cfg. In a PV guest grub2 is the firmware (kernel= in domU.cfg), and the NVRAM is the cmdline (extra= in domU.cfg). Olaf _______________________________________________ Grub-devel mailing list Grub-devel@gnu.org https://lists.gnu.org/mailman/listinfo/grub-devel
