Re: [Xen-users] Xen must be on a 2Mb boundary

[jim burns <jim_burn@xxxxxxxxxxxxx>]

Forgot to mention that any replies should cc: me. Thx, Mark, for doing so.

On Wednesday, 22 February 2017, 17:53:43 EST, Mark Pryor wrote:
> Hello,
> I see "All files are in the same
> sub directory of the ESP."
> https://wiki.xenproject.org/wiki/Xen_EFI
> 
> As noted above, you might try with efibootmgr to make a menu entry in the
> EFI bios. I think this is a simpler approach than chain loading via grub.

Saw that page. At the bottom is the very grub stanza I'm using. I could try 
efibootmgr, but I would have to change it every time xen bumps up it's version 
number, and I wanted to try this stanza. Editing xen.cfg is fairly painless, 
and you still need it to tell xen.efi what kernel and ramdisk to use, and what 
options to use. You think grub is messing with the memory map, and that's why 
xen.efi is not loading correctly?

> Are you using the Xen rpms from distro, or did you build from source? I
> have a spec and SRPM from xen-4.7 & fc25 that should work with xen-4.8, but
> have not done that particular build yet. PryMar56

The only time I compile Fedora's xen .srpm is when I add "--enable-ovmf" to 
the configure command, and all I want from that is hvmloader. My win10 guest 
is efi. I only do this once for every version of xen, and not for each of the 
Fedora sub-revisions that don't change the xen version. Most of the time, I'm 
using Fedora's official xen.efi, from rawhide.

Side note: this worked fine for xen 4.6 & 4.7. For xen 4.8, the compiled 
hvmloader won't load my win10 guest (with bios='ovmf' in it's config), but the 
old hvmloader from xen 4.7 still works. The 4.8 hvmloader is also smaller than 
4.7, and there is a separate ovmf.bin, instead of being folded in to 
hvmloader, like in previous versions.
 
>     On Wednesday, February 22, 2017 9:10 AM, jim burns
> <jim_burn@xxxxxxxxxxxxx> wrote:
> 
> 
>  I get the error msg in the Subject when trying to boot xen via xen.efi on
> Fedora 25, kernels 4.8 - 4.10, xen 4.7 or 4.8.
> 
> My grub2 stanza is:
> 
> menuentry "Xen EFI" --class os {
>     insmod part_gpt
>     insmod search_fs_uuid
>     insmod chain
>     set root='hd0,gpt8'
>     chainloader (hd0,gpt8)/EFI/fedora/xen-4.8.0.efi
> }
> 
> and my xen.cfg is:
> 
> [global]
> default=fedora
> chain=grub.cfg
> 
> [fedora]
> options=dom0_mem=min:4G,max:16G cpufreq=xen loglvl=all guest_loglvl=all
> ucode=scan tmem=1 tmem_dedup=1 tmem_compress=1 nmi=dom0 vpmu=1
> kernel=vmlinuz ro root=/dev/mapper/vg_insp3847-lv_root microcode.early=y
> earlyprintk=vga
> ramdisk=initramfs.img
> ucode=GenuineIntel.bin
> 
> [kernel 4.9.10]
> options=dom0_mem=min:4G,max:16G cpufreq=xen loglvl=all guest_loglvl=all
> ucode=scan tmem=1 tmem_dedup=1 tmem_compress=1 nmi=dom0 vpmu=1
> kernel=vmlinuz-4.9.10-200.fc25.x86_64 ro
> root=/dev/mapper/vg_insp3847-lv_root microcode.early=y earlyprintk=vga
> ramdisk=initramfs-4.9.10-200.fc25.x86_64.img
> ucode=GenuineIntel.bin
> 
> [kernel 4.8.16]
> options=dom0_mem=min:4G,max:16G cpufreq=xen loglvl=all guest_loglvl=all
> ucode=scan tmem=1 tmem_dedup=1 tmem_compress=1 nmi=dom0 vpmu=1
> kernel=vmlinuz-4.8.16-300.fc25.x86_64 ro
> root=/dev/mapper/vg_insp3847-lv_root microcode.early=y earlyprintk=vga
> ramdisk=initramfs-4.8.16-300.fc25.x86_64.img
> ucode=GenuineIntel.bin
> 
> [kernel 4.7.9]
> options=dom0_mem=min:4G,max:16G cpufreq=xen loglvl=all guest_loglvl=all
> ucode=scan tmem=1 tmem_dedup=1 tmem_compress=1 nmi=dom0 vpmu=1
> kernel=vmlinuz-4.7.9-300.fc24.x86_64 ro root=/dev/mapper/vg_insp3847-lv_root
> microcode.early=y earlyprintk=vga
> ramdisk=initramfs-4.7.9-300.fc24.x86_64.img
> ucode=GenuineIntel.bin
> 
> [kernel 4.6.7]
> options=dom0_mem=min:4G,max:16G cpufreq=xen loglvl=all guest_loglvl=all
> ucode=scan tmem=1 tmem_dedup=1 tmem_compress=1 nmi=dom0 vpmu=1
> kernel=vmlinuz-4.6.7-300.fc24.x86_64 ro root=/dev/mapper/vg_insp3847-lv_root
> microcode.early=y earlyprintk=vga
> ramdisk=initramfs-4.6.7-300.fc24.x86_64.img
> ucode=GenuineIntel.bin
> 
> 
> I've tried xen.cfg w/o the extra kernel 4.x stanzas. All files are in the
> same sub directory of the ESP.
> 
> Anybody have any ideas? Thx.
> 
> 
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxx
> https://lists.xen.org/xen-users



_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxx
https://lists.xen.org/xen-users