Re: [Xen-devel] Likely regression in efi=no-rs option

[Rich Persaud <persaur@xxxxxxxxx>]

I don't know if there's a change in efi=no-rs behavior, but some EFI fixes were 
merged on 10/25, which (on some machines) have reduced the need to disable UEFI 
runtime services to work around non-spec UEFI firmware.  This should increase 
hardware compatibility with Xen.  Of course, there could still be other reasons 
to disable UEFI runtime services.

Could you try booting the affected systems with efi=rs?

Rich

> On Nov 16, 2019, at 00:27, Roman Shaposhnik <roman@xxxxxxxxxx> wrote:
> 
> Hi!
> 
> as I've reported earlier -- part of my testing of Xen 4.13 RC2 failed
> in a massive way with Dom0 never coming up. I've traced that problem
> to the option that we're using to boot Xen:
>    efi=no-rs
> We've been using this option for quite sometime and Xen 4.13 RC2
> is the first one that seems to make Dom0 boot fail with this option
> present (note that RC1 was fine).
> 
> I was wondering whether there were any changes in the areas related
> to UEFI in Xen that may have triggered this.
> 
> Here's the boot line that works with RC2:
>    dom0_mem=1024M,max:1024M dom0_max_vcpus=1 dom0_vcpus_pin smt=false
> adding efi=no-rs make Dom0 boot process fail:
>    efi=no-rs dom0_mem=1024M,max:1024M dom0_max_vcpus=1 dom0_vcpus_pin 
> smt=false
> 
> Attaching xl info and dmesg just in case
> 
> Thanks,
> Roman.
> <dmesg.txt>
> <info.txt>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxxx
> https://lists.xenproject.org/mailman/listinfo/xen-devel

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/mailman/listinfo/xen-devel