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

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



Hello,

I see "All files are in the same
sub directory of the ESP."


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.

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


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

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.