From: "Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>
To: Roman Shaposhnik <roman@zededa.com>
Cc: xen-devel@lists.xenproject.org
Subject: Re: [Xen-devel] Likely regression in efi=no-rs option
Date: Sun, 17 Nov 2019 00:07:44 +0100 [thread overview]
Message-ID: <20191116230744.GC4109@mail-itl> (raw)
In-Reply-To: <CAMmSBy9VN9fFC1M5P7OdLOiwZdgWjjWjMWppA63gnOe5wwGr4A@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1304 bytes --]
On Fri, Nov 15, 2019 at 09:24:38PM -0800, Roman Shaposhnik 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
As Rich already said, there was indeed some related changes, that should
make efi=no-rs not needed as an workaround on many machines.
But also it looks like the "efi: use directmap to access runtime
services table" commit broke efi=no-rs case. I'll send the fix shortly.
--
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 157 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2019-11-16 23:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-16 5:24 [Xen-devel] Likely regression in efi=no-rs option Roman Shaposhnik
2019-11-16 20:47 ` Rich Persaud
2019-11-19 7:13 ` Roman Shaposhnik
2019-11-16 23:07 ` Marek Marczykowski-Górecki [this message]
2019-11-18 1:06 ` Roman Shaposhnik
2019-11-18 1:27 ` Marek Marczykowski-Górecki
2019-11-19 7:15 ` Roman Shaposhnik
2019-11-19 13:56 ` Marek Marczykowski-Górecki
-- strict thread matches above, loose matches on Subject: below --
2019-11-19 7:31 Rich Persaud
2019-11-19 7:38 ` Roman Shaposhnik
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20191116230744.GC4109@mail-itl \
--to=marmarek@invisiblethingslab.com \
--cc=roman@zededa.com \
--cc=xen-devel@lists.xenproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.