[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-users] EFI boot unsuccessful with Ubuntu 18.04 dom0
> So... how do you get grub to load the xen hypervisor? Not entirely clear what you're asking ... If you've multiple boot options, grub needs to be told which config to load -- either selected at the menu manaully, or set as its default selection. Verify all your menuentry, grep -i menuentry /boot/grub2/grub.cfg ... and that the right one's selected, grep saved_entry /boot/grub2/grubenv saved_entry=xen-gnulinux-simple-4c0d851f-c586-1a2a-4976-488765f65863 &/or set manually with grub2-set-default The grub (re)install process should populate the bootloader /boot/efi/EFI/opensuse/grubx64.efi file /boot/efi/EFI/opensuse/grubx64.efi /boot/efi/EFI/opensuse/grubx64.efi: PE32+ executable (EFI application) x86-64 (stripped to external PDB), for MS Windows The efi env is pointed to the correct bootloader, e.g. after a kernel update, with the following command efibootmgr --create --quiet \ --disk /dev/sde \ --part 2 \ --loader '\EFI\opensuse\grubx64.efi' \ --label "suse-xen" where, mount | grep /boot/efi | grep vfat /dev/sde2 on /boot/efi type vfat (rw,relatime,fmask=0002,dmask=0002,allow_utime=0020,codepage=437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro,x-systemd.automount) Note also cat efi/startup.nsh fs0:\EFI\opensuse\grubx64.efi where, fs0: <=== the efi partition mount, The script execs automatically when the EFI shell environment is opened, and loads the 'grubx64.efi', The use of the startup.nsh was (is still?) a holdover necessary to resolve prior/recurring problems with the wonky efi loader. Simply -- for me -- it ensures that the script -- and therefore grub->xen -- loads, instead of dropping me to the EFI prompt. _______________________________________________ Xen-users mailing list Xen-users@xxxxxxxxxxxxxxxxxxxx https://lists.xenproject.org/mailman/listinfo/xen-users
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |